Amiga.org
Amiga News and Community Announcements => Amiga News and Community Announcements => Topic started by: dcr8520 on June 27, 2010, 12:26:23 PM
-
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/
-
This is important software, thanx for the update.
-
Awesome!
-
Downloaded. Thanks for the update!
Cheers,
Dragster
-
@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.
-
@Piru:
To check the checksum of downloaded files, maybe?..
-
What ssl implementation is used in the browsers when using https? I suspect alot of people use openssl without know that they do :)
-
Can I ask what you're using openssl command for?
There are two users who is it daily.. I find that quite hard to believe.
I use openssl daily, but not on amiga. The one command I use most is definetly x509, followed by s_connect, hash, req and ca.
-
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. AmiSSL is of course most commonly used by various apps, including those that need to support HTTPS including IBrowse and AWeb. However, it is also supplied the OpenSSL command (which uses the AmiSSL shared libraries). The only problem is that AmiSSL hasn't been updated for a while and is based on OpenSSL 0.9.7g.
-
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:
-
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. AmiSSL is of course most commonly used by various apps, including those that need to support HTTPS including IBrowse and AWeb. However, it is also supplied the OpenSSL command (which uses the AmiSSL shared libraries). The only problem is that AmiSSL hasn't been updated for a while and is based on OpenSSL 0.9.7g.
:shocked: well, you already provided some reasons yourself, so...
I also assume you'll wonder why anybody would somewhat waste their time porting OWB, NetSurf, or Firefox, when there is already IBrowse... :-/
:confused:
-
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.
-
Congrats, Guys! This is really awesome. I have no use of it now, but I appreciate your efforts and hard work. :)
-
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.
-
:shocked: well, you already provided some reasons yourself, so...
I also assume you'll wonder why anybody would somewhat waste their time porting OWB, NetSurf, or Firefox, when there is already IBrowse... :-/
And what's wrong with that? ;)
Actually, that's not a fair comparison. Would you agree that there is no point two developers each making their own Firefox port? Likewise for OpenSSL... I was merely suggesting that it may have been a better idea for the author to work with the AmiSSL authors. Then OS4 users could benefit as well as 68k users, and everybody using IBrowse, AWeb, HTTPResume or whatever, will get the latest OpenSSL support too - not just users using the OpenSSL command line tool.
-
If the AmiSSL guys were any interested in upgrading their package, I would have guessed that they would have done so. I don't really see any problem with someone else doing a port, even if it's only the command line tools.
-
Btw - a device handler akin to TCP: that does SSL would be lovely, with configurable client certificate.
-
If the AmiSSL guys were any interested in upgrading their package, I would have guessed that they would have done so.
I certainly think it's time to update AmiSSL, there we had the 0.9x branch for ages, i think the new 1.0x release(s) deserves it! :)
I don't really see any problem with someone else doing a port, even if it's only the command line tools.
Only?
AmiSSL = Command Line Tool + shared libraries
My OpenSSL = Command Line Tool + static libraries
It's almost the same really (version number apart), each one with his advantages and disvantages...
-
Would you agree that there is no point two developers each making their own Firefox port?
I'm sure that if the Timberwolf sources get released there will be more than two developers doing their own versions... :)
Likewise for OpenSSL... I was merely suggesting that it may have been a better idea for the author to work with the AmiSSL authors.
Well, I've already offered myself to update AmiSSL, i can repeat it here if you want ;)
Then OS4 users could benefit as well as 68k users, and everybody using IBrowse, AWeb, HTTPResume or whatever, will get the latest OpenSSL support too - not just users using the OpenSSL command line tool.
No doubt on that. Also note the initial goal from my port was to provide other developers with static libraries for his ports to support SSL, i have been doing this since the 2003...
-
My OpenSSL = Command Line Tool + static libraries
It's almost the same really (version number apart), each one with his advantages and disvantages...
Well, yours requires programs to be compiled and linked against it, not many that programs are - nothing wrong about it, it just is what it is.
-
Well, yours requires programs to be compiled and linked against it
that's right, the 99.999% of the ports are compiled with libraries linked statically - do you mean this is something bad?
not many that programs are - nothing wrong about it, it just is what it is.
Hmm, wasn't you who said there are more programs using OpenSSL than one might think? well... apply it to yourself as well then ;)
-
Hi there,
Another "1.0.0a" build has been released today, including the following changes:
- Compiled using GCC 3.4.0 for better speed (please report any issue, i didn't trust so much this compiler)
- Optimized bzero/bcopy/memmove/memcpy functions to achieve a somewhat faster speed. (libnix)
- Implemented alarm() to perform the tests, we'll no longer have to wait those long times.
- Time spent on speed tests are now calculated using ReadEClock()
- OPENSSL_assert() will now open a ReAction/Intuition requester (usefull for WB-only progs)
- Enabled MD2 and RC5 which was disabled by default..
- Added 68040 build (user and dev)
- Added new set of root certificates
- Included Installation script.
http://amiga.sourceforge.net/OpenSSL/
-
What ssl implementation is used in the browsers when using https? I suspect alot of people use openssl without know that they do :)
there is now new netsurf in aminet,
it use the openssl1.0.0 from Diego and many thanks to him that he help also to get openssl in libcurl and so netsurf working.
http://aminet.net/package/comm/www/NetSurf-m68k
-
You're welcome.. do i get a percentage of the donations? :)
btw, i've noticed you guys have included on the package my not-yet-released wget 1.12r2.. which still subject to change, in fact there were some improvements over than one included there, i hope to release it some time soon.
-
If you are building libcurl with ssl support for the amiga, you might want to look at polarssl, which libcurl supports and is much smaller than openssl.
-
@buzz:
LOL!...and you recommend this NOW? you're funny indeed :razz:
Well, i didn't recall there existed polarssl, just saw on their website it supports "Motorola 68000", if that means code is in m68k-ASM it may worth a try, although it might need to be optimized for our real cpus.. i'll try to check the code when i'll get some time..
-
@buzz:
LOL!...and you recommend this NOW? you're funny indeed :razz:
Well, i didn't recall there existed polarssl, just saw on their website it supports "Motorola 68000", if that means code is in m68k-ASM it may worth a try, although it might need to be optimized for our real cpus.. i'll try to check the code when i'll get some time..
? I only just saw that they are using the latest libcurl with the browser, and polar ssl support only came in very recently. the polarssl code is in C. I use it already for some software I work on, and it is pretty compact.