Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: David Entwistle Newsgroups: sci.crypt Subject: Re: Seriation Date: Tue, 4 Feb 2025 01:31:52 -0000 (UTC) Organization: A noiseless patient Spider Lines: 24 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Tue, 04 Feb 2025 02:31:53 +0100 (CET) Injection-Info: dont-email.me; posting-host="dac61c544d0ad6a310837cad2f792638"; logging-data="1633932"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+o67DU1h7XEMYolpo2gZS6" User-Agent: Pan/0.149 (Bellevue; 4c157ba git@gitlab.gnome.org:GNOME/pan.git) Cancel-Lock: sha1:aX+vy4J0OYlO2Qh4mMUO+USDr4I= Bytes: 2241 On Mon, 3 Feb 2025 10:17:24 +0000, Richard Heathfield wrote: > #define UPPER "ABCDEFGHIJKLMNOPQRSTUVWXYZ" > #define LOWER "abcdefghijklmnopqrstuvwxyz" > #define DIGIT "0123456789" > #define PUNCT "!\"$%^&*()_-+={}[]#~'@;:/?.>,<\\|" > > which isn't particularly wide, but any encryption of any of those > characters will *always* produce a character drawn from the same set. > When faced with something *not* from that set, SCOS leaves it unchanged. > So I think I'm right in saying that by the above definition SCOS /is/ > closed. Yes, as I recall, and as a rather sloppy adversary unaware of your implementation, my character set ran from char(33) ! to char(126) ~. I think it was the gap between char(95) _ and char(97) a which caused me the most trouble. char(96) is top left on a QWERTY keyboard. I never use it, but it gets used as an apostrophe in some text on the web. As a result some of my checks failed to do what I expected and I didn't feel confident posting SCOS-based ciphers. Happy days though. -- David Entwistle