« first day (625 days earlier)      last day (4553 days later) » 

03:56
@Iszi lol your upvotes triggered the script.
04:38
@TerryChia Script?
@Iszi the serial voting script. all the votes got reversed.
Aww, damn.
I tried.
yeah :P
Looks like a lot more got removed than mine, unless I did a lot more than I thought.
All yours. I gained 140 yesterday which got reversed. I had not answered any questions in awhile.
04:42
@TerryChia Well, crap. Guess you just need to do it the old fashioned way. Write answers that get up votes from 14 people, or questions that get up-votes from 28.
 
3 hours later…
07:41
2
Q: What is catti trying to accomplish?

Karmic CattiCatti is a former employee of Infosek XML Inc.she feels she was wrongly terminated and wants to hack into her former company's network. Since she remembers some of the server names, he attempts to run the axfr and ixfr commands using DIG. What is catti trying to accomplish?

1
Q: Why would you want to initiate a DoS attack on a system you are testing?

Karmic CattiYou work as a penetration tester for Kaizen Security Consultants. You are currently working on a contract for the state government of India. Your next step is to initiate a DoS attack on their network. Why would you want to initiate a DoS attack on a system you are testing?

Anyone get the feeling they are homework questions?
 
1 hour later…
08:53
@TerryChia very much - I was tempted to close the Dig one, but really it could be edited to "what information does Dig provide?" which is on topic
@RoryAlsop The questions itself might be valid. But the user is very obviously just copying the entire question hoping someone answers it.
Which shouldn't be encouraged.
I know SO strongly discourages very obvious homework questions. Do we have any such policy here?
 
1 hour later…
10:18
0
Q: Is there any way to measure scada systems security. any specific methodolgy?

editorh5Is there any way to measure scada systems security. any specific methodolgy ? just wanna know is theres is any particular audit checklist to examine SCADA systems. kindly post your answers. thanks

This one is a dupe to this one:
1
Q: Is there any way to measure scada systems security?

Karmic CattiIs there any way to measure scada systems security. any specific methodolgy ?

10:59
1
Q: Is there any way to measure scada systems security?

Karmic CattiIs there any way to measure scada systems security. any specific methodolgy ?

It's copy-paste from here: ieeexplore.ieee.org/xpl/…
The answer
11:41
@TerryChia not really. A lot of sites have debated on requirements for homework. Putting rules on homework only serves to spark debates about what is homework. The sane way to cope with homework is to apply the usual quality control.
12:37
Herro
13:21
@TerryChia WE HAVE A POLICY AGAINST BAD QUESTIONS. HOMEWORK ARE "BAD QUESTIONS" BECAUSE THEIR VIRTUES ARE IN MAKING THE STUDENT THINK, NOT IN THE ANSWERS THEMSELVES.
@TomLeek I think I out-ranted you here
@Gilles I STRIVE FOR QUALITY, NOT QUANTITY.
TOO BAD I DON'T VOTE, THOUGH, BECAUSE YOUR RANT IS GOOD.
What is it with plagiarism today?
7
A: Plagiarism should be addressed specifically in the FAQ

ManishEarth Blame Pekka for this answer, he put me up to it ;-) . Enough cats, Pekka? Yes, we need something linkable. The FAQ is an ideal place for this, but there are lots of other similar things that can go there as well. We don't want to bloat the faq, too few people read it already. Still, this par...

CEILING CAT IS WATCHING YOU PLAGIARIZE
3
CEILING CAT WILL FEAST ON YOUR SOUL. AFTER HIS NAP.
13:49
0
A: what scanning tools are unlikely to set off network IDS?

Terry ChiaAs with most things - it isn't about the tool, it is how you use it. Take nmap for example. Beginners to the tool or script kiddies might run scan using the default option. nmap 192.168.1.0/24 The default behavior for nmap without specifying any addition flags would be to perform a syn s...

Woah, my longest post yet.
@TerryChia good showing for second-longest post today :p
3
Q: Why is it possible to sniff an HTTPS / SSL request?

