flux_w42

Actually it's the other way around: http://www.wsj.com/articles/honeywell-google-settle-lawsuit-...

It seems to be related to the user names. Just received a 'Howdy' alert box :)

That logo is a lawsuit waiting to happen.

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.

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.

[1] https://tweakers.net/nieuws/100388/beheerder-verliest-contro...

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.

Same for me: Running on Firefox 31.0 (Windows 7) and i can crash it every time ...

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 :)

Ouch, thats bad :) C12.22 is pretty old, AES didn't even exist yet. It seems that it got an update recently (2011) with the smart grid and smart metering use case in mind. The are now using an EAX called EAX prime [1] put it seems to have it's own issues [2].

[1] http://csrc.nist.gov/groups/ST/toolkit/BCM/documents/propose... [2] http://eprint.iacr.org/2012/018.pdf

It's mainly used in Europe. The US has a very similar, but older protocol called ANSI C12. The C12.22 spec includes authenticated encryption, but I'm not familiar with the details.

There is a standard for smart meters called DLMS [1]. It's the most used protocol for smart meters for a while now. The protocol supports two way authentication and uses AES-GCM.

Providing a secure medium for meter communication is in the interest of both the user and the power companies: Users are protected from malicious commands to the meter (using the breaker to disconnect your power, changing the used tariff, ...) and power suppliers prevent fraud.

[1] http://www.dlms.com/