| Deutsch English Français Italiano |
|
<vlfjjb$1ande$6@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Rich <rich@example.invalid>
Newsgroups: sci.crypt
Subject: Re: xorpng
Date: Mon, 6 Jan 2025 03:44:43 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 33
Message-ID: <vlfjjb$1ande$6@dont-email.me>
References: <vl243l$3jkpe$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> <vld86b$tdna$1@dont-email.me> <vldj6q$pqvr$2@paganini.bofh.team> <vlevq2$17khf$4@dont-email.me>
Injection-Date: Mon, 06 Jan 2025 04:44:44 +0100 (CET)
Injection-Info: dont-email.me; posting-host="aacc148df4532970fbc7162b818dee32";
logging-data="1400238"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/hgRn6se/hX+g+q0Zw4KaA"
User-Agent: tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
Cancel-Lock: sha1:HhyxAycqXLE1oHaD151Xz10zJkE=
Bytes: 2648
Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:
> On 1/5/2025 1:25 AM, Stefan Claas wrote:
>> Rich wrote:
>>> Stefan Claas <pollux@tilde.club> 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.
>>>
>>> Which brings up the question of: why?
>>>
>>> Why go to the trouble to create an encryptor that is specalized for
>>> just encrypting the internal bitmap data within a PNG, leaving the rest
>>> as a PNG file, when a generic "byte stream" encryptor will encrypt the
>>> entire PNG with no extra effort?
>>
>> To make more content as allowed postable on social media, like X.
>>
>
> Well, posting a png to say, facebook, well... It's probablly going to
> turn it into a jpg... This can ruin the embedded ciphertext in the png
> image...
ebay seems to recently be converting jpeg's into webp's after one
uploads them, which would also alter the stored bitmap (as webp is
lossy). Although given the volume of image data they handle, if webp
is even 5% smaller than jpegs, it becomes a huge storage savings for
them.