Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | "Chris M. Thomasson" <nospam@nospam.nospam> |
|---|---|
| Newsgroups | sci.crypt |
| Subject | Re: Introduction me |
| Date | 2015-10-15 12:13 -0700 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <mvottj$r0e$1@speranza.aioe.org> (permalink) |
| References | (1 earlier) <mvjtg0$tjc$1@speranza.aioe.org> <mvk0hh$mf0$1@dont-email.me> <mvmiv7$oqq$1@speranza.aioe.org> <mvmjd6$dtv$1@dont-email.me> <mvo57c$ubk$1@dont-email.me> |
>"Richard Heathfield" wrote in message news:mvo57c$ubk$1@dont-email.me... >>On 14/10/15 23:02, Rich wrote: >>> Chris M. Thomasson <nospam@nospam.nospam> wrote: [...] >>> FWIW, I converted the ciphertext into hexbytes in ASCII because I >>> liked the way Richard Heathfield presented his ciphertext challenges >>> to this group. It worked great! >> >> It was necessary for posting to the group to insure that various NNTP >> transports and viewers did not corrupt the data. > The advantages of the method I used were: [snip advantages of hexbytes in ASCII] > The disadvantage was that it takes three bytes (two hexits and a space) to > represent one byte. This isn't ciphertext inflation as such, because it's > only the rather naff transport mechanism that's to blame, not the > algorithm, and the inflation gets punctured by the tool that reconstructs > the binary from the hex data. Exactly right. The inflation in not the fault of the algorithm, its part of the “convenience” of showing the ciphertext in ASCII hexbytes. I not not need to add the space between each hexbyte, but it sure makes them easier to see individually! ;^) > >> What do you think about using a checkbox that allows a user to generate > >> ASCII hexbytes or raw output dumped into the ciphertext textarea? > > > > A very bad idea. > Doesn't that rather depend on his objectives? If his intent is, say, for > people to grab the ciphertext so that they can (literally) have a crack at > it on their home machines, then the above may well make this easier for > them, which would be a good thing, right? It sure beats copying and > pasting 8947h ry4ifabdklf r4yu89w4 $^&*( from an output window. This is exactly why I did it Richard, and I am sorry for not making this clear. ;^( Also, I am worried about a “cut-and-paste” keeping all of the non-printable characters, such as null bytes from a textarea in HTML5. I need to test this by filling a textarea A with a bunch of nulls and other non-printable characters, then copy it over to another textarea B and validating that A = B. My Javascript and HTML5 skills are a bit rusty! ;^/ Therefore, I think adding a checkbox wrt displaying the ciphertext in ASCII hexbytes is a good thing? Humm...
Back to sci.crypt | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Introduction me eaglesondouglas@gmail.com - 2015-10-12 10:26 -0700
Re: Introduction me Rich <rich@example.invalid> - 2015-10-12 17:45 +0000
Re: Introduction me eaglesondouglas@gmail.com - 2015-10-13 08:28 -0700
Re: Introduction me William Unruh <unruh@invalid.ca> - 2015-10-13 16:09 +0000
Re: Introduction me Rich <rich@example.invalid> - 2015-10-13 16:19 +0000
Re: Introduction me William Unruh <unruh@invalid.ca> - 2015-10-12 17:46 +0000
Re: Introduction me Karl-Uwe Frank <karl.frank@freecx.co.uk> - 2015-10-12 21:19 +0200
Re: Introduction me Rich <rich@example.invalid> - 2015-10-12 20:24 +0000
Re: Introduction me Johan Wevers <johanw@vulcan.xs4all.nl> - 2015-10-13 10:08 +0200
Re: Introduction me Rich <rich@example.invalid> - 2015-10-13 16:20 +0000
Re: Introduction me Rich <rich@example.invalid> - 2015-10-13 16:24 +0000
Re: Introduction me Nomen Nescio <nobody@dizum.com> - 2015-10-14 16:20 +0200
Re: Introduction me Ribeiro Alvo <ribeiroalvo@gmail.com> - 2015-10-13 03:58 -0700
Re: Introduction me "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-10-13 14:35 -0700
Re: Introduction me William Unruh <unruh@invalid.ca> - 2015-10-13 22:28 +0000
Re: Introduction me "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-10-14 14:54 -0700
Re: Introduction me Rich <rich@example.invalid> - 2015-10-14 22:02 +0000
Re: Introduction me gordonb.loovx@burditt.org (Gordon Burditt) - 2015-10-15 02:39 -0500
Re: Introduction me William Unruh <unruh@invalid.ca> - 2015-10-15 08:00 +0000
Re: Introduction me Richard Heathfield <rjh@cpax.org.uk> - 2015-10-15 13:14 +0100
Re: Introduction me "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-10-15 12:13 -0700
Re: Introduction me "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-10-15 12:35 -0700
Re: Introduction me Rich <rich@example.invalid> - 2015-10-15 22:34 +0000
Re: Introduction me "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-10-16 01:15 -0700
Re: Introduction me William Unruh <unruh@invalid.ca> - 2015-10-16 18:02 +0000
Re: Introduction me wizzofozz <oscxxxxxxxaas@gmail.com> - 2015-10-16 20:30 +0200
Re: Introduction me Rich <rich@example.invalid> - 2015-10-16 20:09 +0000
Re: Introduction me "Chris M. Thomasson" <nospam@nospam.nospam> - 2015-10-19 14:45 -0700
Re: Introduction me William Unruh <unruh@invalid.ca> - 2015-10-15 23:16 +0000
Re: Introduction me William Unruh <unruh@invalid.ca> - 2015-10-14 22:48 +0000
Re: Introduction me eaglesondouglas@gmail.com - 2015-10-14 08:03 -0700
Re: Introduction me omnilobe@gmail.com - 2015-10-14 10:23 -0700
Re: Introduction me William Unruh <unruh@invalid.ca> - 2015-10-14 17:34 +0000
Re: Introduction me eaglesondouglas@gmail.com - 2015-10-15 07:21 -0700
Re: Introduction me Jeffrey Goldberg <nobody@goldmark.org> - 2015-10-18 12:56 -0500
Re: Introduction me MM <mrvmurray@gmail.com> - 2015-10-18 11:44 -0700
Re: Introduction me rpw3@rpw3.org (Rob Warnock) - 2015-10-18 18:57 +0000
Re: Introduction me Jeffrey Goldberg <nobody@goldmark.org> - 2015-10-19 17:52 -0500
csiph-web