200 Follower Special:

turning seasons 🌸🌻🍁❄️

. .

start of new cycle of spring, time to finally posting the full sets!

thinkin

A proposal

Sometimes, in fandom, we just want to write id-tastic fic that rolls around in tropes that might be viewed as problematic. But we don’t want to address the problematic side of things in this particular fanwork; we just want to roll around and wallow.

It is considered courteous to give readers a heads-up via use of AO3 tags. I propose a tag that signals that a given fanwork is for rolling around, not giving a measured evaluation of anything. The MCU has carved out a space for this sort of fic with the “HYDRA Trash Party” tag, for which I commend them. Trash Party is a bit too specific to cover all of the ground I’m thinking of here, though; I propose “Dead Dove: Do Not Eat.”

For those of you not familiar with Arrested Development, Michael Bluth finds a paper bag in the freezer labeled “Dead Dove: Do Not Eat.” He opens the bag, finds a dead dove, and reacts as follows:

[gif of a white man saying “I don’t know what I expected” in a deadpan manner]

The “Dead Dove: Do Not Eat” tag would essentially be a “what it says on the tin” metatag, indicating “you see the tropes and concepts tagged here? they are going to appear in this fic. exactly as said. there will not necessarily be any subversion, authorial commentary condemning problematic aspects, or meditation on potential harm. this fic contains dead dove. if you proceed, you should expect to encounter it.”

(more at KnowYourMeme: http://knowyourmeme.com/memes/i-dont-know-what-i-expected)

fein and couri as their main val characters

loaf with mama

MCSR MAKEUP!!!

day 1: feinberg :3

Malwarebytes

All Gmail users at risk from clever replay attack

All Google accounts could end up compromised by a clever replay attack on Gmail users abusing Google infrastructure.

Cybercriminals are abusing Google’s infrastructure, creating emails that appear to come from Google in order to persuade people into handing over their Google account credentials. This attack, first flagged by Nick Johnson, the lead developer of the Ethereum Name Service (ENS), a blockchain equivalent of the popular internet naming convention known as the Domain Name System (DNS). Nick received a very official looking security alert about a subpoena allegedly issued to Google by law enforcement to information contained in Nick’s Google account. A URL in the email pointed Nick to a sites.google.com page that looked like an exact copy of the official Google support portal.

As a computer savvy person, Nick spotted that the official site should have been hosted on accounts.google.com and not sites.google.com. The difference is that anyone with a Google account can create a website on sites.google.com. And that is exactly what the cybercriminals did. Attackers increasingly use Google Sites to host phishing pages because the domain appears trustworthy to most users and can bypass many security filters. One of those filters is DKIM (DomainKeys Identified Mail), an email authentication protocol that allows the sending server to attach a digital signature to an email. If the target clicked either “Upload additional documents” or “View case”, they were redirected to an exact copy of the Google sign-in page designed to steal their login credentials. Your Google credentials are coveted prey, because they give access to core Google services like Gmail, Google Drive, Google Photos, Google Calendar, Google Contacts, Google Maps, Google Play, and YouTube, but also any third-party apps and services you have chosen to log in with your Google account. The signs to recognize this scam are the pages hosted at sites.google.com which should have been support.google.com and accounts.google.com and the sender address in the email header. Although it was signed by accounts.google.com, it was emailed by another address. If a person had all these accounts compromised in one go, this could easily lead to identity theft.

How to avoid scams like this

Don’t follow links in unsolicited emails or on unexpected websites.

Carefully look at the email headers when you receive an unexpected mail.

Verify the legitimacy of such emails through another, independent method.

Don’t use your Google account (or Facebook for that matter) to log in at other sites and services. Instead create an account on the service itself.

Technical details Analyzing the URL used in the attack on Nick, (https://sites.google.com[/]u/17918456/d/1W4M_jFajsC8YKeRJn6tt_b1Ja9Puh6_v/edit) where /u/17918456/ is a user or account identifier and /d/1W4M_jFajsC8YKeRJn6tt_b1Ja9Puh6_v/ identifies the exact page, the /edit part stands out like a sore thumb. DKIM-signed messages keep the signature during replays as long as the body remains unchanged. So if a malicious actor gets access to a previously legitimate DKIM-signed email, they can resend that exact message at any time, and it will still pass authentication. So, what the cybercriminals did was: Set up a Gmail account starting with me@ so the visible email would look as if it was addressed to “me.” Register an OAuth app and set the app name to match the phishing link Grant the OAuth app access to their Google account which triggers a legitimate security warning from no-reply@accounts.google.com This alert has a valid DKIM signature, with the content of the phishing email embedded in the body as the app name. Forward the message untouched which keeps the DKIM signature valid. Creating the application containing the entire text of the phishing message for its name, and preparing the landing page and fake login site may seem a lot of work. But once the criminals have completed the initial work, the procedure is easy enough to repeat once a page gets reported, which is not easy on sites.google.com. Nick submitted a bug report to Google about this. Google originally closed the report as ‘Working as Intended,’ but later Google got back to him and said it had reconsidered the matter and it will fix the OAuth bug.

the fundamental problem on this website is that if a homeless person tried to talk to most of y’all you’d be scared out of your minds