Well, Python has the @property decorator that achieves the same thing without changing the signature and without generating massive amounts of boilerplate code.
The CA maintains a copy of your private key? Are you 100% certain of this?
My understanding of the way it worked was that the CA *generated* the private key, and, more importantly, signed the certificate and keypair for you, but that only you (and anyone you're dumb enough, or trusting enough, to give it to) actually has a copy of the private key...
No, nobody gets to see your private key. When you're e.g. buying an SSL certificate, you generate a key pair plus a CSR, which contains the public key and other data, like your name (cert subject). Then you send only the.csr file to the CA. They have no business knowing your private key and it's only your problem if the signed CSR (i.e. a certificate file) doesn't match your key.
And how do you ensure that? Without some way to ensure that, it seems to me that you are practicing "faith based" security. Because they never see it? They don't generate it, as somebody upthread said. You hand them a CSR (certificate signature request, essentially the public key) and they send you a certificate (public key + signature). Never ever do they get to see your private key.
Slashdot Mirror
It's being censored.
md5sum -c var/lib/dpkg/info/foo.md5sums
There's also a tool called debsums which does roughly the same. So that gets you at least half way there.
Well, Python has the @property decorator that achieves the same thing without changing the signature and without generating massive amounts of boilerplate code.
Debian does not use Redhat kernels. Two different distributions, packing systems and philosophies.
Debian admins, however, do cherry-pick relevant fixes backported by RedHat to older kernels. Or rather used to do.
Blackberry.
What's incorrect about referring to mx records instead of specifying ip addresses by hand?
587 actually, and usually servers accept auth also on 25
Mah-tish-chick would be close enough, I guess.
Secretaries get free lunches, flowers, cards, etc. so why not Sys Admins?
Tits.
If you're looking at the cheap end, forget Java. Hosting PHP is way cheaper (in some part, due to its sheer popularity).
Was that so bad?
What, exactly, are you thinking that | cat on the end is adding?
!isatty(1) inside ls, influences formatting (like ls -1).
"gluck, gluck, gluck" is the sound you hear when you repeatedly slap a filled-up douchebag against the sidewalk? Seriously?
How about, "Ouch, ouch, ouch!"
You're doing it wrong.
datasorting for I new one our overlords! welcome
Read up on readline (google food: inputrc)
Were you dictating?
NinaFS?
ORLY?
Closures work out of the box, too. Oh, and the new /. interface sucks balls.
I'm sure there's some JavaScript out there to help you :)
Hey, I always wanted to stick a '#!/usr/bin/perl' at the beginning of sendmail.cf, just to see what happens :)
/JAPH
The CA maintains a copy of your private key? Are you 100% certain of this?
My understanding of the way it worked was that the CA *generated* the private key, and, more importantly, signed the certificate and keypair for you, but that only you (and anyone you're dumb enough, or trusting enough, to give it to) actually has a copy of the private key...
No, nobody gets to see your private key. When you're e.g. buying an SSL certificate, you generate a key pair plus a CSR, which contains the public key and other data, like your name (cert subject). Then you send only theWow, what a way to miss the point.
Just not your day, man.