maxtherabbit
Veteran Member
Dunno about ODI, but I've definitely used NDIS packet shims with mTCP and everything works 100%
Just to be clear - your NICs were PCI-based and came with real-mode NDIS drivers?Dunno about ODI, but I've definitely used NDIS packet shims with mTCP and everything works 100%
But that is what Chucks query was about....PCI nics that had packet drivers available for them.No, I never said a thing about PCI. ISA cards
And it's finally available: http://www.brutman.com/mTCP/mTCP.html
Besides the list above there were some more bug fixes, some of them surprisingly old. HTTPServ also now has an SNTP client built in so that it can have accurate time across days or weeks. See the release notes for details.
-Mike
PS: At the moment everything except for large PDF files is being redirected and being served from a PCjr. I've got the PCjr and networking gear on a UPS and I want to see how long it can stay running. (My bet is that I'll have to shut it down in five weeks to clear the log file.) Here is a picture of the actual machine:
View attachment 1254939
Thank you. I think most users use DOS/Windows as well, so they won't notice, either.I'll scrub that for the next release, but in general it should be safe to force everything to lower case.
I'd like to get TLS 1.2/1.3 working on my 286/12. Since the TLS apocalypse, internet access with older machines has become useless. Even sites hosting old drivers and using simple layouts only respond with an HTTPS redirect, as they will be cut off from search engines otherwise. The hard part is doing the handshake before the server closes the connection. Encryption won't be fast, and security isn't even an option.Are you making anything interesting?
Also having an interest in this, though I've focused on SSH, on anything below a 386 I think you're going to end up writing a small server to offload the asymmetric cryptography calculations (ECDH/ECDSA/RSA/Ed25519) to another machine on the local network, and return the results of the calculation to the 286/8088 machine (such that it can proceed with the handshake) in order to achieve anything tolerable.I'd like to get TLS 1.2/1.3 working on my 286/12. Since the TLS apocalypse, internet access with older machines has become useless. Even sites hosting old drivers and using simple layouts only respond with an HTTPS redirect, as they will be cut off from search engines otherwise. The hard part is doing the handshake before the server closes the connection. Encryption won't be fast, and security isn't even an option.
Eventually, I'd like to get something in between MicroWeb and Arachne. But that is a long shot. I did port Arachne to SDL2, but its code quality is... not great.
I was planning to hand-roll the crypto, removing security for speed. So far, I have primitives for aes128 (16-bit), aes256 (16-bit), base64 (8-bit), curve25519 (64-bit), sha256 (32-bit) and hmac-sha256 (32-bit). With a precomputed private key, a TLS 1.2 handshake should be doable with a single curve25519 multiplication, which currently takes about 30 seconds. I hope that a 16-bit assembly implementation can reduce this by 25%, making the handshake possible. Maybe it will be tolerable when paired with HTTP Keep-Alive.Have you thought of which TLS library to use?
Wait, what? How did you do this?
- A live-patching the executable in memory session to disable the logging to disk to conserve disk space.
Wait, what? How did you do this?