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/

NOD32 detects it as an Arch-bomb. Made me think of the somewhat similar 'Billion laughs' XML bomb but for archives.

First question and you can already sense he has no clue what that simple question means ...

  "Where are you?"
  > I am? You better ask my pig Bill. I know you are supposed to trick me.

And basic math isn't his strongest :D

  "How old are you?" > I'm 13 years old.
  "When were you born?" > I was born on the 30th of January 1988.

I never thought of that actually. In Dutch we say paper-rock-scissors (blad-steen-schaar).

According to wikipedia:

The meaning of the key's abbreviation is not explicitly given in many IBM PC compatible technical reference manuals. However, IBM states that AltGr is an abbreviation for alternate graphic, and Sun keyboards label the key as Alt Graph.

Apparently, AltGr was originally introduced as a means to produce box-drawing characters, also known as pseudographics, in text user interfaces. These characters are, however, much less useful in graphical user interfaces, and rather than alternate graphic the key is today used to produce alternate graphemes.

Here in Belgium we have to AltGr-the hell out of our keyboard during development. These characters can only be entered using the AltGr key on a Belgian Azerty keyboard (be-latin1): '|' '@' '#' '^' '{' '}' '[' ']' '\' and '~' Its not realy a problem, as long as you're used to it :-)

Would indeed be interesting to get to know some other cryptography-interetsted people on the bus, metro and other public places, so here you go: http://teespring.com/riptelegram

I constantly read about people waiting for months on their money from MtGox so I tested it a few weeks ago: I did a withdrawal of 250 EUR from MtGox to my European bank account and it took exactly 12 days. Not blazingly fast, but for sure not impossible.

Here to with 2.3.7-CM. If you explicitly check the certificate it even says: "This certificate is valid" with a reassuring green check mark. Seems legit ... These things really makes me pull out my hair.

Maybe it injects itself using some hardware hooks, more or less the same way as described in this this previously submitted article: https://news.ycombinator.com/item?id=6393029

With such a hardware root-kit, it could be possible to detect other software root-kits by looking for patterns in memory and/or other suspicious behaviour.

I'm wondering if it still contains data, if it's working.

Maybe Satoshi Nakamoto died before bitcoins got popular ...

Bugfixing is fun with Mozarts Requiem - Dies Irae :) It feels like saving the world with every commit :D

Exactly what I was thinking to :D You can hear it clear on 4:15

Hmm, I got the 0x26c4: Snowman without snow: ⛄

Here in Belgium they do

I think this is a great idea. From the moment I heard of WebSockets I was disappointed it was only a thing between the sockets-capable-web-server and the client and not a real TCP connection to wherever you want. This solves stuff :) However, I think that you should keep an eye on the possible security implications (ex. fooling the same origin policy, using your websockets proxy as a hub to attack other systems on the internet, ...)