Amissl v4.0

Yam latest dev is feclaiming amissl v4.0
Where can i get it?

Found it here
https://github.com/jens-maus/amissl/re ... wnload/4.0/AmiSSL-4.0.lha

From aminet: http://aminet.net/util/libs/AmiSSL-4.0.lha
Or directly from Jen's github acc: https://github.com/jens-maus/amissl/releases

Hi,
trying to recompile a project with latest AmiSSL (installation done manually in my SDK: because not doing by installer)

/SDK/local/newlib/lib/libamisslauto.a(autoinit_amissl_main.o): In function `__init_amissl_main':
autoinit_amissl_main.c:(.text+0x20e): undefined reference to `errno'
autoinit_amissl_main.c:(.text+0x21e): undefined reference to `errno'

including errno.h in my code doesn't solved the problem.

Is somebody encoutered this problem ?

Thanks

edit : reverted to libamisslauto.a from 2005 in my SDK:local/newlib/lib make linking works again.

@zzd10h

Please add it to the AmiSSL issue tracker

@zzd10h

Yes, please add to the issue tracker. Jens went ahead and released AmiSSL before I had really finished writing script that builds the release archives. The included libamisslauto.a is for apps compiled to use clib2, and not newlib (the old SDK contained two versions). I did raise my concern, but was also unsure how many developers actually used it.

Anyway, as you've found, the quick fix is to use the one from the old SDK - nothing substantial, if anything, has changed in that code. Hopefully, we can get this fixed for the next release.

edit: I've just now pushed in changes to github that will resolve this for the next release.

The OS4 AmiSSL V4 installer puts the docs in SYS:Documentation but the AmiSSL docs (as installed by OS4.4FE) are in SYS:Documentation/AmiSSL. A user ends up with 2 sets of AmiSSL documentation which could result in some user confusion. I just reported this at the AmiSSL repository but current users might want to place the AmiSSL docs in the correct location.

@xenic

Good catch, thank you

@Raziel

Not sure if this is the right place for this, as this thread obviously is for the OS4 version of AmiSSL 4.0.

Regarding the m68k version of AmiSSL 4.0, there was a news item at amiga-news.de on Feb 8th. At the end of this news item there was an 'editor's note':

editor's note: Those who are really still occasionally using IBrowse to surf the web should enable TLS to improve IBrowse's compatibility with encrypted websites significantly - even without AmiSSL-4-support.

Clicking on the "enable TLS"-link led me to an old news item of Feb 2016, where the original message of the IBrowse-development-team with an instruction on how to enable TLS in IBrowse v2.4 was linked.

Unfortunately I missed the news last year - and so I have not tested it up to now (And yes, I'm one of those infamous users "who are really still occasionally using IBrowse to surf the web").

Maybe this is now covered in AmiSSL 4.0 - but just in case it is not, I'd like to share this info with you on how to make IBrowse nevertheless access "https -sites"...