By Soulskill from Slashdot's my-place-or-yours department
An anonymous reader writes: Since 2012, WikiLeaks founder Julian Assange has been holed up inside Ecuador's embassy in London trying to avoid extradition to Sweden, where he faces a sexual assault investigation. Now, after the case has been stalled for years, Swedish prosecutors are arranging to come to London and question Assange within the embassy. According to his lawyer, Assange welcomes this, but Sweden still needs to be granted permission from both the UK and Ecuador. "Assange's lawyers, who are appealing against his arrest warrant in Sweden's highest court, have complained bitterly about the prosecutor's refusal to travel to London to speak to him – an essential step under Swedish jurisprudence to establish whether Assange can be formally charged. [Lead investigator Marianne] Ny's refusal, they say, has condemned Assange to severe limitations on his freedom that are disproportionate to the accusations against him." Ny has also requested a DNA sample from Assange.Read Replies (0)
By timothy from Slashdot's first-world-problems department
An anonymous reader writes A new piece of ransomware that (mis)uses the Cryptolocker "brand" has been analyzed by Bromium researchers, and they discovered that aside from the usual assortment of file types that ransomware usually targets, this variant also encrypts file types associated with video games and game related software. It targets files associated with single-user games Call of Duty, Star Craft 2, Diablo, Fallout 3, Minecraft, Half-Life 2, Dragon Age: Origins, The Elder Scrolls and specifically Skyrim-related files, Star Wars: The Knights Of The Old Republic, WarCraft 3, F.E.A.R, Saint Rows 2, Metro 2033, Assassin's Creed, S.T.A.L.K.E.R., Resident Evil 4, Bioshock 2; and online games World of Warcraft, Day Z, League of Legends, World of Tanks, and Metin2.
Here's the Bromium Labs report
.Read Replies (0)
By timothy from Slashdot's that's-a-shame department
An anonymous reader writes GitHub has officially won. Google has announced that Google Code project creation has been disabled today, with the ultimate plan to kill off the service next year. On August 24, 2015, the project hosting service will be set to read-only. This means you will still be able to checkout/view project source, issues, and wikis, but nobody will be able to make changes or new commits. On January 25, 2016, Google Code will be shut down. Google says you will be able to download tarballs of project source, issues, and wikis "throughout the rest of 2016." After that, Google Code will be gone for good.Read Replies (0)