Wouldn't this just reinforce the self-created echochambers on Twitter?

If Nintendo could be bothered to ship a WebKit that wasn't 6+ months old it wouldn't be such a security nightmare for them.

This is why instead of embedding a plugin in the browser for PDFs, Mozilla has created PDF.js. It uses HTML5 & JavaScript to render PDFs within the browser's normal sandbox. There's even a Chrome addon.

Given that many UEFI updates patch security flaws, it's a good idea to keep up to date. BIOS had its issues, but UEFI offers a much larger attack surface.

Sophos Antivirus's AutoUpdate feature flows over HTTP. This has been a known issue since 2013 and Sophos doesn't care.

As someone who has been deploying Windows 8.1 for a while, it's pretty easy to remove apps you don't want from your system images. You can even do it on a running system:

Get-ProvisionedAppxPackage -Online | where-object {$_.DisplayName -eq "Microsoft.WindowsStore"} | Remove-ProvisionedAppxPackage -Online

That makes sense. I don't use the Kindle store frequently so I never would have seen it there.

I received an email encouraging me to update my 2015 Kindle not long ago. I tried to check for updates on the device but found nothing. Two weeks later, Amazon sent me a similar message again. After another update check, I still found nothing. I wasn't able to get the device to upgrade until I manually copied the firmware file to the device.

My daily web browser is Nightly. A few days ago when they enabled e10s by default I found out about the change because my browser crashed on startup. The only way I could get it working again was to start Nightly in Safe Mode and disable e10s. Multiprocess in Nightly is varying states of very broken for most addons. For me the key ones are HTTPSEverywhere, Adblock Plus, and Reddit Enhancement Suite. None of these addons are functional with e10s enabled currently.

In my org (a high school) we were having issues with spambots using our organization's address in the From: field for spam campaigns. The turning point for us was when a malware payload came with a From: field of the assistant principal addressed to many of our employees. The mail was not from one of our mail servers, but the From field trick some of our users into opening it. With DMARC + DKIM and a strict policy we have eliminated this problem.

We did have some minor implementation headaches. Our admissions team's spam mailing vendor was non-compliant with DKIM and would not work with us to set up authenticated mail. We resolved our issue with them by making the admissions guys send mail from a more permissive subdomain so that we could implement the strict protections on our primary domain.

All that said, the implementation was not incredibly difficult. We use Google Apps for our mailing, and a SMTP server on-campus to allow our applications to send mail. Google DKIM+DMARC is easy, and there are plenty of guides on implementing DKIM in Postfix. Overall I think the change has been worth it. I'm a little frightened at all of the abuse reports I see now that otherwise would have gone out in our domain's name.

• Notepad++: 7.3MB
• Sublime Text: 7.6MB
• BBEdit: 12.5MB
• Atom - 67MB

I'm guessing this is the trick. The government doesn't know there is evidence on the storage device. It sounds like they are making the argument that compelling a password for discovery purposes is a violation, but providing one to give them what they know you have is not. At least, that's what it seems like they are saying to me.

I get by by running a VPN server at my house and then connecting to that while I'm on the go.