Rocksolid Light

News from da outaworlds

mail  files  register  groups  login

Message-ID:  

BOFH excuse #347: The rubber band broke

sci / sci.crypt / Re: [base64+]

SubjectAuthor
* [base64+]Stefan Claas
`* Re: [base64+]Rich
 `* Re: [base64+]Stefan Claas
  `- Re: [base64+]Rich

1
Subject: [base64+]
From: Stefan Claas
Newsgroups: sci.crypt
Organization: To protect and to server
Date: Mon, 30 Dec 2024 14:21 UTC
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!newsfeed.bofh.team!paganini.bofh.team!not-for-mail
From: pollux@tilde.club (Stefan Claas)
Newsgroups: sci.crypt
Subject: [base64+]
Date: Mon, 30 Dec 2024 15:21:31 +0100
Organization: To protect and to server
Message-ID: <vkua9d$33gds$3@paganini.bofh.team>
Mime-Version: 1.0
Injection-Date: Mon, 30 Dec 2024 14:21:33 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="3260860"; posting-host="lXbPTgCmfq3Yw1jDpgjSEQ.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:fscUWOwyjoZNxFNS2Rrqget3Qyk=
X-Notice: Filtered by postfilter v. 0.9.3
X-Ed25519-Sig: ff3b71fb0a9f719b0acff3a7f870239c1adb79df536ec43f987eb89c823381ad
088faa7727c37838a9f49cc55bb95719398241f007d85d47f4eacd387fdc0d09
X-Date: It's Mon Sep 11444 03:21:31 PM CET 1993, the September that never ends.
X-Ed25519-Pub: c0ffee5a36e581eb10f60b2831b3cdb955d2e7ef680dd282a8d43ad8b84b357a
View all headers

Hi all,

while no encryption, this is an enhanced version of a standard
base64 encoder/decoder.

It writes the filename, file size and SHA256 hashsum as a Header,
like in this example:

bart.jpg
2837
8f17bcf334121fe993a48c61179d09c18c25aa2dac1c9c8e6ccef8f860e68997

/9j/4AAQSkZJRgABAQEASABIAAD/2wBDAAEBAQEBAQEBAQEBAQEBAQIBAQEBAQIB
AQECAgICAgICAgIDAwQDAwMDAwICAwQDAwQEBAQEAgMFBQQEBQQEBAT/2wBDAQEB
AQEBAQIBAQIEAwIDBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQE
BAQEBAQEBAQEBAQEBAT/wgARCAAwADADAREAAhEBAxEB/8QAGgABAQADAQEAAAAA
AAAAAAAACAAEBQcCCf/EABwBAAIDAAMBAAAAAAAAAAAAAAAGBQcIAQIDBP/aAAwD
[...]

When decoding one no longer needs to provide a filename, because
it is detected and the file is automatically written in the current
directory.

$ base64+ -d < bart.txt
Original size: 2837 bytes
SHA256: 8f17bcf334121fe993a48c61179d09c18c25aa2dac1c9c8e6ccef8f860e68997
Matches original: true

Hope you like base64+!

https://github.com/706f6c6c7578/base64-plus

--
Regards
Stefan

Subject: Re: [base64+]
From: Rich
Newsgroups: sci.crypt
Organization: A noiseless patient Spider
Date: Mon, 30 Dec 2024 20:37 UTC
References: 1
Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: rich@example.invalid (Rich)
Newsgroups: sci.crypt
Subject: Re: [base64+]
Date: Mon, 30 Dec 2024 20:37:52 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <vkv0b0$1pi60$2@dont-email.me>
References: <vkua9d$33gds$3@paganini.bofh.team>
Injection-Date: Mon, 30 Dec 2024 21:37:53 +0100 (CET)
Injection-Info: dont-email.me; posting-host="1830077b5b0fbda0c8b476fd9564eff1";
logging-data="1886400"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/OnYaXep3fks0XqG/fhVpt"
User-Agent: tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
Cancel-Lock: sha1:J7vO+X9a+EChmN218ZqfT03T5mk=
View all headers

Stefan Claas <pollux@tilde.club> wrote:
> Hi all,
>
> while no encryption, this is an enhanced version of a standard
> base64 encoder/decoder.
>
> It writes the filename, file size and SHA256 hashsum as a Header,
> like in this example:

So, somewhat like an 'extended' uuencode.

https://en.wikipedia.org/wiki/Uuencoding

Subject: Re: [base64+]
From: Stefan Claas
Newsgroups: sci.crypt
Organization: To protect and to server
Date: Tue, 31 Dec 2024 12:45 UTC
References: 1 2
Path: news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!newsfeed.bofh.team!paganini.bofh.team!not-for-mail
From: pollux@tilde.club (Stefan Claas)
Newsgroups: sci.crypt
Subject: Re: [base64+]
Date: Tue, 31 Dec 2024 13:45:49 +0100
Organization: To protect and to server
Message-ID: <vl0p20$3cemr$2@paganini.bofh.team>
References: <vkua9d$33gds$3@paganini.bofh.team> <vkv0b0$1pi60$2@dont-email.me>
Mime-Version: 1.0
Injection-Date: Tue, 31 Dec 2024 12:45:52 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="3554011"; posting-host="6lqOwJyxRLkv94k9QBgAmg.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:HC2fkC+/PxmlQfG80BL8yUn06h4=
X-Notice: Filtered by postfilter v. 0.9.3
X-Ed25519-Pub: c0ffee5a36e581eb10f60b2831b3cdb955d2e7ef680dd282a8d43ad8b84b357a
X-Date: It's Tue Sep 11445 01:45:49 PM CET 1993, the September that never ends.
X-Ed25519-Sig: 8ed439e644933c0335b8e3de2a235de9000fefce89368dc5a432257c662a4a47
beb36d58387d242700eb4281b81218286a0ec3bfdc08d0448079a0f88cfc8b0c
View all headers

Rich wrote:
> Stefan Claas <pollux@tilde.club> wrote:
> > Hi all,
> >
> > while no encryption, this is an enhanced version of a standard
> > base64 encoder/decoder.
> >
> > It writes the filename, file size and SHA256 hashsum as a Header,
> > like in this example:
>
> So, somewhat like an 'extended' uuencode.
>
> https://en.wikipedia.org/wiki/Uuencoding

Well, yes. :-)

I wonder why nobody else came up with the idea of base64+ in the past.

--
Happy New Year 2025
Stefan

Subject: Re: [base64+]
From: Rich
Newsgroups: sci.crypt
Organization: A noiseless patient Spider
Date: Tue, 31 Dec 2024 23:25 UTC
References: 1 2 3
Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: rich@example.invalid (Rich)
Newsgroups: sci.crypt
Subject: Re: [base64+]
Date: Tue, 31 Dec 2024 23:25:50 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 40
Message-ID: <vl1uhu$2ef4n$2@dont-email.me>
References: <vkua9d$33gds$3@paganini.bofh.team> <vkv0b0$1pi60$2@dont-email.me> <vl0p20$3cemr$2@paganini.bofh.team>
Injection-Date: Wed, 01 Jan 2025 00:25:51 +0100 (CET)
Injection-Info: dont-email.me; posting-host="8c10bf53f7fd2c88970ece96e6e64bf0";
logging-data="2571415"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19GNiVk1O3Khuq8y4T+68qx"
User-Agent: tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64))
Cancel-Lock: sha1:Ja9EWgKrZHa3ZEloAN9xmMlfR7c=
View all headers

Stefan Claas <pollux@tilde.club> wrote:
> Rich wrote:
>> Stefan Claas <pollux@tilde.club> wrote:
>> > Hi all,
>> >
>> > while no encryption, this is an enhanced version of a standard
>> > base64 encoder/decoder.
>> >
>> > It writes the filename, file size and SHA256 hashsum as a Header,
>> > like in this example:
>>
>> So, somewhat like an 'extended' uuencode.
>>
>> https://en.wikipedia.org/wiki/Uuencoding
>
> Well, yes. :-)
>
> I wonder why nobody else came up with the idea of base64+ in the past.

Several ideas (all mostly guesses):

1) Uuencode already exists (although, granted, your base64+ goes beyond
what Uuencode does in providing a hash over the data)

2) yenc exists <https://en.wikipedia.org/wiki/YEnc>

3) par2 exists (and goes far beyond base64+ in allowing recovery of
broken files) <https://en.wikipedia.org/wiki/Parchive>

4) (I feel this one is most likely) The 99.9'th percentile of computer
user has no idea what base64 even is, and all the mechanics are hidden
from them behind their email UI. They simply drag and drop a file onto
their email client, and it becomes an "attachment" (and looks to them
to be a "file" via UI trickery) and they don't know, nor care, about
the how/why. MIME specifies base64 encoding for the attached files,
and includes features for including the filenames and sizes (which is
how the "attached files" can appear to be "files" to the users), and so
99.9% of the "need" has been met. So no one is worried about meeting
the missing 0.1%.

1

rocksolid light 0.9.8
clearnet tor