Yeah... because Honeywell produced a product that everyone was talking about with their friends and family? Nope. They've been sitting in a dominant market position for decades without any real innovation. Innovator came along and produced a great product; Honeywell went into full patent troll mode.
Hmm, just browsing to http://pictureswap.org/success gives you the other side's image without uploading one yourself :/ That's probably not what it's supposed to do?
It's sad that someone would hack a site like this. The only thing they could possibly want are the email and password combinations. I hope they are stored in a secure way.
There are plenty of other motivations. It could be:
1) a novice hacker looking for experience
2) an automated bot that scanned IPs for some vulnerability and acted on its own when it found one
3) someone looking to extort the owner for money
4) someone with a personal vendetta against the owner
5) someone looking to secretly plant bitcoin mining software on the servers (who got caught)
6) someone looking to alter their own score to help them get some sort of math job
I could probably go on for a while, but you get the point. It's hard to ascribe intent to this sort of thing without more information.
As Project Euler is completely free and has a positive impact on the programming community, it would be very sad if the reasons for the hacking were 3) or 4).
I would discard 1) cause a real hacker, even if novice, would enter without damaging or stopping the service. He/She would maybe report to the owner the vulnerability or even would keep it secret.
It was posted elsewhere that visiting the hacked site triggered downloads of "flash_updater.exe" type trojans, so maybe one reason for the hack was to spread malware.
Think about agencies, not private actors — then this site makes a perfect target. Recruit and subvert are basic tasks for these agenices, and to do so you need information about the candidates. This website had probably a significantly higher proportion of interesting prospects.
You're talking about a cryptographically secure random. Normal random can really contain any sequence, including a repeating string of 1's or 0's. The infinite monkey theorem proves it :)
A Dutch tech news site [1] published the news on their site and got in contact with the ISP Snel:
The ISP told Tweakers that the account of Thomas White was blocked due to a security policy of the company. The customer let a deadline for verification accidentally expire and logged in through KVM. "Some KVM's generate a USB event when you use it to set up a connection to the server, this is what the customer just notified." - according to the ISP Snel. Meanwhile, the man's account is released.
Few quick points (that I found most interesting, click link to read everything):
"The likelihood of this being the work of law enforcement seems to be lower than originally anticipated. This is good in many ways but asks more questions than it solves right now."
"Support staff at the ISP have confirmed to me there has been unauthorised access to my account. This could be down to the fact I access the control panel often via Tor (yes, using TLS before anybody asks), however it does raise the prospect of a non-LE person(s) being behind this but does not explain why a chassis intrusion was detected for example or anything else to do with on-board sensors."
"Again, at this moment in time I am under no gagging orders or unreasonably withholding information under orders."
For me personally, the sweet spot between readability and compactness would be one of the first examples:
for(var i = 0; i <= 100; i++){
var out = ''
if (i % 3 == 0) out += 'fizz'
if (i % 5 == 0) out += 'buzz'
if (out.length == 0) out = i
console.log(out)
}
Not on my PC where the crash occurred. I'm using Intel graphics on my Ubuntu laptop, and there it's working perfectly. Disabling AddblockPlus seems to solve the problem though.
Exactly! I learned what a BIOS is and does the first time in my life the moment my parents put a BIOS password on the PC. My first rough workaround was to open the case, remove the CMOS battery and reset a pin. Then I found an easier workaround using the DOS debug tool to trigger a BIOS reset with the IO ports 70 and 71 :)
