News for hackers. Stuff that matters.

A comment on Skype's Principal Architect explains why peer-to-peer was eliminated. Parent comment

Re:Skype's Principal Architect explains why peer-to-peer was... by atesti on Monday June 24, 2013 @05:37AM (#5931907)
And let's not forget how Microsoft scanned all private urls that were mentioned inside Skype chats recently:

http://seclists.org/fulldisclosure/2013/May/78

[ Parent | on HN ]
Re:Skype's Principal Architect explains why peer-to-peer was... by bskap on Monday June 24, 2013 @12:07PM (#5933803)
Um yes, that's covered in the "malicious URL removal" part. Hard to do malicious URL removal without, you know, looking at the URLs to see if they need to be removed.
[ Parent | on HN ]
Re:Skype's Principal Architect explains why peer-to-peer was... by alephnil on Monday June 24, 2013 @01:44PM (#5934469)
Except that they only checked HTTPS URLs, and most malicious URLs are on HTTP, which they apparently not checked.
[ Parent | on HN ]
Re:Skype's Principal Architect explains why peer-to-peer was... by bskap on Tuesday June 25, 2013 @10:25AM (#5939617)
Are you an expert in this domain or are you just parroting what the article said? I can think of at least one reason for a spam filter to contact the computer for an HTTPS request but not for an HTTP request- you want to find out what certificate they're using.
[ Parent | on HN ]