Supposedly a non-root RCE in OpenBSD up to 7.4, appears to require NFSd running though?
Notes
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"
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
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.
I wish Microsoft would embrace its roots as a heavy metal band
Me: I should keep my code on GitHub so I get useful bug reports and contributions
Ok friends, making 60 PowerBook 1xx batteries was fun but I think I'm done now
These are the last 8 that will be for sale
I haven't been able to sell my new PowerBook 1xx batteries internationally because nobody seems to want to deal with them on airplanes, even though I label the box and customs form that it isn't a lithium ion battery (it's nickel-metal hydride). I tried through USPS and they refused it at the border and sent it back.
Someone recently bought two on eBay through their International Shipping program where I only list them as shipping domestically and eBay has me ship to a local forwarder but they deal with repackaging it and shipping it internationally. Apparently they also failed because they just canceled this order but somehow I don't have to refund the buyer and eBay pays for it. I guess I don't get my batteries back though?