bitmoeI'm new to the realm of HTTP requests and security and all that good stuff, but from what I've read, if you want your requests and responses encrypted, use HTTPS and SSL, and you'll be good. Someone in a previous question posted a link to this app http://www.charlesproxy.com/ which shows that it ...

answers so far are not awful but not great either
That should be here. Although i think its a dupe?
@TerryChia we undoubtedly have questions on the topic, but I can't find an exact dupe, only threads that would be good references for further information
14:23
I answered, and cited a few questions on Sec.SE, but didn't find any duplicate
@RoryAlsop Aww, you beat me to the mass delete by seconds!
@JeffFerland lol - 2 high effort users this morning, so I lost my tolerance :-) Karma person and now this heavy plagiariser
Homework poster's still at it
I woke up... 9 flags? Dafuq?
You could do him for plagiarizing, too
14:34
0
Q: What type of virus is this?

Karmic CattiYou are running known exploits against your network to test for possible vulnerabilities. To test the strength of your virus software, you load a test network to mimic your production network. Your software successfully blocks some simple macro and encrypted viruses. You decide to really test the...

It's Windows!
> #EC council questions
virus code where the code actually rewrites itself entirely and the signatures change from child to child, but the functionality stays the same
Obviously
In fact it looks like all of his questions are from the same source
@Gilles not certain ec|council would be best pleased
and once again he uses incorrect tags
I have nothing against reposting exam questions, except that he should make some attempt to solve them
14:39
Next Q gets a temp ban.
But he must acknowledge his source
@JeffFerland yup
@Gilles agreed - if he shows some effort, and asks for info on a particular piece - sure, we can help. But I agree - no source, no effort - no value
0
Q: Why is it essential that security analysts know Cisco routers inside and out?

Karmic Catti( Ec-council ECSA Certification) all question i am asking are for learning purpose. Why is it essential that security analysts know Cisco routers inside and out?

14:41
@JeffFerland maybe he's reading the transcript? (Hello Karmic. You MUST acknowledge your sources. And you really should make some attempt at solving these exercises by yourself.)
@karmiccatti Hi Karmic. We're having issues with the quality of questions you're posting. Copying (plagiarizing) questions directly is not appropriate for our site.
2
Q: How to hide a running process ?

GrSrUsing Ubuntu 12.04. is there any way to hide a running process ? That process shouldn't' display in system monitor,top,htop . There is no problem to remember the process id (PID) so observation of the process can be done easily .but i want to hide the process completely . is there any way ?

