Finally, after 20 attempts to click "Pay now" I succeeded. In my case, I changed "shipping address" in Paypal and I managed to buy for the second attempt. Uff.
I've not tried to buy this exact product, but have had problems using AmiStore a few months ago.
It was impossible to make a purchase, because my shopping cart would never empty. When I got to the point of paying, I had like 5-6 identical products in the cart. When logging in on a later date, the same items were still there, but they did not show up in the cart in AmiStore. Tried different things to fix it, but to no avail.
Contacted A-EON several times, but got no reply. The result was that I ended up ordering a boxed version of Enhancer instead.
It would be nice if they had a shopping section similar to the usual AmigaKit website. Would be much easier!
Maybe a system similar to Alinea in Germany? I've bought downloads from them and it works very well. You put the wanted software in the cart, check out and pay, and then you will receive a link to download what you've bought.
Thanks for the security alert regarding OpenSSL ...
I have rolled back to AmiSSL 5.3 and will await a future update.
AmiSSL 5.5 is now available - be sure to always use AmiUpdate to grab the latest release. I'm still a bit confused why they pulled OpenSSL 3.0.6. The regression issues were relatively minor, especially when compared to the high severity buffer overflow bugs which are also fixed in 3.0.7 and were present in all OpenSSL 3.0 versions (and therefore all AmiSSL v5 releases).
I managed to get the Bridge. Paypal's support told me to try different browsers and clear the cache and cookies before trying to pay. (I should have realized to clear them by myself.) I tested Firefox on a Mac this time clearing the cache and all of the cookies first. Payment went smooth without a glitch.
Edited by TSK on 2022/11/3 19:25:44
Rock lobster bit me - so I'm here forever X1000 + AmigaOS 4.1 FE "Anyone can build a fast CPU. The trick is to build a fast system." - Seymour Cray
amigakit wrote:Today the following public releases have been made available to download on Updater utility:
AmiSSL v5.5
To download goto the Packages tab
May I ask why AmiSphereServer (and therefore Updater) doesn't itself use AmiSSL and instead uses an outdated, obsolete, statically linked OpenSSL 1.0.2o? It should be easy to make the switch and it'll make AmiSphereServer much smaller too! Please support AmiSSL, rather than waste time messing with OpenSSL directly.
As the OpenSSL team itself says: "All older versions (including 1.1.0, 1.0.2, 1.0.0 and 0.9.8) are now out of support and should not be used."
It appears to be using libcurl too - the latest libcurl has built-in AmiSSL v5 support, but you may not even need to use libcurl at all either. OpenSSL 3.0 has its own simple built-in HTTP(S) client.
May I ask why AmiSphereServer (and therefore Updater) doesn't itself use AmiSSL and instead uses an outdated, obsolete, statically linked OpenSSL 1.0.2o? It should be easy to make the switch and it'll make AmiSphereServer much smaller too! Please support AmiSSL, rather than waste time messing with OpenSSL directly.
It was written by it's original authors using libcurl. as you note below. That makes / made using AmiSSL problematic...
Quote:
As the OpenSSL team itself says: "All older versions (including 1.1.0, 1.0.2, 1.0.0 and 0.9.8) are now out of support and should not be used."
An ideal we often fall short of in amiga land Quote:
It appears to be using libcurl too - the latest libcurl has built-in AmiSSL v5 support, but you may not even need to use libcurl at all either. OpenSSL 3.0 has its own simple built-in HTTP(S) client.
Two bbits of useful info thanks. Does the inbuilt https support cookies etc??
It appears to be using libcurl too - the latest libcurl has built-in AmiSSL v5 support, but you may not even need to use libcurl at all either. OpenSSL 3.0 has its own simple built-in HTTP(S) client.
Two bbits of useful info thanks. Does the inbuilt https support cookies etc??
Not directly - as you might expect with OpenSSL, things are a bit more low-level than Curl. However, you are free to add any outgoing HTTP headers as you wish, which includes adding a cookie header. See https://github.com/jens-maus/amissl/blob/master/test/httpget.c for a general example.
Retrieving a "Set-Cookie" header from the response might be more problematic. I've not played to see how or if this is possible, but it seems not. I've opened a feature request at https://github.com/openssl/openssl/issues/19609.
Good for radeonrx v2.12, take only 2 months to release it :)
But isn't amissl are open stuff, which everyone can download from GitHub and/or os4depot/aminet ? Or having it in the updater give some benefits for anyone downloading from ? At least the version 5.6 is uploaded to os4depot a month ago.
Beta testing is not a quick process. Many of our beta testers test in their spare time between family life and events such as Christmas holidays can pause testing. We release something when it has passed the testing process.
Updater tool is used by most users here on a weekly or even daily basis. Some of our products use AmiSSL so it makes sense to make it available easily to our user base through Updater tool. It is the official method of distributing files for our system.
@amig_os
Click the Information button in Updater tool to read the change logs. This release fixes Copy routine bugs