Thanks Mechy! Good to know! Now, when might we see IBrowse 2.5 and a new version of AmiSSL? I hope soon... any devs actively working on these?  Thanks again! BTW, this will make OM's day!

Good sir!  I say!  You can't just post something like this and not give more details!  :lol:

That is all there is on the IB news page.. it was passed to me so i passed it here wish there were more details. Far as i know the guy who did amissl 3.6 is not updating it, as there are some problems he said. When you read this though it makes me think someone else is working on it.

http://www.ibrowse-dev.net/news.php

AFAIK the person doing the updates to AmiSSL is this guy:

http://www.warpdt.co.uk/

If so, I heartily approve!  Last I heard was that he had a new version, but was stuck waiting on the rest of the IBrowse team to move forward...

I can't take the credit regarding AmiSSL - most of the work has been done by Jens Maus, and several others have been involved. It's true that development did stall, but to cut a long story short I stepped in recently to help fix everything as the code was broken and simply didn't work. Now it is working again, the AmiSSL team have regained their motivation, as you can see from GitHub .

AmiSSL is not dependent on IBrowse and can be released at any time. However, IBrowse is if course dependent on AmiSSL - it would be foolish to release IBrowse 2.5 until the SSL issues were fixed and that means a new AmiSSL.

I didn't realise until yesterday, while reworking the SSL code in IBrowse, that IBrowse 2.4 and AmiSSL 3.6 could already handle TLSv1 connections - IBrowse 2.4 explicitly disables it for a reason I am unsure of. Wish I'd figured that out earlier as I could have published the "fix" as soon as POODLE hit and sites began to shut off SSLv3, but better late than never!

I can't take the credit regarding AmiSSL - most of the work has been done by Jens Maus, and several others have been involved. It's true that development did stall, but to cut a long story short I stepped in recently to help fix everything as the code was broken and simply didn't work. Now it is working again, the AmiSSL team have regained their motivation, as you can see from GitHub .

AmiSSL is not dependent on IBrowse and can be released at any time. However, IBrowse is if course dependent on AmiSSL - it would be foolish to release IBrowse 2.5 until the SSL issues were fixed and that means a new AmiSSL.

I didn't realise until yesterday, while reworking the SSL code in IBrowse, that IBrowse 2.4 and AmiSSL 3.6 could already handle TLSv1 connections - IBrowse 2.4 explicitly disables it for a reason I am unsure of. Wish I'd figured that out earlier as I could have published the "fix" as soon as POODLE hit and sites began to shut off SSLv3, but better late than never!

Thanks for letting us know, i look forward to a new release of Amissl! Its getting harder to get around the net in ibrowse on my 4k

Thanks for letting us know, i look forward to a new release of Amissl! Its getting harder to get around the net in ibrowse on my 4k

Note that existing apps will not automatically be able to make use of the new AmiSSL. Programs need to be recompiled using the new headers, due to changes in the OpenSSL API (this has always been the case and intention - there is no way around that, so AmiSSL v3 was designed this way).

One thing for sure as soon as IBrowse 2.5 gets released I'll definitely register it at once to support future development.