Live AWS keys in 75 throwaway repos, each made public for one of five windows from 60 seconds to 12 hours, every use logged. The keys were tripwires; the real question was who notices a private repo going public, and what they do once they're in.

The most useful finding is the dull one: re-hiding the repo does nothing. One busy harvester kept re-validating the captured keys for a day after the repos went private again. Only rotating the key stops it.

This came out of building a monitor for exactly these repo-setting changes.

you are viewing a single comment's thread
view the rest of the comments
[–] 97 points 1 month ago (3 children)

Info for anyone reading, while the read was quite interesting, the whole article turned out to be an ad.

  • source
  • hideshow 6 child comments
  • [–] 17 points 1 month ago

    From the post description this made it obvious it's an ad for something. Otherwise it sounded like someone actually made reasearch on the subject.

    This came out of building a monitor for exactly these repo-setting changes.

  • source
  • parent
  • [–] [S] 4 points 1 month ago (1 child)

    Fair to call out. This did come out of me building a product in the space, and I'd rather disclose that than bury it. The method and numbers are real, happy to get into either.

  • source
  • parent
  • hideshow 2 child comments