squirrelitude: (Default)
Somewhere in the past days or weeks, Google started either bouncing email without a DKIM signature or is silently filing it as spam. (DKIM: DomainKeys Identified Mail, an anti-spoofing measure.)

If you receive email at a domain you registered, there is a good chance that recipients who use Google Mail are not receiving it. You'll need to ensure that you're getting a DKIM "pass" result that matches your domain name.

For example, I use Fastmail. GMail was indicating "DKIM PASS from messagingengine.com" (that's Fastmail's actual mail service) but was still rejecting my mail. Once I added the DNS records that Fastmail indicating I needed to add in their settings page for my domain, I instead started getting "DKIM PASS from [my actual domain]" and my mail started getting through.

(While DKIM is a reasonable tool and it's fine that Google is using this as part of their spam check, I suspect they're doing this strict version to try to solidify their position by further freezing out other mail providers.)
squirrelitude: (Default)
This past Saturday night, our whole household came down sick. Close to midnight, Elusiveat had a sudden onset nausea and weakness, I suddenly had drainage and coughing, and between the two I only got about 4 hours of sleep.

Sunday was awful. I got what felt like tension and soreness in my bronchi when I inhaled too fast, and deeper inhales provoked a cough. I coughed a bunch in the morning, and it was eventually productive, after which the coughing stopped -- which was like the daily routine I had had for a month or so late in the winter. I also developed a low fever, maxing out at 101.0°F, complete with chills. Lethargy, headache, sore hips, sensitive skin, anhedonia. Elusiveat and I basically spent the whole day either sleeping or lying around. Even the kid was a bit sick, although just with the chest discomfort.

And then by evening it was lifting, and on Monday we felt fine. So what the heck was that all about?

My first guess had been influenza, but we all would have to have been exposed at the same time, and the only plausible route would have been food-borne/fomite from a takeout meal. Even then *all* of us catching it that way wouldn't be plausible. Another possibility was some kind of allergen, but nausea didn't fit the pattern. And there was a previous episode of this a couple months ago, prompting us to get COVID-19 tests, but only I experienced it then. Maybe the mold from the shiitake grow block that was starting to die? Not real likely.

My best guess at this point is that it was Legionnaires' disease. I had had the humidifier on in the living room for a big chunk of the winter, and I eventually fell out of the routine of cleaning it one or two times per week. The antimicrobial bar inside it is also pretty old and likely no longer working. Legionella bacteria grow in warm, stale water and the humidifier stays a bit warm thanks to having an internal transformer; Legionella is also primarily spread via aerosolized soil or water. (It's named for an outbreak at an American Legion conference, traced to the hotel's HVAC.) And I had just switched the humidifier back on the day before after a long break, which I think might line up with the morning cough I had for a while. It might be something else that was growing in the water, but... close enough for an explanation, and enough to give me confidence that it's not something contagious.

So. Yes. I'll definitely be better at following the instructions for the humidifier in the future, and maybe be a little more cautious about using it.
squirrelitude: (Default)
The new Massachusetts state vaccination system is now live: https://vaccinesignup.mass.gov/ The signup process was pretty painless.

You can now pre-register with all the information they need in order to determine your eligibility. The plan is that as people become eligible, they'll be offered appointments in nearby mass vaccination locations, which they can either accept or decline. (This does not include the vaccinations offered at pharmacies, doctor's offices, and hospitals.)

I don't know whether they'll be randomizing within each newly eligible group or whether appointments will be offered first to those who signed up first -- I hope it's the former, and I wish they gave some indication of that.
squirrelitude: (Default)
Dreamwidth is a little unusual in giving everyone their own subdomain. Off the top of my head, I can only think of three other sites that do this: Its predecessor (Livejournal), Tumblr, and DeviantArt. There are almost certainly others, but it's uncommon.