@Gilles Poor quality Q. I don't want it.
@JeffFerland you wouldn't get it, it's on-topic where it is
If I link to a question without saying anything else, treat it as “this question might interest some of the denizens here”, not as “this is a migration request”
14:58
@Gilles I'm so not building a hash table of who means what :P
Off to go organize the rest of the thing I haven't taken care of since moving in and see if maybe I'll actually get internet service today instead of hanging out on my phone.
@Gilles yep - that's how I always read your posts, and usually when I follow the link I am interested.
@JeffFerland hahahaha - roaming data costs FTW
@JeffFerland But it's simple! When I say “Humpty Dumpty”, I mean “it's a beautiful diurnal isomorphism today”
and when I say ‘When I say “Humpty Dumpty”, I mean “it's a beautiful diurnal isomorphism today”’, I mean oops, look at the time, I have something I should be doing
Alright, while we're dealing with everything else this morning...
@JeffFerland are you working for Amazon?
or any such big cloud provider?
just courious
15:10
interesting
I just got a new job - 40 datacentres, global presence, and building new website from scratch, and I am looking for such solutions, have tried already few, will try this one too
like CI etc
The company everything what they make is opensource
So the open source is preffered
@AndrewSmith What is this company?
MI-5 :D
branch of it
that's what I think
Ok....
That's what you think?
I'm hired, but I'm not sure who I'm working for?
15:24
@JeffFerland HE WHO HAS LOOSE CONTACT WITH REALITY JUST ASSUMES THAT EVERYBODY ELSE HAS TOO. THAT'S IMPLACABLY LOGICAL.
4
@JeffFerland UK govt departments will make it very clear who you are working for and what your responsibilities are :-)
they are good like that
@JeffFerland yes
@TomLeek you should go and install wifi hot spots in iraq, then we can talk who has better touch with reality
IMHO I am the best informed person in the world.
I understand all social engineering taking place at every time and it's output :D
just lax of security and cloud automation is holding me back
@JeffFerland I do not represent any company; I have my own business exclusively.
But I work with many companies for 7 yrs, before I was working for hosting provider / ISP
and software development company
Now I have role of DevOps, to push the limits of todays solution and outsmart NSA
DevOps is very smart actually, it has a lot of to do with self-sentinence
DevOps manage GLOBAL CLOUD
It's opposite to single box
So DevOps are open and flexible, just like the global cloud
And they work mainly towards performance
And availability
It's a new kind of job, and new kind of business, hence everything in this subject is now big interest to me, e.g. nimbula
And the "Director" is a very nice thing, as it says by itself, that it's designed for clueless operator
e.g. developers :P
I guess this is DoS:
__ratelimit: 52 callbacks suppressed
TCP: time wait bucket table overflow
nf_conntrack: table full, dropping packet.
nf_conntrack: table full, dropping packet.
nf_conntrack: table full, dropping packet.
nf_conntrack: table full, dropping packet.
echo 1000000 >/proc/sys/net/netfilter/nf_conntrack_max
echo 100000 >/proc/sys/net/ipv4/tcp_max_tw_buckets
15:58
@AndrewSmith Hmmm?
Well I just got spike in traffic I believe, so I maxed the conntrack and I am checking what was that
16:28
/me = NSA
IMHO I have better insight then them actually, also I have procedure for hardening centos 6 and they dont
:D
ps. If you ever wondered who is illuminati, it is me! :D
And I have met with Rihanna twice, to pay tribute to her darkness
16:44
Now I am looking to take over the world; by building self-sentiment network
This is not paranoid, actually there are many companies and governments doing the same
It's up to date research subject
Nimbula has features of it
Self-sentiment network works the way, that the communication between the nodes is very fast, hence it can process large amounts of jobs, like information coming from left side of brain to the right
It's a long path, just like from cloud to cloud
And it's asynchronous too
And by connecting this kind of network to the global internet, and having e.g. 100M viewers per year, and make system understand the content (like youtube does), add language and other layers, you can see in real-time that it's sentinent
And with this, I can predict future events, so I know what it's going to happen
And it's not paranoid, it's advanced research
But nobody except me ever have seen that, because I am still anonymizing the data
As per Rook advise
Hence I believe NSA does have sentinent network too
Such website, has great marketing potential, because it can tell you a lot about your users and their behaviour in english
And can predict lot's of stuff, mostly sales
And it's my own proprietary research
Same system is on the TV - it will be logging what do you watch, and based on that it can hack into your mind
And works much better then web advertising, because it does understand what's on your mind much better
That's why I look for lot's of security, because I have it a lot in every project
And social network websites are excellent for this job
 
