At 12:38 PM 12/29/03 -0500, Jerrold Leichter wrote:
...
Merkle's knapsack systems (which didn't work out for other reasons) had the
property that the public key was computed directly from the private key.
(The private key had a special form, while the public key was supposed to
look like a random i
| On Dec 27, 2003, at 10:01 AM, Ben Laurie wrote:
| >> "Note that there is no theoretical reason that it should be possible
| >> to figure out the public key given the private key, either, but it so
| >> happens that it is generally possible to do so"
| >> So what's this "generally possible" busine
Jerrold Leichter <[EMAIL PROTECTED]> writes:
> | > "Note that there is no theoretical reason that it should be
> | > possible to figure out the public key given the private key,
> | > either, but it so happens that it is generally possible to
> | > do so"
> | >
> | > So what's this "generally poss
| > "Note that there is no theoretical reason that it should be
| > possible to figure out the public key given the private key,
| > either, but it so happens that it is generally possible to
| > do so"
| >
| > So what's this "generally possible" business about?
|
| Well, AFAIK its always possible,
On Dec 27, 2003, at 10:01 AM, Ben Laurie wrote:
"Note that there is no theoretical reason that it should be possible
to figure out the public key given the private key, either, but it so
happens that it is generally possible to do so"
So what's this "generally possible" business about?
Well, AFAI
Raymond Lillard wrote:
Ben Laurie wrote:
Ian Grigg wrote:
What is the source of the acronym PAIN?
Lynn said:
... A security taxonomy, PAIN:
* privacy (aka thinks like encryption)
* authentication (origin)
* integrity (contents)
* non-repudiation
I.e., its provenance?
Google shows only a few h
Ben Laurie wrote:
Ian Grigg wrote:
What is the source of the acronym PAIN?
Lynn said:
... A security taxonomy, PAIN:
* privacy (aka thinks like encryption)
* authentication (origin)
* integrity (contents)
* non-repudiation
I.e., its provenance?
Google shows only a few hits, indicating
it is not wi
Ian Grigg wrote:
> What is the source of the acronym PAIN?
For what it's worth, I was using PAIN in presentations for Open Market
in 1995. As far as I can recall, I altered it from CAIN (which Greg Rose
mentioned). I won't claim that anyone else picked it up from me (with a
few exceptions that I
At 03:03 AM 12/21/2003, Ian Grigg wrote:
What is the source of the acronym PAIN?
I've seen, for many years, the acronym "CAIN", where the C is
"Confidentiality". I think that was in the Orange Book.
There's also, historically, an R for "Robustness" or "Reliability" in many
military contexts, ins
Ben Laurie wrote:
> http://www.apache-ssl.org/tech-legal.pdf.
Is this unpublished? You might consider
submitting it to WEC:
http://tab.computer.org/tfec/cec04/cfpWEC.html
iang
-
The Cryptography Mailing List
Unsubscribe by se
Ian Grigg wrote:
What is the source of the acronym PAIN?
Lynn said:
... A security taxonomy, PAIN:
* privacy (aka thinks like encryption)
* authentication (origin)
* integrity (contents)
* non-repudiation
I.e., its provenance?
Google shows only a few hits, indicating
it is not widespread.
Pr
On Sat, 2003-12-20 at 09:03, Ian Grigg wrote:
> What is the source of the acronym PAIN?
>
> I.e., its provenance?
>
> Google shows only a few hits, indicating
> it is not widespread.
>
> iang
I just tried
+security +pain +privacy +authentication +integrity
on alta vista and it claims to have
What is the source of the acronym PAIN?
Lynn said:
> ... A security taxonomy, PAIN:
> * privacy (aka thinks like encryption)
> * authentication (origin)
> * integrity (contents)
> * non-repudiation
I.e., its provenance?
Google shows only a few hits, indicating
it is not widespread.
iang
---
13 matches
Mail list logo
