Re: TLS 1.3 HTTPS project for C64

Raj, if you want to try to run it the working program is in my repo, along with the scripts that can set up the python based HTTPS listener. It would be interesting to know if it works on real metal vs the VICE version of RR-net so if you are feeling passionate then by all means I’d love to hear.  Beyond that it is mostly an academic exercise to run this on anything other than a U64E or C64U because I don’t think I can ever get the math fast enough to claw back over an hour and a half of runtime at 1Mhz. I am working on integrating my optimized crypto primitive libraries into c64-https and I’ve made them public now since they were in a usable state if anyone has a use for them in some other project. Generally speaking they rely heavily on using the REU to store precomputed tables and that will probably force the next release of c64-https to require a 512KB REU.

https://github.com/JC-000/c64-ChaCha20-Poly1305
https://github.com/JC-000/c64-nist-curves
https://github.com/JC-000/c64-x25519
https://github.com/JC-000/c64-polyval

Thanks,

Justin

> On Apr 19, 2026, at 14:59, Raj Wurttemberg <rajaw_at_c64.us> wrote:
> 
> Hey Justin,
>  
> I have a 64NIC+ from Brain Innovations (https://www.go4retro.com/products/64nic/), I don’t know if that would be helpful in testing, but I would be happy to help if needed.
>  
> Kind regards,
> /Raj
>  
> From: Justin <shadow_at_darksideresearch.com>
> Reply-To: <cbm-hackers_at_musoftware.de>
> Date: Sunday, April 19, 2026 at 12:50 PM
> To: <cbm-hackers_at_musoftware.de>
> Subject: Re: TLS 1.3 HTTPS project for C64
>  
> I have pushed an update today after discovering and fixing a bug that made it not work properly with IP65/RR-net. I have now validated that it completes the TLS 1.3 handshake and an HTTPS GET at 1 MHz in VICE and on the U64E. I do not have a real RR-net to test with on a real 64. It think it takes ~1h 37m to complete at 1 Mhz. If anyone chooses to try it on real metal or in VICE you should expect a very long wait after the third PROC symbol is displayed.
>  
> Thanks,
>  
> Justin