Groups | Search | Server Info | Login | Register
Groups > comp.security.unix > #236
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Newsgroups | comp.security.unix, sci.crypt |
| Subject | Re: Patterns |
| Date | 2024-02-15 18:39 -0800 |
| Organization | A noiseless patient Spider |
| Message-ID | <uqmhtl$3ilmr$1@dont-email.me> (permalink) |
| References | (2 earlier) <uqhgi2$2gjm1$2@dont-email.me> <uqj7eo$2q28i$3@dont-email.me> <uqln3h$2pbms$1@i2pn2.org> <uqlq0s$3f0e5$1@dont-email.me> <uqlrlj$2pi12$1@i2pn2.org> |
Cross-posted to 2 groups.
On 2/15/2024 12:20 PM, Stefan Claas wrote: > Rich wrote: > >> In sci.crypt Stefan Claas <pollux@tilde.club> wrote: >>> Chris M. Thomasson wrote: > >>>> Or even the other way around? If one knows the OTP (Bob and/or >>>> Alice), they can create a special plaintext that generates this >>>> output for fun. >>> >>> How would you do this? >> >> For a traditional, 1940's substution style OTP, it is trivial: >> >> Message: The >> >> Pad: >> >> T=H >> e=r >> h=e >> >> Substitute using the pad, get the encrypted message: Her > > Well, one uses a substitution table, trigraph, etc. and then > a pad to encrypt the message. Otherwise it would be a plain > text encoded message, right? Give me a OPT 3 bytes long. Creating a plaintext that results in a ciphertext of say 123, or ABC is possible... > >>> It had been best if the OP had posted a reference URL ... >> >> I doubt OP found the string at some URL. I suspect the OP was >> trolling. > > That was my thought too and the reason why I did not reply to him > directly. > > Regards > Stefan
Back to comp.security.unix | Previous | Next — Previous in thread | Next in thread | Find similar
Patterns doctor@doctor.nl2k.ab.ca (The Doctor) - 2024-02-13 01:30 +0000
Re: Patterns Jakob Bohm <jb-usenet@wisemo.invalid> - 2024-02-13 16:44 +0100
Re: Patterns "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-13 12:43 -0800
Re: Patterns Rich <rich@example.invalid> - 2024-02-14 04:45 +0000
Re: Patterns "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-14 12:22 -0800
Re: Patterns Stefan Claas <pollux@tilde.club> - 2024-02-15 20:02 +0100
Re: Patterns Rich <rich@example.invalid> - 2024-02-15 19:51 +0000
Re: Patterns Stefan Claas <pollux@tilde.club> - 2024-02-15 21:20 +0100
Re: Patterns "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-15 18:39 -0800
Re: Patterns Stefan Claas <pollux@tilde.club> - 2024-02-16 17:57 +0100
Re: Patterns Stefan Claas <pollux@tilde.club> - 2024-02-16 18:07 +0100
Re: Patterns "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-16 12:26 -0800
Re: Patterns William Unruh <unruh@invalid.ca> - 2024-02-17 00:25 +0000
Re: Patterns "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-16 17:12 -0800
Re: Patterns Rich <rich@example.invalid> - 2024-02-17 05:39 +0000
Re: Patterns William Unruh <unruh@invalid.ca> - 2024-02-18 21:04 +0000
Re: Patterns "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-20 13:09 -0800
Re: Patterns Richard Harnden <richard.nospam@gmail.invalid> - 2024-02-20 21:55 +0000
Re: Patterns "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-20 14:15 -0800
Re: Patterns "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-20 14:17 -0800
Re: Patterns doctor@doctor.nl2k.ab.ca (The Doctor) - 2024-02-20 22:17 +0000
Re: Patterns William Unruh <unruh@invalid.ca> - 2024-02-20 23:47 +0000
Re: Patterns Stefan Claas <pollux@tilde.club> - 2024-02-21 19:24 +0100
Re: Patterns "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-22 16:21 -0800
Re: Patterns Stefan Claas <pollux@tilde.club> - 2024-02-23 15:00 +0100
Re: Patterns Stefan Claas <pollux@tilde.club> - 2024-02-23 19:59 +0100
Re: Patterns "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2024-02-23 12:23 -0800
Re: Patterns Stefan Claas <pollux@tilde.club> - 2024-02-24 20:25 +0100
csiph-web