Even though all communications to the site are done over a secure connection, so the *contents* of the pages are hidden from your ISP, any government interlopers, nosy parents who have installed spyware on the home router, and people snooping on your use of insecure café WiFi... the domain name you're visiting (here, squirrelitude.dreamwidth.org) is still being broadcast in two ways:


  • When your computer asks the Domain Name System for the IP address of the site, it sends the domain name out in the clear[1], and the DNS server of course knows what domain you're asking for
  • When your computer then connects to that IP address, it mentions the domain name in the initial message to the server[2]


That means that within a few minutes of poking around on Dreamwidth, anyone who can watch your internet traffic likely knows 1) who your friends are, and 2) by that token, who *you* are. (If you stick to just your Reading Page, you are not leaking your circle's usernames to any watchers, but you are leaking your own.)

I feel like this is maybe something that could and should be changed, since DW is already a centralized service and doesn't *need* separate domain names. (My social media prototype will *need* it, to some extent, which is a sobering thought.) I don't know if I believe this strongly enough to advocate for it,

Another option is to access DW via Tor! I just fired up TAILS and confirmed that I can log in to Dreamwidth just fine. [3] (No captchas or other nonsense.) Unlinking your home IP from the domain you're visiting (and those domains from each other) in the eyes of someone snooping on network traffic is *precisely* what Tor is for. So regardless of whether DW takes action on this, if this is a privacy issue for you, there is a way you can protect yourself. (Also applies to Tumblr, DeviantArt, etc.)


[1] This first part does not apply for people using experimental DNS-over-HTTPS—only the DNS server can read the request

[2] The Server Name Indication TLS header, which is unencrypted in current versions of TLS. TLS 1.3 allows encrypting it, but that's still being rolled out.

[3] Tor is quite safe to use as long as you're visiting HTTPS websites, which is most sites these days. But advice to heed browser warnings about invalid certificates applies doubly so over Tor. If you ignore those, Tor becomes *less* safe than using the internet directly. So don't. :-)
squirrelitude: (Default)
Scammers have gained access to a list of Livejournal usernames and passwords. I'm not sure how long ago the breach was, but your best bet is to change your password now. Also, if you used that password anywhere else, change your password there as well and if possible check those accounts for signs of compromise. (Change them all to *different* passwords. Use a password manager such as 1Password or Firefox's built-in password manager, or just memorize them and write the less important ones down in a physical notebook.)

Source: People (including myself) are receiving scam emails with some bullshit claim about having installed malware, giving an email address and password as proof. They're using emails and passwords from compromised sites, such as Last.fm, LinkedIn, and now Livejournal. LJ was not known to be compromised, but it's not at all a surprise to me. Other sources:

- https://bifurious.co.uk/livejournal-compromised-in-more-ways-than-one/
- https://siderea.dreamwidth.org/1453052.html
- https://dw-news.dreamwidth.org/38612.html (doesn't name LJ, but you know it)
- https://www.livejournal.com/support/request/?id=2085067 (has since been locked down, although I archived it first and have since been in touch with that user)

You can sign up for https://haveibeenpwned.com/ to keep abreast of further password database breaches (and other leaks of your personal information) although Troy hasn't yet posted about this one, probably since the leaked DB hasn't yet made its way into his hands.

(There is not yet evidence that anyone has used the passwords to log into LJ and scrape your post and comment history and the posts and comments of your friends, but it could happen. If you have abandoned LJ but have *not* wiped out all your posts and unfriended everyone, please go ahead and change your password anyway to protect your friends.)

Update 2018-10-09: I can confirm that the breach happened on or before 2017-04-27. In that first link, a commenter narrows it down to the 2011–2014 window.

Update 2020-05-08: Spammers started using the dump to take over DW accounts and advertise their sites: https://dw-maintenance.dreamwidth.org/81865.html

Profile

squirrelitude: (Default)
squirrelitude

August 2024

S M T W T F S
    123
45678910
11121314151617
18192021222324
25262728293031

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Dec. 28th, 2025 05:13 pm
Powered by Dreamwidth Studios