Stephen R. van den Berg wrote:
>Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
>>Seems to be due to an incompatibility in the implementation of Curve25519.
>>Try disabling Curve25519 for now (by eg disable it in the mapping
>>ECC_CURVES in SSL.pmod/Constants.pmod).
>After your
Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
>> The test program below shows an I/O error for Pike 8.1, and it shows
>[...]
>Seems to be due to an incompatibility in the implementation of Curve25519.
>Try disabling Curve25519 for now (by eg disable it in the mapping
>ECC_CURVES
Stephen R. van den Berg wrote:
>I now have an API that works roughly like this:
The API has since reached beta-stage and is now included in Pike 8.1
(it has a synchronous, a callback *and* a promise interface).
Documentation is a little bit skimpy at the moment.
But a working minimal example is
> The test program below shows an I/O error for Pike 8.1, and it shows
[...]
Seems to be due to an incompatibility in the implementation of Curve25519.
Try disabling Curve25519 for now (by eg disable it in the mapping
ECC_CURVES in SSL.pmod/Constants.pmod).
/grubba
Stephen R. van den Berg wrote:
>The test program below shows an I/O error for Pike 8.1, and it shows
My new Google API code seems to be ready for production.
However, I switched back to Pike 8.0 to develop it, due to the broken
SSL implementation of Pike 8.1
Unfortunately I used the promise