3 hours later…
19:58
I hope that one day we'll manage to deploy a name=>key resolution system that doesn't suck.
That certificate business so so annyoing. Users don't understand it.
And understanding it doesn't help either, it's just that you now know that you're doomed.
20:15
@CodesInChaos X.509 was designed to work in the context of the Directory.
Since the Directory does not exist, it is no wonder that X.509 works improperly.
I've always found it strange that you obtain certificates from a separate entity and not through the same route you obtain your domain itself
Can't be less secure, since anybody who can manipulate your DNS can already pass the checks for some CAs which only validate by email
@CodesInChaos there is DNSSEC almost working, it should be sorted out by any time, and there is nothing to stop you from using it for name=>key resolution over internet
I would kill for working DNSSEC, because there is so many bugs because of it
Somebody should speed it up, most of the domains works ok, there are just two or three missing, but the biggest - gov and org
but it makes completely useless
20:30
Putting public keys into DNS is certainly a logical place. Not sure how well DNSSEC will work. Some people think it'd be great, others flame it.
@CodesInChaos If I want to be sure that the water distributed by my home city is fit to drink, I would like a report from an independent analysis lab. Should I expect the report to come out of the faucet too ?
That analogy seems weird.
It's certificates -- weirdness all over the place.
With less analogy: DNSSEC is about empowering the registrars, giving them the powers and duties of CA.
It is unclear whether such a merging of powers is wise or not.
Well the registrars already have those powers, since the validation of a CA already depends on DNS
Not per X.509.
The only links between X.509 and DNS are:
1. with no DNS, no Internet, thus no download of certificates and CRL
2. the client looks for the server _name_ in the server _certificate_, and that name happens to also be the part which goes through the DNS to actually know how to contact the server
First link is more about DoS than validation: break the Internet, and communication does not work.
20:39
The problem is how does the CA know I'm the rightful owner of the domain example.com. This always boils down to somehow asking the registrars
Second link is at best coincidental. And, anyway, in a SSL context, the server sends his certificate to the client, so when the client looks at the certificate, he already knows how to talk to it.
@CodesInChaos There are several ways...
I have seen some CA ask for a specific DNS entry
i.e. they send a challenge (a random value) and expect the value to appear as a TXT field in the domain.
This demonstrates control of the DNS
without any action or awareness from the registrar
have u seen this: nimbula.com
The moderators business
Serious stuff, it does federation of cloud instances
That's my point. In the end all of it boils down to control of DNS, and the trust in the DNS is rooted in the registrars.
I saw 10 job offers to do this - from top 10 companies in London - and this does this automatically
I am resending this offer to everyone now
The system is already only as secure are the DNS, so we can cut out all middle men after that
20:42
@CodesInChaos I have also seen non-DNS approaches
the CA requires thorough identification of the certificate requester, in the "legal person" sense.
This ensures that, if there is trouble, then the certificate can be tracked back to a punishable entity
You still need to match that to a domain, else the client can't verify the certificate automatically.
In that case, there is no link to DNS at all; only that the certificate requester assumes the consequences of the certificate contents.
But those certs by themselves are not useful in a network security context.
The client wants to match two things: the name as displayed to the user and the name in the certificate. This is what validation is about: customer who wants to talk to Amazon sees "amazon.com" on his screen, and wants to be sure that he talks to "amazon.com"
That the same name is also an entry point into a name resolution system is technical and unconnected to the validation business.
For what it's worth, I don't care, and, more importantly, SSL does not care how the IP packets flow between client and server. Poison the DNS so that "www.amazon.com" resolves to your address, and things are still safe, as long as you forward the packets to the true Amazon server.
The name displayed to the user is only a second layer of defense. The main layer is the domain entered by the user.
The main issue is, Does the domain the user typed into the addressbar of his browser match the public key SSL uses?
20:51
By "name displayed to the user" I mean "the one in the URL" (presumably the one he typed, except that people no longer type, they click).
@CodesInChaos Yes, precisely. Match between the name in the URL and the name in the certificate. Resolution of that name into a IP address or whatsnot has no impact on the security of SSL. Communication is not even required to be IP-based (SSL works over a bidirectional tunnel of bytes, and does not care about IP addresses).
But there is still the issue, does the legal entity "Microsoft" own the domain "microsoft.com". And the only way to figure that out goes through the domain registry, directly or indirectly.
@CodesInChaos Note that neither X.509 nor DNSSEC addresses this issue.
And the domain registry does not really, either.
Actually nothing guarantees that microsoft.com is indeed the property of Microsoft, except that we somehow assume that Microsoft would mightily strike at whoever would try to do otherwise (and, indeed, it has happened).
The best you can hope for, with X.509 or DNSSEC, is that whoever signed the public key allegedly attributed to microsoft.com also collected some data which is sufficient to trace back to the actual private key holder.
And that trace always goes through the domain registry in some form. So you already need to trust them. CAs are useful for making a connection to a legal entity, but that's only a second step.
What I want is that the chain between key and domain is as short and strong as possible.
yeah, you can add txt field on the domain with a public key, however if it's not signed by dnssec, it's not cryptographically strong, right
@CodesInChaos Giving the power to act as CA to the people who already act as DNS sure makes things shorter (less people involved) but it does not necessarily equates with stronger, and this does not necessarily equates with safer (for you !)
21:02
I am not sure what u want to do, by dnssec is broken, so this is hopeless job
(warning: analogy ahead) Usually, there is a reason why we prefer that judges and policemen are not the same persons.
Not wanting to merge PKI with DNS relates to the same reasons.
If the only information that the judges obtain is what the policeman says, the separation doesn't gain you anything
@CodesInChaos Yes, but that's absolutely not the case for SSL (see above !)
CAs are cool for things like EAV certificates, where they also create a mapping to a legal person, but IMO they're useless for simple domain certificates
DNS tells you what IP address hides behind a given host name.
IP address is not used in SSL
the IP address is not displayed to the user either
21:05
I'm not talking about IPs
I don't care about IPs, since they are a trivial problem once you have a mapping domainname=>key
but you are talking about the DNS... and the DNS is "only" a system which maps names to IP
The problem is how does a CA figure out if they should give a certificate for example.com to a certain requester.
it all boils down to this: why should the system which maps hostnames to IP addresses be the same system than the one which maps "server names" (as seen by human beings) to public keys ?
DNSSEC solves a distribution problem which was not a problem (SSL servers and clients already have no trouble exchanging certificates), and this "solution" implies that whoever will map names to IP addresses will also have to be the entity which verifies key ownership
These are distinct crafts.
Verifying key ownership is trivial, verifying domain ownership is hard
and domain ownership in the first order is defined by who the domain registry thinks owns that key
@CodesInChaos Key ownership is hard because you have to define what an "owner" is. It is easy to validate that "whoever is talking to you right now" controls a private key. What's hard is to validate that a given key is controlled by Mr Bob Smith (legal entity, can be sued if needed).
21:12
But that's not a question that the browser asks.
The browser just asks Does ownership of key x indicate ownership of domain y?
Verifying that "whoever controls a domain" and "whoever controls a given key" are the same entity is relatively easy, and CA already do it (the "challenge" above), and does not need in any way collaboration of the Registrar.
They verify by trusting DNS
@CodesInChaos Yes. So what ? In what does it imply that the guy who remembers the IP addresses of the name servers for domain y must be the one who puts his seal on the "key x to domain y" covenant ?
@CodesInChaos Certainly not ! What says the DNS that is to be trusted in that case ?
Since the challenge you mentioned consists of demonstrating write access to a certain DNS record
it implies trust in DNS
@CodesInChaos If I give an order to my dog and the dog executes it, does it imply that I or you trusts my dog ?
No, it just demonstrates my control.
By writing a challenge value in the DNS I demonstrate that I am able to write challenge values in the DNS.
21:18
But the control is granted to you through the domain registration
Control is granted by any way it wishes to be granted
So the one granting you that control could instead give you a certificate directly
The CA does not care how I manage to control the domain, as long as I control it.
@ThomasPornin I agree that this analogy seems weird. A closer one would be: do you get a birth certificate and a passport from the same place?
Also, mind the details: adding a challenge value in my domain means that I have control of the name server -- the same name server that is known by IP address by the Registrar.
It is still my name server.
The people who grant me access to my name server are... me !
21:21
And the registrar could decide to move the domain to a different nameserver temporarily, demonstrate control of it, obtain the cert from the CA, and switch it back
@ThomasPornin registration and certification are very closely tied: who owns the domain, who serves data about the domain and who is the public face of the domain are closely tied. What is a separate matter is address resolution
Identity management calls for a central authority… but that's not PC
@CodesInChaos Ah, now we get to something: yes, Registrars have a lot of control over the Internet and are ideally placed to game authentication protocols -- which is a very strong reason why we would prefer to deploy public keys.
This shows that the challenge-in-domain procedure is not sufficient to achieve the kind of security we wish in our name-to-key mapping.
A big part of the CA business is still to gather identification data which could be used to make perpetrators suffer.
Claiming that registrars should be given general CA power because they already have a strong power of nuisance and impersonation (should they elect to use it that way) is akin to saying that when criminals are too powerful we may just as well call them "policemen" and be done with it.
Personally I believe that each top level domain registry should be a trust root. When you buy a domain, you tell them your public key (and optionally your real name, as a means to recover the domain if you lose your key), and they public the mapping domainname=>public key. And courts of the appropriate jurisdiction can force-transfer domains, which will also be published.
I recognize that, historically, monarchy has often worked that way (the strongest makes the Law, ultimately). But I do not mean that it is a model to pursue.
And which and the mapping of top level domain to registry gets hardcoded into the client in some form
It essentially boils down to one CA per TLD
21:32
@CodesInChaos I am still wary of making registrars the basis of trust.
It is not their specialty
CA job is hard, it is full of procedures.
The problem is, that they already are. And I see no way to prevent that
Not that existing CA always do it properly...
but taking the job from the barely competent and giving it to someone who never did it, well, that does not look like a smart move
If they do the job no better than they already manage their DNS, we still don't lose anything
@CodesInChaos Well, there is a way to prevent the root DNS and registrars from impersonating who they wish: build an independent PKI, with unrelated root CA, and distribute X.509 certificates... the very thing that you advocate removing, precisely.
I'm advocating that every CA gets their own namespace
instead of trusting every one of them for every possible name
21:37
@CodesInChaos That was the idea of the Directory.
If you look at .com, verisign currently as full and total control over it. They can create certificates for any .com domain, and they can take anybodies domain away, because they're the registry.
The only thing that adding additional CAs that can create .com certs changes is reducing security
Of course you still need to combine that with some kind of log, containing any certificate every published, to keep that CA honest. But you need that in some form anyways
u know it's not that difficult to take over the domain
in fact, if the registry does it once, and there is proof of this, it's very hard to reverse it
@CodesInChaos Hey, that's my point. Verisign is both a PKI (issues certificates, as a root key in Windows) and a registrar. Validating keys, and mapping names to IP are important services and I would be happier if they were in different hands
but obviously once it goes thru the court, you got sentenced and the domain is taken back
It is called separation of powers.
21:43
The core service is mapping names to control, and control preferably takes the form of a public key.
once you have that, the name->ip mapping becomes a powerless service
@CodesInChaos Indeed. Essential for continuity of operations, but powerless for security issues.
None of this says why the powerless service should be maintained by exactly the same people than the PKI thing.
What I want is that the institution that sells domains in a certain TLD is the one that does the PKI for that TLD.
Actually I find that it says why the powerless service should not be maintained by the same people: to avoid concentration of powers.
I don't care either way. I just want a short and strong domain-name=>key mapping
@CodesInChaos Well... why would you want it ? Apart that it would appear "logical" to you (and not to me)
21:47
And the domain-name administration is by definition centralized
The PKI companniesw are geo localized on the English speaking countries, like south america, australia, us and uk, while the domain I guess mainly resides in US :P
I have helped to build one PKI company in central Europe myself, for public use, and ppl use it via website and browser generates the key, and this makes the transaction and document download.
@CodesInChaos It is a good goal but I still don't see how DNSSEC would bring you closer to it in any way.
So this way it doesnt go out of country and the keys are in the control of the website owner, so who needs that PKI any way - and the connection is via IP number - BGP - no domain involved
While DNSSEC is probably not optimal, it essentially takes your interactive challenge "Demonstrate control over the DNS record" and turns it into a non interactive one "Put your fingerprint into the DNS record"
@CodesInChaos And, in the same time, it implies that the CA job must be done by someone who is either new to it (not good), or someone who already does both and thus does not need it to be formalized any further (the case of Verisign).
21:53
It reduces the number of trust roots.
Currently we have 100+ of those, each with full trust over all domains
And it's as weak as the weakest of them
Afterwards we only have one per TLD
And it's not like the current design avoids a monopoly either. That's inherent in a name registration system.
@CodesInChaos So what you are actually requesting is not really a merging of CA with TLD per se, but removal of a number of crappy CA and a fresh restart with only a few (presumably competent) CA, a situation which could (hopefully) be obtained as a by-product of switching to DNSSEC ?
I want one CA per TLD, and that users buy their domain with that CA.
That's what I understand from what you say about centralization and the power or registrars: that giving them CA power would not break the system anymore than what it already is, and thus we can do it if only for an interesting side effect.
@CodesInChaos I think it can be fairly said that it is quite clear that you want that. What I dispute is the justification: that it would increase security.
You always need once central authority who does the name administration. And everybody else, directly or indirectly, refers to that authority to figure out who owns that domain.
There is no way around that part, it's inherent in a global naming system.
@CodesInChaos I dispute that, too.
I mean, the registry is what it is named: a registry.
22:00
How would you avoid it?
Let's take an analogy (I love analogies): if I want to know the law, I ask a judge
Guys, DNS is a global system, there is a DNS server running in every language in the world almost - so you can have in each country whatever you want, and regarding .com and .net - these belongs to US apparently
judges are experts at law.
That's their job
But they do not make the law.
That power is not given to them.
But if you don't have a central authority who administers the names, how do you ensure that only a single person owns a given name?
(Unless you want to go all name-coin, but that's a whole new can of worms)
@CodesInChaos you can have signed contract
22:04
Similarly, if I want to map a name to an IP address or get some casual information on who may have presumably bought a domain, I ask the registrars.. because they are the clerks.
It does not mean that I trust the registrar.
The registrar is not the ultimate definition of the truth in the matter of domains.
they are - they operate the domain protocol - they can make any operation on these objects, including the history, and legally they are responsible, but you can claim domain in court
Ultimately, should issues occur (e.g. a dispute for ownership of a domain, or tracing back a certificate to its owner), we all end up before a judge.
who else is? You have judges who can force registries in their juristiction to force-transfer domains. But apart from that, the registry is the ultimate authortiy.
And in practice everybody, including the CAs asks the registry.
@CodesInChaos And what ? Asking does not mean trusting.
And the CA does not trust the registry.
The CA trusts its own procedures.
And for validating domain ownership all those procedures boil down to "Ask the registry, and believe what it says".
And if you catch it lying, sue the registry
22:09
@CodesInChaos That's not my experience of CA, from both sides (as a CA and as a customer of CA)
Of course there are CA and CA. A cheap one like Startcom verifies that the requester has some basic control of emails.
What else can they do?
Some CA want to get copies of identification (the "K-bis": a French document which is akin to an ID card, for corporations).
For the non domain parts of the certificate, it ultimately boils down to ask the state in where the person is a citizen/company is registered, and for the domain part it boils down to asking the registry
For the domain part, the CA which ask for identification do not really care, although they prefer to do a verification (e.g. the challenge-in-domain procedure) if only to trap typographic errors.
What the CA guarantees is that "this key is really owned by someone who owns that domain", where "guarantee" does NOT mean "we really checked it", but rather "if this is false, then we know who to blame and we have proof for that".
This is the difference between a CA-for-business (where legal retaliation is everything) and a CA-for-spy-networks (where a priori safety is paramount).
The CA "for the Internet" operates as a CA-for-business, and that's rather logical since most of the needs for CA over the Internet is indeed to protect transactions.
It'd probably be a good idea to create two separate certificates for "Owns this domain" and "We know who to sue"
The first one created by the registry, and the second one by traditional CAs
I for one only care about the first one
22:20
@CodesInChaos For anything business-like (e.g. every time I buy something from Amazon), I really prefer the second kind. It is my protection...
For the rest, I don't see why I should relate to an external entity. E.g., when I use ssh to log in my server, I do not use any external PKI, be it DNSSEC or X.509 or anything else.
The next challenge after domains is usernames/email addresses
@CodesInChaos Actually, I presume that registrars themselves will not be over-eager to assume the CA role if it implies any kind of additional liability. Verisign will want to do it because it is already their job. I am not sure about other registrars...
In that case "We know whom to sue" is out of the window entirely, since I like pseudonyms. So we're back to a simple map human readable string to keys.
Essentially we have two separate problems: 1) Map human readable, unique strings to keys. 2) Map keys to real names/ suable entities
@CodesInChaos For emails ? To some extent, this begs the question: if I do not know who you are, what kind of security can we define at all ? If I send you an email, I already do not know who will read it...
For the second part conventional CAs are OK.
22:26
For emails (and also other medias, like this very chat interface), what we want is continuity: when I send a message to "CodesInChaos", I want it to be read by the same person than the previous messages to "CodesInChaos" (whoever he/she may be)
I am just some humanly memorable unique string, called "CodesInChaos@something".
A fingerprint is not humanly memorable
@CodesInChaos Identity Based Encryption is a mathematical solution to this problem
unfortunately, it implies a central authority which knows all the keys (by construction)
the smart thing in IBE is that the central authority needs not be online: it is like a black box through which all emails go, except that the box is virtual and thus cannot block the system due to a hardware failure.
The central authority is still trusted in the intelligence agency sense: it has the power to betray everybody.
IBE implies even more trust than a plain registry or CA
To a large extent, I can use my computer to remember fingerprints. OpenPGP works well in that kind of situation.
The petname solution
zooko's triangle, as always
22:32
I have no problem in exchanging encrypted emails when I deem it important because of possible confidential issues. This implies exchanging some PGP keys when I meet the people.
The real bugger is about getting signed emails -- the kind I could use as proofs in a legal dispute. For that, we need a PKI.
The problem is that verifying 128 bit+ fingerprints is too annoying for average users.
Anyway, I must go buy some food; my fridge is empty.
Guess our main difference is that I'm thinking more in a context where suing people is undesirable.
@CodesInChaos Well, I don't want to get sued -- and if I am, I want some legal protection against it.
I am not keen on suing other people. But I like my business transaction to be protected (i.e. that legal retaliation is possible).
None of this is about confidentiality, which is really a distinct affair.
For business transactions this is desirable
22:39
That's my conclusion: the Internet at large, for all its business-like transactions, requires integrity more than confidentiality (it needs confidentiality mostly to protect the tokens which ensure integrity, e.g. passwords).
For usages which need confidentiality, the case for a global, worldwide identification system is much weaker.
I'd like it if all communications on the internet to be encrypted with reasonable authenticity checks.
I don't want to send confidential data to just anybody; I want to send it to people or entities that I know a priori in some way.
And for business-like transactions you build a system with strong identification on top of that
More often than not, that a priori knowledge supports a local key binding, e.g. login to a SSH server. No need for a global PKI at all for that.
@CodesInChaos I am not sure you can build an a posteriori trust system (the "I know who to sue") over an a priori trust system.
This looks non-trivial to me.
the two problems might be orthogonal.
HTTPS is almost there
22:42
@CodesInChaos except for the certificates, of course...
For example firefox displays the domain and the legal entity
Now we just need two different certs for these two parts
So that everybody can get the "yellow lock" with domain validation
And those who opt into strong identification get the "green lock" with a legal name in addition to that
It's yellow now ? Gee, the fashions change so fast...
ah ok, you are using it as a gradation
And the "green" CA uses the "yellow" certificate from the registry for the domain part, instead of using silly challenges
(Personally I'd also like to switch signatures to hash-trees, but that's a different can of worms)
@CodesInChaos One CA I did business with did not use the registry for that, but the K-bis (i.e. some paper-based documents, totally outside of the Internet)
I must really go now
bye
cu
Still those documents sound more like they attest the legal name of the entity, and not the ownership of the domain.

« first day (625 days earlier)      last day (4553 days later) »