Notes

joshua stein via @jcs@jcs.org - Mar 10 2024 09:44:29

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

joshua stein via @jcs@jcs.org - Feb 28 2024 11:17:46

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

joshua stein via @jcs@jcs.org - Feb 26 2024 21:49:29

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".