PUBLIC MARKS with tag security

Security researchers and the networks they rely on were at risk of breach by the hackers they investigate, thanks to now mitigated man-in-the-middle holes in a popular plugin for analysing debugger OllyDbg.

H4cktimes.com Siber Uzay'ın Haber Platformu

Modern web development has many challenges, and of those security is both very important and often under-emphasized. While such techniques as threat analysis are increasingly recognized as essential to any serious development, there are also some basic practices which every developer can and should be doing as a matter of course.

First european bug bounty platform that relies on european economic area rules, principles and legislation.

In November 2015, a video was released to the public showing 17-year-old Laquan McDonald— a black kid who went to school in Chicago’s South Side—being shot 16 times in less than 15 seconds by Jason Van Dyke, a white officer with the Chicago Police Department. Protests erupted around the country, and to this day, protests continue in Chicago. Not only was this an example of an officer brazenly ignoring protocol and killing another human being with wanton disregard for the law, it was also evidence of an apparent cover-up: McDonald was killed in October 2014, and it took at least one lawsuit and 13 months for the city to hand over the video—seemingly an inherently public record—to journalists and lawyers working the case.

Google recently announced a security policy change that will impact future versions of the Chrome browser. Chrome is already warning that support to powerful features on insecure origins (HTTP) is deprecated, and according to recent announcements the removal will take place soon.

After we published this post Google announced that they are pushing back the release date of the HTTPS security change. They’re estimating that it will now be released to production in December 2015.

As with gradually marking HTTP as non-secure, we expect to gradually migrate these features to secure-only, based on thresholds of usage, starting with lowest usage and moving towards higher. We also expect to gradually indicate in the UX that the features are deprecated for non-secure origins.