| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 42 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 02:03:11 |
| Calls: | 220 |
| Calls today: | 1 |
| Files: | 824 |
| Messages: | 121,544 |
| Posted today: | 6 |
Chris M. Thomasson wrote:a4f7cb5f3c7a0957d9517ad740b06a5d13a02e0affcb2882f700e388eec93f650c92e3b451915f04d2c0dd45f13e1ad5bfad03552937e2ff2602ec88dc3ccdce8b3076ec0addad4b41123297542709c292bb836850057363dbd2e7c7eb6f237db3e3d3d891600c880b92bbbe0b293a34bbc4994c81dba3deef421247965b01e
On 9/20/2024 4:17 AM, Stefan Claas wrote:
I came up with the following idea.
Register a webpage at nekoweb.org, use an API key
and send encrypted messages to the web page, which
later Bob and Alice can decrypt.[...]
To decrypt use the default key, except click on the SHA512 radio button, then click decrypt:
http://fractallife247.com/test/hmac_cipher/ver_0_0_0_1?ct_hmac_cipher=
Hi Chris, please reply here in plaintext. I do not have the passwort anymore.
On 10/18/2024 12:10 PM, Stefan Claas wrote:
:^) Fwiw, I never compiled any Go code in my life. C and Pascal, yup,
but not Go. Fwiw, I am friends with somebody who is/was on the Go team. Not sure if he still works for Google. I have not talked to him in some months.
Oh, interesting. :-) Go is IMHO pretty cool, because it has so many libraries,
you can find on GitHub and most new and cool crypto stuff etc. is either written in Go or Rust.
He is a very smart person and I feel great to be able to converse with
him about many things.
On 9/20/2024 4:17 AM, Stefan Claas wrote:a4f7cb5f3c7a0957d9517ad740b06a5d13a02e0affcb2882f700e388eec93f650c92e3b451915f04d2c0dd45f13e1ad5bfad03552937e2ff2602ec88dc3ccdce8b3076ec0addad4b41123297542709c292bb836850057363dbd2e7c7eb6f237db3e3d3d891600c880b92bbbe0b293a34bbc4994c81dba3deef421247965b01e
I came up with the following idea.
Register a webpage at nekoweb.org, use an API key
and send encrypted messages to the web page, which
later Bob and Alice can decrypt.[...]
To decrypt use the default key, except click on the SHA512 radio button,
then click decrypt:
http://fractallife247.com/test/hmac_cipher/ver_0_0_0_1?ct_hmac_cipher=
On 10/8/2024 6:42 AM, Stefan Claas wrote:a4f7cb5f3c7a0957d9517ad740b06a5d13a02e0affcb2882f700e388eec93f650c92e3b451915f04d2c0dd45f13e1ad5bfad03552937e2ff2602ec88dc3ccdce8b3076ec0addad4b41123297542709c292bb836850057363dbd2e7c7eb6f237db3e3d3d891600c880b92bbbe0b293a34bbc4994c81dba3deef421247965b01e
Chris M. Thomasson wrote:
On 9/20/2024 4:17 AM, Stefan Claas wrote:
I came up with the following idea.
Register a webpage at nekoweb.org, use an API key
and send encrypted messages to the web page, which
later Bob and Alice can decrypt.[...]
To decrypt use the default key, except click on the SHA512 radio button, then click decrypt:
http://fractallife247.com/test/hmac_cipher/ver_0_0_0_1?ct_hmac_cipher=
Hi Chris, please reply here in plaintext. I do not have the passwort anymore.
If you click on the link; click on the SHA512 radio button and then
click the decrypt button you should see the following plaintext: ________________________
Well, shit... I have been really busy lately.
Sorry for neglecting this group.
________________________
Here is a screenshot with the plaintext highlighted:
https://i.ibb.co/tzSbQYJ/image.png
Stefan Claas wrote:a4f7cb5f3c7a0957d9517ad740b06a5d13a02e0affcb2882f700e388eec93f650c92e3b451915f04d2c0dd45f13e1ad5bfad03552937e2ff2602ec88dc3ccdce8b3076ec0addad4b41123297542709c292bb836850057363dbd2e7c7eb6f237db3e3d3d891600c880b92bbbe0b293a34bbc4994c81dba3deef421247965b01e
Chris M. Thomasson wrote:
On 9/20/2024 4:17 AM, Stefan Claas wrote:
I came up with the following idea.
Register a webpage at nekoweb.org, use an API key
and send encrypted messages to the web page, which
later Bob and Alice can decrypt.[...]
To decrypt use the default key, except click on the SHA512 radio button, then click decrypt:
http://fractallife247.com/test/hmac_cipher/ver_0_0_0_1?ct_hmac_cipher=
Hi Chris, please reply here in plaintext. I do not have the passwort anymore.
Or for further communications, I would prefer that you use my minicrypt too, because then we do not need to visit the WWW, for encrypted communications.
My pub key (save it as stefan.pem):
-----BEGIN PUBLIC KEY-----
tRxoeAmoI+0ygSbUYHBRpbYBDkC9+Q3rSTchzSXFHrU=
-----END PUBLIC KEY-----
https://github.com/706f6c6c7578/minicrypt
On 10/17/2024 12:25 PM, Stefan Claas wrote:a4f7cb5f3c7a0957d9517ad740b06a5d13a02e0affcb2882f700e388eec93f650c92e3b451915f04d2c0dd45f13e1ad5bfad03552937e2ff2602ec88dc3ccdce8b3076ec0addad4b41123297542709c292bb836850057363dbd2e7c7eb6f237db3e3d3d891600c880b92bbbe0b293a34bbc4994c81dba3deef421247965b01e
Stefan Claas wrote:
Stefan Claas wrote:
Chris M. Thomasson wrote:
On 9/20/2024 4:17 AM, Stefan Claas wrote:
I came up with the following idea.
Register a webpage at nekoweb.org, use an API key
and send encrypted messages to the web page, which
later Bob and Alice can decrypt.[...]
To decrypt use the default key, except click on the SHA512 radio button,
then click decrypt:
http://fractallife247.com/test/hmac_cipher/ver_0_0_0_1?ct_hmac_cipher=
Hi Chris, please reply here in plaintext. I do not have the passwort anymore.
Or for further communications, I would prefer that you use my minicrypt too,
because then we do not need to visit the WWW, for encrypted communications.
My pub key (save it as stefan.pem):
-----BEGIN PUBLIC KEY-----
tRxoeAmoI+0ygSbUYHBRpbYBDkC9+Q3rSTchzSXFHrU=
-----END PUBLIC KEY-----
https://github.com/706f6c6c7578/minicrypt
Your ciphertext is also longer than minicrypt ciphertext.
Your message with your HMAC cipher:
a4f7cb5f3c7a0957d9517ad740b06a5d13a02e0affcb2882f700e388eec93f65 0c92e3b451915f04d2c0dd45f13e1ad5bfad03552937e2ff2602ec88dc3ccdce 8b3076ec0addad4b41123297542709c292bb836850057363dbd2e7c7eb6f237d b3e3d3d891600c880b92bbbe0b293a34bbc4994c81dba3deef421247965b01ef 1cfca2ac91fc73b1511997cb09907e
Your message with my minicrypt cipher:
RzJ1JQ9XcXuvqozXkVDzTMOLVwOcZTboSrj+16/gZmU+l/0wrLy1Lj6tu+o24QHJ Oo7OZ2XXhbf6PqdQ4mpGxDOB7QuasdrnKwPLUNrnUPgXgimjl/3f1HRcJz6pBQf2 Ywgh1TCpiZnydd+Clt8uj4dbXHYpSSBkG0NIchAauixcHzXAPlME233RW8VrddMi tAYbJptlqHLB
Yeah, I am only representing the ciphertext in hex right now for the
online version. Now, I could modify it to encode the ciphetext in base
64 or something a little more "dense", so to speak... Fwiw, here is a
link to a C based test version, have you seen it yet?
https://groups.google.com/g/comp.lang.c/c/a53VxN8cwkY/m/XKl1-0a8DAAJ
;^)
Stefan Claas wrote:
I came up with the following idea.
Register a webpage at nekoweb.org, use an API key
and send encrypted messages to the web page, which
later Bob and Alice can decrypt.
https://pollux.nekoweb.org
Alice does:
$ xchacha20 key iv < msg.txt | b2h | hex2img -b 0 -v | xml2html > index.html && neko
Process completed in 4.7553ms
Files uploaded
While Bob does:
$ curl https://pollux.nekoweb.org | xml2html -d | hex2img -v -d | b2h -d | xchacha20 key iv
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 825 0 825 0 0 4881 0 --:--:-- --:--:-- --:--:-- 4881
Hello sci.crypt! :-)
Process completed in 191.3448ms
Thus allowing Alice and Bob to exchange messages without email usage and without visiting a website with a browser.
Hope you like the idea!
Have made the process a bit more flexible, so that the neko bash script
is replaced with a nekoweb Go program, which acts as cURL, for Windows
users who don't have cURL. This makes also the upload more flexible, so
tha folders can be created where the files are stored.
Example: https://pollux.nekoweb.org/msg/1.txt
I came up with the following idea.
Register a webpage at nekoweb.org, use an API key
and send encrypted messages to the web page, which
later Bob and Alice can decrypt.
https://pollux.nekoweb.org
Alice does:
$ xchacha20 key iv < msg.txt | b2h | hex2img -b 0 -v | xml2html > index.html && neko
Process completed in 4.7553ms
Files uploaded
While Bob does:
$ curl https://pollux.nekoweb.org | xml2html -d | hex2img -v -d | b2h -d | xchacha20 key iv
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed 100 825 0 825 0 0 4881 0 --:--:-- --:--:-- --:--:-- 4881
Hello sci.crypt! :-)
Process completed in 191.3448ms
Thus allowing Alice and Bob to exchange messages without email usage and without visiting a website with a browser.
Hope you like the idea!
I came up with the following idea.
Register a webpage at nekoweb.org, use an API key
and send encrypted messages to the web page, which
later Bob and Alice can decrypt.
https://pollux.nekoweb.org
Alice does:
$ xchacha20 key iv < msg.txt | b2h | hex2img -b 0 -v | xml2html > index.html && neko
Process completed in 4.7553ms
Files uploaded
While Bob does:
$ curl https://pollux.nekoweb.org | xml2html -d | hex2img -v -d | b2h -d | xchacha20 key iv
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed 100 825 0 825 0 0 4881 0 --:--:-- --:--:-- --:--:-- 4881
Hello sci.crypt! :-)
Process completed in 191.3448ms
Thus allowing Alice and Bob to exchange messages without email usage and without visiting a website with a browser.
Example.
key: 5c42a3c290c91c66654b9af5a924057677b691257a24b7e414d028300bd4f6f0
iv: 7dfa38650527d096fbbbeb8b05e5097c48089a21c391a45b
https://pollux.nekoweb.org/msg/3.html
$ enc | nekoweb msg/3.html
$ nekoweb -d https://pollux.nekoweb.org/msg/3.html | dec
I wish the sci.crypt community a nice weekend
and hope that you come up as well with such
an encoder/decoder! Best regards Stefan. :-)
Stefan Claas wrote:
Example.
key: 5c42a3c290c91c66654b9af5a924057677b691257a24b7e414d028300bd4f6f0
iv: 7dfa38650527d096fbbbeb8b05e5097c48089a21c391a45b
https://pollux.nekoweb.org/msg/3.html
$ enc | nekoweb msg/3.html
$ nekoweb -d https://pollux.nekoweb.org/msg/3.html | dec
I wish the sci.crypt community a nice weekend
and hope that you come up as well with such
an encoder/decoder! Best regards Stefan. :-)
Reference tools:
https://github.com/706f6c6c7578/nekoweb https://github.com/706f6c6c7578/hex2img
https://github.com/706f6c6c7578/b2h
https://github.com/706f6c6c7578/xchacha20
I am also thinking of creating a key pair for sci.crypt, so that we
no longer have to use SCOS, because SCOS was floating around on
Bitmessage, as C, Pascal and Go code.
On 10/17/2024 1:25 PM, Stefan Claas wrote:
Chris M. Thomasson wrote:[...]
Yeah, I am only representing the ciphertext in hex right now for the online version. Now, I could modify it to encode the ciphetext in base
64 or something a little more "dense", so to speak... Fwiw, here is a link to a C based test version, have you seen it yet?
https://groups.google.com/g/comp.lang.c/c/a53VxN8cwkY/m/XKl1-0a8DAAJ
;^)
Yes, I remember that and I had compiler errors.
You never got it compile with C99?
Have you tried my minincrypt yet? It is probably the easiest to
use public key encryption software. ;-)
I have not. Sorry! Been working lately.
Stefan Claas <pollux@tilde.club> wrote:
I am also thinking of creating a key pair for sci.crypt, so that we
no longer have to use SCOS, because SCOS was floating around on
Bitmessage, as C, Pascal and Go code.
Do note that SCOS was not intended to be "secure" (for most definitions
of that word). Richard H. posted it as an exercise in breaking a
cipher given just examples of the cipher's output. It fits in as a
somewhat more difficult ROT13 than as a true "protection" for anything
posted with it.
It is interesting that source for it is on bitmessage.
On 10/18/2024 6:38 AM, Stefan Claas wrote:
Chris M. Thomasson wrote:
On 10/17/2024 1:25 PM, Stefan Claas wrote:
Chris M. Thomasson wrote:[...]
Yeah, I am only representing the ciphertext in hex right now for the online version. Now, I could modify it to encode the ciphetext in base
64 or something a little more "dense", so to speak... Fwiw, here is a link to a C based test version, have you seen it yet?
https://groups.google.com/g/comp.lang.c/c/a53VxN8cwkY/m/XKl1-0a8DAAJ
;^)
Yes, I remember that and I had compiler errors.
You never got it compile with C99?
I tried with gcc and g++, but it is ok.
Well, what errors did you get? Many others were able to compile and run
it wrt encrypt and decrypt cycles on various plaintexts.
Have you tried my minincrypt yet? It is probably the easiest to
use public key encryption software. ;-)
I have not. Sorry! Been working lately.
You should really try and use it.
Hummm... Agreed. Also, I have you to query if I have any issues.
Thanks Stefan. :^)
It is probably the easiest to
use encryption program out there and it uses modern ciphers and
no need for WWW based encrypted message exchange.
The only reasons I created an online version of it was for "convenience"
and just to see if I could do it to begin with. Its client side only. I thought, sending the ciphertext in a url was be an easy way. Hex
encoding was simple enough. Keep in mind that my cipher is purely
symmetric at this stage.
I am also thinking of creating a key pair for sci.crypt, so that
we no longer have to use SCOS, because SCOS was floating around
on Bitmessage, as C, Pascal and Go code.
:^) Fwiw, I never compiled any Go code in my life. C and Pascal, yup,
but not Go. Fwiw, I am friends with somebody who is/was on the Go team.
Not sure if he still works for Google. I have not talked to him in some months.
On 10/18/2024 6:38 AM, Stefan Claas wrote:
Chris M. Thomasson wrote:
On 10/17/2024 1:25 PM, Stefan Claas wrote:
Chris M. Thomasson wrote:[...]
Yeah, I am only representing the ciphertext in hex right now for the >>>>> online version. Now, I could modify it to encode the ciphetext in base >>>>> 64 or something a little more "dense", so to speak... Fwiw, here is a >>>>> link to a C based test version, have you seen it yet?
https://groups.google.com/g/comp.lang.c/c/a53VxN8cwkY/m/XKl1-0a8DAAJ >>>>>
;^)
Yes, I remember that and I had compiler errors.
You never got it compile with C99?
I tried with gcc and g++, but it is ok.
Well, what errors did you get? Many others were able to compile and run
it wrt encrypt and decrypt cycles on various plaintexts.
