Path: ...!news.roellig-ltd.de!open-news-network.org!weretis.net!feeder8.news.weretis.net!newsfeed.bofh.team!paganini.bofh.team!not-for-mail
From: Stefan Claas <pollux@tilde.club>
Newsgroups: sci.crypt
Subject: Re: xorpng
Date: Sun, 5 Jan 2025 23:40:50 +0100
Organization: To protect and to server
Message-ID: <vlf1pk$s3d3$1@paganini.bofh.team>
References: <vl243l$3jkpe$1@paganini.bofh.team> <vl7ivj$3k1t8$1@dont-email.me> <vl8urh$8hto$1@paganini.bofh.team> <vl9mkg$3796$5@dont-email.me> <vlbtbm$i8qt$1@paganini.bofh.team> <vlc7ia$k8so$5@dont-email.me> <vlc80o$ipdu$1@paganini.bofh.team> <vlc891$k8s5$2@dont-email.me> <vlc8om$k8s5$3@dont-email.me> <vlc9d8$irra$1@paganini.bofh.team> <vlcahc$ks00$1@dont-email.me> <vlcbki$j00g$1@paganini.bofh.team> <vlccrh$lb6a$1@dont-email.me> <vlchr0$j921$1@paganini.bofh.team> <vlcivh$md8n$2@dont-email.me> <vlcjan$oal1$2@paganini.bofh.team> <vlcu54$o46f$1@dont-email.me> <vldj3j$pqvr$1@paganini.bofh.team> <vlev0b$17khf$1@dont-email.me> <vlf0lu$s1t0$2@paganini.bofh.team> <vlf1be$17khf$8@dont-email.me>
Mime-Version: 1.0
Injection-Date: Sun, 5 Jan 2025 22:40:52 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="920995"; posting-host="P19FF9OOayxo5XAXCSdPUg.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A";
User-Agent: flnews/1.3.0pre29 (for GNU/Linux)
Cancel-Lock: sha1:XvucRAya2TvqWvnh58xPT9fpez0=
X-Ed25519-Pub: c0ffee5a36e581eb10f60b2831b3cdb955d2e7ef680dd282a8d43ad8b84b357a
X-Notice: Filtered by postfilter v. 0.9.3
X-Ed25519-Sig: 6880c90854932018adeaceb5203874b0f40647174e39dd854d382006740a46c9
 8807c4028c5e9172e957158f9c827e598a0f97eb9726305f0c89aa62c72ecc04
X-Date: It's Sun Sep 11450 11:40:50 PM CET 1993, the September that never ends.
Bytes: 3950
Lines: 51

Chris M. Thomasson wrote:
> On 1/5/2025 2:21 PM, Stefan Claas wrote:
> > Chris M. Thomasson wrote:
> > > On 1/5/2025 1:24 AM, Stefan Claas wrote:
> > > > Chris M. Thomasson wrote:
> > > > > On 1/4/2025 4:21 PM, Stefan Claas wrote:
> > > > > > Rich wrote:
> > > > > > 
> > > > > > > If instead you mean some kind of "special, PNG aware, encryptor that
> > > > > > > only encrypted the bitmap data of a PNG", but left the file as
> > > > > > > otherwise a proper PNG image structure, then that is slightly tricky
> > > > > > > (and an algorithm that is only useful for PNG's alone).
> > > > > > 
> > > > > > Yes, this is what I mean.
> > > > > > 
> > > > > 
> > > > > Well, take a good ol' bag o' bytes and turn it into a valid png?
> > > > 
> > > > No, encrypt a .png, so that an encrypted noise image comes out.
> > > > 
> > > 
> > > Are you talking about encrypting something A. Taking the resulting
> > > ciphertext B and creating a new png C out of B. The png C will have B a
> > > a visual entity. Now, since C has the ciphertext B in it, we can decrypt
> > > that data back into A.
> > > 
> > > Is this what you are doing?
> > 
> > I am talking about .png image encryption. I got it working for ppm (P6)
> > files, so that when you have created with Gimp a ppm (raw) file it will
> > then be encrypted with a password and salt and results in a noise image.
> > 
> > Have you not seen my online folder with the example ... ???
> > 
> 
> The PPM still needs it proper format to be a, as you say, noise image?

Are you not reading the complete thread, in which I have replied to Rich?
 
> I have worked a lot with PPM's. Keep in mind that storing ciphertext for
> any file, even the original PPM, JPG, ect, can be stored in another PPM
> for sure. So, the resulting PPM will have the payload of any file,
> another PPM, no problem. Then we can look at the payload as an image on
> the screen.

Arrgh ...  I am not talking about ciphertext or payload, I am talking about
*Image Encryption*! I had that already in the mid 90s as Photoshop plug-in,
from Japan.

-- 
Regards
Stefan