anirbandd
Conversation Architect
Source:reddit
is 100% true.
but now, i'll have to top up my phone balance physically. no more net banking for a long time.
Source:reddit
Source:reddit
what the hell
there is much more
pretty sure NSA is also using this exploit
The Heartbleed Hit List: The Passwords You Need to Change Right Now
Don't change your password. It's strange advice to hear when the so-called Heartbleed bug is leaving databases all over the web open and exposed, but it's applicable. Yes, security has been compromised for many of your favorite websites and services (including Google, Flickr and Steam, at least initially) but protecting yourself isn't quite as easy as changing your password. Unlike past exploits, Heartbleed isn't a database leak or a list of plaintext logins; it's a flaw in one of the web's most prevalent security protocols -- and until its fixed, updating your login information won't do a darn thing to protect you. What, then, can you do to protect yourself? Wait, watch and verify.
Does going incognito helps?
Are you sure you thought? *boughtLast year I thought something from Amazon UK using my Credit card. My Credit card has password authentication for transaction. But to my surprise transaction is passed without asking password. So its still vunerable
Short answer no.
The bug affects how OpenSSL, the most widely used cryptographic library for Apache and nginx Web servers, handles a service of Transport Layer Security called Heartbeat—an extension added to TLS in 2012.
Heartbeat allows a connected Web client or application to send messages to keep a connection active during a transfer of data. When a Heartbeat message is received, the server usually simply echoes back what it got to the sender. However, starting with the initial implementation of Heartbeat in OpenSSL 1.01 (and in all subsequent releases up to OpenSSL 1.01f, including the OpenSSL 1.0.2 beta) the extension could be fooled into sending back the contents of its memory buffer by sending a request that advertised itself as 64 kilobytes long but in fact had no content—resulting in “Heartbleed".
Does going incognito helps?
This bug is turning into a nightmare, a lot of the projects handled by our company uses OpenSSL, guess they are all screwed, got some frantic mails from Corporate division, they are asking to shut down all OpenSSL based projects so they can send teams to patch it
Remedy: use lastpass..
The LastPass Blog: LastPass and the Heartbleed Bug
- - - Updated - - -
Also check in your favorite in here for the vulnerability:
*lastpass.com/heartbleed/