aaronk6

4 ms·

1. 1.▲
   by aaronk6 4y ago

   Exactly! I had only posted the link on www.reddit.com/r/reactos and didn’t expect it to get attention from a wider audience :-) Also, I deliberately avoided CDNs and caches to see if the source system can handle the load. I know
2. 2.▲
   by aaronk6 4y ago

   Yeah, but not necessarily ReactOS’s fault! The machine it’s running on doesn’t have much power as I didn’t expect it to get much attention really. Also see my notes regarding the HTTPS link that was temporarily broken: https://ne
3. 3.▲
   by aaronk6 4y ago

   HTTPS is fixed now.
4. 4.▲
   by aaronk6 4y ago

   This. Part of the challenge for me was to avoid any proxies and and have all requests go directly to the ReactOS system. I’m totally aware that this doesn’t make any sense in a real-world scenario.
5. 5.▲
   by aaronk6 4y ago

   I’m the author of the page. It’s now reachable via HTTPS (again). I think this is what happened: I experimented with HTTPS on Sunday and actually got it up and running by patching msafd.dll (see https://jira.reactos.org/brow
6. 6.▲
   by aaronk6 4y ago

   Hi, I’m the author of the page. > Probably doesn't have a letsencrypt client. Right, Certbot doesn’t work because of an issue with Python, however, it’s easy to generate the certificates elsewhere and inject them into the virtual ma
7. 7.▲
   by aaronk6 13y ago

   I cannot confirm this. I've just updated via iTunes and it asked for the PIN code.