Notes

Maybe instead of replacing everything with Rust, we can start by not relying on 25,000-line autoconf shell scripts

FWIW, this eBay auction is not mine, they just ripped off my pictures and description. Not sure if this is just a scam listing or if they are actually selling old PowerBook batteries.

https://www.ebay.com/itm/166672331810

🤔

Supposedly a non-root RCE in OpenBSD up to 7.4, appears to require NFSd running though?

https://www.youtube.com/watch?v=i_JOkHaCdzk

I wonder if there's a "sovereign citizen" group of wackos that try to ignore daylight saving time and show up to everything an hour late

Like they get a ticket for driving without a license plate because they don't believe in them, then they show up to court an hour late and get arrested yelling at the judge that the government doesn't have the right to control time

there are dozens of us!

There's a large cache of in-box (much of it unopened) classic Mac software being sold on eBay recently:

https://www.ebay.com/sch/i.html?_ssn=chopinpiano745&store_name=xtraordinaryemporium&_oac=1&_sop=10

"We've put the keyboard to the back of the unit, placed the trackball here in the center, which left this area which we call a palm rest"

from https://social.jcs.org/@compchron/111653683399618214

I wonder if companies ever intentionally put spammy things in their "Updates to our Privacy Policy and User Agreement" e-mails to make sure they land in most users' spam folders, avoiding user scrutiny and complaints while providing legal cover that users were technically notified

For any pentesters out there, I came across this wacky MIME syntax for an e-mail attachment in RFC 2231 that is properly parsed by iOS Mail and other things, but I'm curious if it can make a .exe attachment pass through an e-mail scanning appliance:

Content-Type: application/octet-stream
Content-Disposition: attachment;
filename*0="a.txt";
filename*1=".ex";
filename*2="e";

Which is to be properly decoded as:

Content-Disposition: attachment; filename="a.txt.exe"

Section 4.1 says this encoded syntax is also legal:

Content-Type: application/octet-stream
Content-Disposition: attachment;
filename*=us-ascii'en-us'a.txt%00%2E%65%78%65

iOS Mail displays it as "a.txt<?>.exe" and can't seem to download it. Mutt and FastMail's web interface stop at the null byte and just show "a.txt".

computer

A new C Programming on System 6 video showing some work on Carl, my IMAP (and now SMTP) e-mail client

https://jcs.org/2024/02/20/carl

Some weird scenario I think about from time to time:

You wake up in a remote cabin with access to a 1980s computer (pick your favorite) that has slow access to the modern internet through satellite with a working TCP/IP stack but no recursive DNS server configured and no utilities installed (ping, ftp, etc.). The computer is too slow to do SSH, TLS, etc. and you can't remember any logins or passwords to existing systems. It does have a BASIC interpreter, simple compiler (whichever language you want that was around in the 1980s), and assembler. There are no manuals or other documentation available on the computer or in the cabin, other than installed header files or whatever else is needed for the compiler to use the TCP/IP stack.

Can you use the computer and internet to communicate enough to get rescued? What steps would you take?

Version 4 of Subtext, my BBS server for classic Mac OS, is available today. It fixes some bugs, adds things like remote syslog support, and makes telnet negotiation faster.

https://jcs.org/subtext

I wish Microsoft would embrace its roots as a heavy metal band

https://www.ebay.com/itm/386780461528