The Internet is a huge place. Some parts of it are awesome, but others are…less so. And falling squarely in that latter category is the ancient .su domain, once the cyberhome of the Soviet Union . It’s not exactly well maintained, or well policed, which is why more and more online criminals are using it as a hideout. Read more…
More here:
Tons of Hackers Are Hanging Out in Old Soviet Cyberspace
wiredmikey writes “Google on Tuesday announced that it now fully supports DNSSEC (Domain Name System Security Extensions) validation on its Google Public DNS resolvers. Previously, the search giant accepted and forwarded DNSSEC-formatted messages but didn’t actually perform validation. ‘With this new security feature, we can better protect people from DNS-based attacks and make DNS more secure overall by identifying and rejecting invalid responses from DNSSEC-protected domains,’ Yunhong Gu, Team Lead, Google Public DNS, wrote in a blog post. According to Gu, about 1/3 of top-level domains have been signed, but most second-level domains remain unsigned. According to NIST, there has been no progress in enabling DNSSEC on 98 percent of all 1,070 industry domains tested as of March 18, 2013. ‘Overall, DNSSEC is still at an early stage and we hope that our support will help expedite its deployment,’ Gu said.” Read more of this story at Slashdot.
Read More:
Google Implements DNSSEC Validation For Public DNS
DECula writes “In a move not communicated to its users before hand, Google’s Gmail servers were reconfigured to not connect to remote pop3 servers that have self-signed certificates, leaving folks with unencrypted connections, or no service when getting email from other services. Not good for the small folks. One suggestion was to allow placing the public keys on Google’s side in the user configuration. That would be a heck of a lot better than just dropping users into never never land.” Apparently, “valid” now means “paid someone Google approves to sign the certificate.” It’s not like commercial CAs have the best security track record either. Read more of this story at Slashdot.
Visit site:
Gmail Drops Support for Connecting To Pop3 Servers With Self -Signed Certs
An anonymous reader writes “Darren Nix works for 42Floors, a business that uses its website to help people find office space. He recently received a marketing email for a service that offered to identify visitors to his website. After squeezing some information out of the marketer and playing around with a demo account, he now explains exactly how sketchy companies track your presence across multiple websites. The marketer offered to provide Nix with ‘tracking code that would sit in your web site’ which would ‘grab a few key pieces of data from each visitor.’ This includes IP addresses and search engine data. The marketer’s company would then automatically analyze the data to try to identify the user and send back whatever personal information they’ve collected on that user from different websites. Thus, it’s entirely possible for a site to know your name, email address, and company on your very first visit, and without any interaction on your part. Nix writes, ‘A real-world analogue would be this scenario: You drive to Home Depot and walk in. Closed-circuit cameras match your face against a database of every shopper that has used a credit card at Walmart or Target and identifies you by name, address, and phone. If you happen to walk out the front door without buying anything your phone buzzes with a text message from Home Depot offering you a 10% discount good for the next hour. Farfetched? I don’t think so. … All the necessary pieces already exist, they just haven’t been combined yet.'” Read more of this story at Slashdot.
Continue Reading:
How Websites Know Your Email Address the First Time You Visit