Comment Re:Not Coming to a Switch Near You (Score 1) 91
That hackers keep using WebKit exploits is probably the main reason the Switch doesn't have a user-accessible web browser app; the 3DS was also hacked via its YouTube app, which is also why the Switch is probably lacking similar 3rd-party apps -- they want to ensure the app's security first.
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.
Comment Mozilla has the right idea with PDF.js (Score 1) 85
Comment Re:Idiocy (Score 1) 77
They really should not be done unless there is an actual problem that will actually be solved by the update.
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.
Comment Sophos Too (Score 1) 77
Comment Not Hard to Fix (Score 1) 407
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
Comment Re:Poor Update Process (Score 1) 71
Comment Poor Update Process (Score 2) 71
Comment Been using Nightly for a while. (Score 3, Interesting) 181
Comment We have implemented DMARC + DKIM + SPF (Score 1) 139
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.
Comment Prime Example of Software Bloat (Score 5, Interesting) 121
- Notepad++: 7.3MB
- Sublime Text: 7.6MB
- BBEdit: 12.5MB
- Atom - 67MB
Comment Re:Last Sentence (Score 5, Informative) 322
This is a close call, but I conclude that Feldman's act of production, which would necessarily require his using a password of some type to decrypt the storage device, would be tantamount to telling the government something it does not already know with "reasonably particularity"
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.