Hi all,

a little test to convert cipher text to
..SVG poly lines and back.

The first image used my adiantum cipher,
the second my ff1 cipher and the third
image is openssl rand -hex 32.

Hope you like the idea!

The images can be found in the german (binary)
Usenet group (avialable for all, I guess)
de.alt.dateien.misc, with the following M-IDs:

Subject: adantium cipher
<urus5n$1qce4$1@stefan.eternal-september.org>

Subject: ff1 cipher
<urus7a$1qce4$2@stefan.eternal-september.org>

Subject: openssl rand -hex
<urus8h$1qce4$3@stefan.eternal-september.org>

Regards
Stefan

P.S. I think we can use this Newsgroup for all
our binary crypto output, or files, because it
says dateien(=files).misc ... ;-)

--
----Ed25519 Signature----
e3117be00a0f16bdf1663ef9e72a75fed2b7535cec0f1bb7832789b537dc523d
4120ad6c0aabef791a9023997acf2487e934a12a12c6f19ddf3fcc6fa67dad0b

Stefan Claas wrote:

> Hi all,
>
> a little test to convert cipher text to
> .SVG poly lines and back.
>
> The first image used my adiantum cipher,
> the second my ff1 cipher and the third
> image is openssl rand -hex 32.

Here is how the images look, as .png:

https://postimg.cc/gallery/hhSHWpF

Regards
Stefan
--
----Ed25519 Signature----
dd5747f79f72ac3714febab9608831707f5045fdd9805d2e241bf965d33fe0a3
2f895eb3b435cd1aebc57c3acae676f9b3c9fb314a2e0c8b18ae8392d85d3207

On 02/03/2024 09:55, Stefan Claas wrote:

>
> P.S. I think we can use this Newsgroup for all
> our binary crypto output, or files, because it
> says dateien(=files).misc ... ;-)
>

No, please, no binaries.

For your reference, records indicate that
Stefan Claas <pollux@tilde.club> wrote:

> a little test to convert cipher text to
> .SVG poly lines and back.

Back when *owning* DVDs were a thing:

<https://en.wikipedia.org/wiki/AACS_encryption_key_controversy>

This image was cooked up with a similar idea:

<https://datafetish.com/images/sinister_plot.jpg>

I like the update of using SVG. It makes it easier to get data out, but
also might make it more obvious that there *is* data to get out. And,
honestly, there is so much room for steganography in SVG that a proper
encoder could pack it in much more densely than simple line drawings.

--
"Also . . . I can kill you with my brain."
River Tam, Trash, Firefly

Doc O'Leary , wrote:

> For your reference, records indicate that
> Stefan Claas <pollux@tilde.club> wrote:
>
> > a little test to convert cipher text to
> > .SVG poly lines and back.
>
> Back when *owning* DVDs were a thing:
>
> <https://en.wikipedia.org/wiki/AACS_encryption_key_controversy>
>
> This image was cooked up with a similar idea:
>
> <https://datafetish.com/images/sinister_plot.jpg>

Ah, nice! :-)

> I like the update of using SVG. It makes it easier to get data out,
> but also might make it more obvious that there *is* data to get out.

Yes me too, but how if one embeds the vector graphic in another .svg file
like an invisible watermark (a transparent object). Maybe worth to
explore?

> And, honestly, there is so much room for steganography in SVG that a
> proper encoder could pack it in much more densely than simple line
> drawings.

I just found this example:

https://github.com/japplebaum/svgsteg

Regards
Stefan
--
----Ed25519 Signature----
8c98dfe11de6e415362446a7f6b0c843c9d257769ca5d022cc233a8c3049c572
0494f6ea837777c5e6796208af32dca6ee7a81e38f317733e76f025fe6fbbb02

Richard Harnden wrote:

> On 02/03/2024 09:55, Stefan Claas wrote:
>
> >
> > P.S. I think we can use this Newsgroup for all
> > our binary crypto output, or files, because it
> > says dateien(=files).misc ... ;-)
> >
>
> No, please, no binaries.

I did non mean to post there binary versions of programs,
but binary output, like an encrypted message, or image is
fine there, I would say.

