HN user

ulldma

33 karma

working at the GitHub Security Lab

Posts11
Comments10
View on HN

Hey! I’m one of the authors of this blog post. We (the GitHub Security Lab) developed an open-source AI-framework that supports security researchers in discovering vulnerabilities. In this blog post we show how it works and talk about the vulnerabilities we were able to find using it (including viewing PII of other users in online shops and logging into a popular chat application service using ANY password)

Well, Microsoft often uses suspicious looking URLs for their services. E.g. Office/OneDrive connects to hosts like "oneclient.sfx.ms" and "auth.gfx.ms". So as a user you have to trust these domains and you also have to trust the domain management of the island of Montserrat.

Signed HTTP Exchanges (or SXG) enables loading Web contents signed by the content publishers from anywhere, e.g. from a fast server, as if they came from the original publishers.

Correct me if I'm wrong, but this seems to be part of a greater vision (as heard before). Not only is the transported content protected by TLS, the content is also signed by the publisher and can be loaded from other servers. E.g. makes sense in an AMP context. (As you still know that the content was produced by your newspaper)

Yes, this is important: Maven Central/Sonatype only checks if the submitted artifacts are signed (regardless of the used key).

The work is shifted to client, but there's currently no standardized way on how to verify dependencies and plugins.

There's an issue in the Maven bug tracker with the idea to extend the POM to allow trust information: https://issues.apache.org/jira/browse/MNG-6026