OpenSSL for AmigaOS have been updated! The OpenSSL Project is a collaborative effort to develop a robust, commercial-grade, full-featured, and OpenSource toolkit implementing the Secure Sockets Layer (SSL v2/v3) and TransportLayer Security (TLS v1) protocols as well as a full-strength general purpose cryptography library.

OpenSSL is based on the excellent SSLeay library developed from Eric A. Young and Tim J. Hudson. The OpenSSL toolkit is licensed under a dual-license (the OpenSSL license plus the SSLeay license) situation, which basically means that you are free to get and use it for commercial and non-commercial purposes as long as you fulfill the conditions of both licenses.

The OpenSSL binary for AmigaOS is provided fully native (no ixemul), with support for the following ciphers:

mdc2, md4, md5, hmac(md5), sha1, rmd160, rc4, des cbc, des ede3, idea cbc, seed cbc, rc2 cbc, blowfish cbc, cast cbc, aes-128 cbc, aes-192 cbc, aes-256 cbc, camellia-128 cbc, camellia-192 cbc, camellia-256 cbc, sha256, sha512, whirlpool, aes-128 ige, aes-192 ige, and aes-256 ige.

Developer material can be found in the included devfiles.tar.7z file, read first the devfiles.txt if you want to check the provided files. Tree structure is keep with GeekGadgets compatibility in mind. Static libraries are provided for libnix and ixemul including builds for 68020 and 68060 - more info at the included amiga.readme.txt file.

For further info and downloads, please go to http://amiga.sourceforge.net/OpenSSL/

Awesome!

@arnljot, drHirudo, Pyromania, som99

Can I ask what you're using openssl command for?

You really use openssl command under amigaos daily? I find that quite hard to believe.

What ssl implementation is used in the browsers when using https? I suspect alot of people use openssl without know that they do

What ssl implementation is used in the browsers when using https? I suspect alot of people use openssl without know that they do

The poll has a separate option for software that uses openssl.

It's slightly confusing why anybody would somewhat waste their time porting OpenSSL, when it has already been ported natively in the form of AmiSSL ... The only problem is that AmiSSL hasn't been updated for a while and is based on OpenSSL 0.9.7g.

Maybe that is why? D'oh! :hammer:

Does AmiSSL have a CLI?  That would be one good reason.  As well, the fact that it is based on an older release of OpenSSL is enough for me.  I like programs that do not crash (as frequently, anyway) on questionable certificates, input, etc.

Anyway, I both use programs which incorporate OpenSSL (stunnel, to name one) as well as use OpenSSL on a near-daily basis.  I play a lot with secure certificates, both web SSL and others, and OpenSSL is pretty invaluable.

I am just waiting for YAM to support S/MIME so I can import my personal email certificate and begin signing my YAM-produced emails.

Does AmiSSL have a CLI?  That would be one good reason.

It does have the standard OpenSSL command, yes - probably something that most users are not aware of.