Regards
Stefan
--
----Ed25519 Signature----
ede2027a80d9532ee98c89df496114e19c613877175d39c48df01167ee8aa260
574b768a6876ec9edc32edf01c79186a9acf07c3759bca6b7836ea02e955d90e

https://archive.org/details/cryptographylang00lang - see book pages 8
and 9 (PDF pages 20 and 21).

On 2024-03-02 10:55, Stefan Claas wrote:
>
> a little test to convert cipher text to
> ..SVG poly lines and back.
>

--

-----BEGIN PGP PUBLIC KEY FINGERPRINT-----
5745 807C 2B82 14D8 AB06 422C 8876 5DFC 2A51 778C
------END PGP PUBLIC KEY FINGERPRINT------

Chax Plore wrote:

>
> https://archive.org/details/cryptographylang00lang - see book pages 8
> and 9 (PDF pages 20 and 21).

Nice! Thank you!

Regards
Stefan
--
----Ed25519 Signature----
233a18227d82d23f3804f47572051e2c7426ac773cae291db73e25e4e3f7083c
1ba40429a7c75e67207c3ae551fa2ef7153d6695c891a579c10b03c61f3ea501

For your reference, records indicate that
Stefan Claas <pollux@tilde.club> wrote:

> Yes me too, but how if one embeds the vector graphic in another .svg file
> like an invisible watermark (a transparent object). Maybe worth to
> explore?

Once you just start jamming data into “out of band” spaces in file formats
it doesn’t feel as interesting an exercise. It’s also a big red flag to
anyone who *is* suspiciously inspecting the contents.

> https://github.com/japplebaum/svgsteg

I’ve also never been a big fan of using only one bit of each number like
that. To my thinking, it doesn’t make much sense to have an
“imperceptible” difference to some reference file, because that inherently
introduces a possible validity check. “Nice image of Tux you’ve got here.
Any reason it doesn’t hash to the publicly available version that everyone
else uses? Let’s continue this investigation in a more formal
setting . . .”

I was thinking of something that used as many bits as possible. The
“image” may render more like a Jackson Pollock painting or some other
abstract artwork, but the numbers/data there in plain sight, and *meant*
to be seen, so you couldn’t be accused of hiding anything. I mean, yeah,
they could just as easily lock you up if they wanted to, but I think the
plausible deniability is greater when the data is as unstructured as
possible.

--
"Also . . . I can kill you with my brain."
River Tam, Trash, Firefly

Doc O'Leary , wrote:
> I was thinking of something that used as many bits as possible. The
> “image” may render more like a Jackson Pollock painting or some other
> abstract artwork, but the numbers/data there in plain sight, and
> *meant* to be seen, so you couldn’t be accused of hiding anything. I
> mean, yeah, they could just as easily lock you up if they wanted to,
> but I think the plausible deniability is greater when the data is as
> unstructured as possible.

I tried with colored rectangles, but then when decoding not all data
was written. I then changed to circles with a random fill color and
black border and now it works. The program tells the user that the hex
input string must be of even pairs (for x,y coordinates) and if odd it
prints an error message to stdout.

Regards
Stefan
--
----Ed25519 Signature----
8a209aa55569ace635554dbde9cd94947e044bd65255949e66218b70e8f6aa80
e4e4325180b6f1d1de24c0cb7573f916f771dc1739f9c0a8b6ef9a1e9bc6be08

Stefan Claas wrote:

> I tried with colored rectangles, but then when decoding not all data
> was written. I then changed to circles with a random fill color and
> black border and now it works. The program tells the user that the hex
> input string must be of even pairs (for x,y coordinates) and if odd it
> prints an error message to stdout.

Sample output:

(The encoded message is: Zwölf Boxkämpfer jagen Viktor quer über den
großen Sylter Deich.)

Usenet Group: de.alt.dateien.misc
M-ID: <us4su4$3832i$1@stefan.eternal-september.org>

Regards
Stefan
--
----Ed25519 Signature----
9b1ae01a38e1f532c50f6033a77ba0acf2272bfe26398e5c0b71770f22c2d772
007345c1bc5a9a7544a1e56d1fb0da3831a2a5c7100d1781bcb8b5327c4f7c04