Earlier quoted context omitted.
> This requires a very different model of access control and user/application privileges, and unfortunately I don't think any mainstream OS is even close to solving this one yet. I'm not sure it does require a different model of access control. It just requires people to actually use the access control mechanisms that exist already. You should not access banking details or any other sensitive information in the same…
Your proposal is OK if accessing sensitive information is something you only do occasionally, but it's not very practical to switch users completely if you deal with sensitive information often, which many people do. On the other hand, if only explicitly authorised applications can create outbound Internet connections at all, and if applications like browsers and e-mail clients need explicit permission to read a gene…
You’re infected—if you want to see your data again, pay us $300 in Bitcoins
191–200 of 295 posts
Re: You’re infected—if you want to see your data again, pay us $300 in Bitcoins
#192Earlier quoted context omitted.
It's also not auditable: Tarsnap, while not OSS, has easily available source code for perusal and personal use, if I recall.
The crashplan JARs decompile pretty easily - I had a go a few months ago, and they weren't obfuscated. Highlights: The crypto is pretty bad - it's using blowfish in CBC mode with a static IV of 0c22384e5a57412b (convert each byte to decimal...). The client-server protocol use 32 bit nonces and MACs, which is. License key validation works by decrypting some packed data from the key after converting the alphabet back t…
Re: You’re infected—if you want to see your data again, pay us $300 in Bitcoins
#193While ransomware isn't anything new, the fact that the authors of such software are using currencies like Bitcoin make it that extra bit harder to track and stop these people from extorting data. I sense a new wave of ransomware is about to hit the scene now that Ars have revealed specifics about potentially making millions a year from such a racket. It's hard informing people about these things without encouraging others to go and try writing their own ransomware and expect Bitcoin as payment.
This really worries me.
Re: You’re infected—if you want to see your data again, pay us $300 in Bitcoins
#1941. Your machine is infected, and it encrypts everything it can.
2. The 72 hour countdown begins, and during that time your machine has been re-purposed to crunch BitCoins.
3. All you have to do is wait 72 hours, and everything will un-encrypt and uninstall, leaving you perfectly fine.
Creators profit by having millions of machines crunching BitCoins in their name.
Re: You’re infected—if you want to see your data again, pay us $300 in Bitcoins
#195Re: You’re infected—if you want to see your data again, pay us $300 in Bitcoins
#196Pull-only backups were the savior here, although because we didn't notice until the next day, the pulled backups on that system were also overwritten with encrypted/corrupt files. Luckily we had VSS versioning on the pull-only backup location. There was a close call in that the 2 TB or so of "new" data ended up pushing VSS over quota and we almost lost our good versions of the files that way. If not for the VSS versions, we would've had to resort to cold backups which would've been a bit older. As it stood, no file recovered was more than a few hours old.
Auditing on the file share indicates which workstation was infected. Pertaining to that: it surprises me that in 2013, a default install of Windows will not log any useful information about shared folders by default. You must enable object auditing in Group Policy and specifically declare which users or groups are subject to said auditing on a share-by-share basis. In a world without logrotate, I suppose a sensible default is to just let a bunch of shit happen without recording it.
What gets me wound up most of all is the amount of engineering involved for an average home user to protect themselves. I thought a Mac with Time Machine was enough, but a similar virus would easily corrupt those backups if they were available to it over a mapped drive.
It is the goddamn 21st century, and users are still losing work by overwriting documents by accident, or opening a document as an e-mail attachment and not being able to find the actual file they edited. Should people really need an IT guy with ten years of experience to be protected from simple mistakes? Google has made progress on that front with the Chromebook, I suppose.
Re: You’re infected—if you want to see your data again, pay us $300 in Bitcoins
#197Earlier quoted context omitted.
Here's one: https://blockchain.info/wallet/send-shared (Please note, before downvoting, that I'm not saying that's a bad thing)
there is no downvoting
Re: You’re infected—if you want to see your data again, pay us $300 in Bitcoins
#198Re: You’re infected—if you want to see your data again, pay us $300 in Bitcoins
#199Re: You’re infected—if you want to see your data again, pay us $300 in Bitcoins
#200And for those who say "my mother can't use Linux", don't be a cheapskate, get your loved ones a Mac - they will definitely know how to use it.