Liste des Groupes | Revenir à s crypt |
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.
Les messages affichés proviennent d'usenet.