I skimmed a few of those and noticed two submissions for signature
issues: RyanCastellucci, and AleksanderEssex. Is it normal for people
to find issues with the signing/verification process or is this just
coincidence?
On Sat, Mar 21, 2015 at 5:44 PM, Adam Caudill a...@adamcaudill.com wrote:
FYI
On 21 Mar 2015, at 22:24, Lee wrote:
On 3/21/15, Jeffrey Goldberg jeff...@goldmark.org wrote:
(1) the file isn't secret
But the fact that I'm using it as my one-time pad is. Why isn't that
good enough?
As others have already answered, your key is knowledge of which
publicly available file
On 21 Mar 2015 21:17 -0700, from sch...@eff.org (Seth David Schoen):
*True random pad*: Attacker doesn't know whether pad k₁ is actually more
likely than pad k₂, if (c ⊕ k₁) and (c ⊕ k₂) both appear to be equally
plausible plaintexts.
*Choosing a meaningful file but keeping secret which one
agreed.
On 3/21/2015 5:18 PM, John Levine wrote:
Would a commonly available large binary file make a good one-time pad?
Something like ubuntu-14.10-desktop-amd64.iso12 maybe..
Unlkely for two reasons. One is that the point of a one-time pad is
that only the sender and recipient are supposed
On 22 Mar 2015 09:36 -0500, from jeff...@goldmark.org (Jeffrey Goldberg):
There are good crypto systems in use which generate pseudo-random
pads from keys that are 128 (or 256) bits in length. But these are
– at best – no better than the length of their keys.
Which is, admittedly, _quite good
On 22 Mar 2015 10:50 -0400, from givo...@gmx.com (Givon Zirkind):
I was tempted by the promise of software to run a one-time pad on my
machine. I am a fool and I fall upon my own sword.
An unauthenticated one-time pad is trivial to implement; it's
literally a few lines of code in any
If we haven't argued it enough by now, he'll never get it. Either way I would
ask people to stop this discussion before I have to unsubscribe from yet
another once-useful discussion list.
Greg.
Phone: +1 619 890 8236
GPG/PGP: 1081A37C 232B EC8F 44C6 C853 D68F E107 E6BF CD2F 1081 A37C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Here's an optimization:
* Assume you have a decent One Time Pad generator.
* Assume you have a secure pad delivery system.
* Assume it is reasonably low-latency and high-volume. Say somewhere between
Usenet and the modern Internet.
Now then --
On 22 Mar 2015, at 9:48, Michael Kjörling wrote:
On 22 Mar 2015 09:36 -0500, from jeff...@goldmark.org (Jeffrey
Goldberg):
There are good crypto systems in use which generate pseudo-random
pads from keys that are 128 (or 256) bits in length. But these are
– at best – no better than the length
Right. An ISO file is a bad choice - too many zeros machine code
isn't very random. But what about something like an MP3, OGV or some
other compressed file?
No!
The requirements for the Vernam cipher are very simple:
- the pad must be random
- the pad must not be reused
- the pad must
whos to say?
we're jus trapt on erf together.
On Mar 21, 2015 11:37 PM, Seth David Schoen sch...@eff.org wrote:
Lee writes:
On 3/21/15, Jeffrey Goldberg jeff...@goldmark.org wrote:
[Apologies for quoting badly]
No! A thousand times no.
(1) the file isn't secret
But the
11 matches
Mail list logo
