d4-project/snake-oil-crypto

Spotting and sharing weak cryptographic key materials

snake-oil-crypto

Snake-oil crypto is a term coined by Phil Zimmermann in 1991 original PGP user guide that designates bad security products that are hardly distinguishable from good ones:

like [...] automotive seat belts that look good and feel good, but snap open in the slowest crash test

The main aim of this project is therefore to provide slow speed crash tests for crypto materials: trying the easiest cracking techniques against the crypto items found in the wild.

Broadly speaking this project generates a feed of crypto materials identified as borked, or being low hanging fruits for an attacker.

Subjects

We are interested in the use of RSA and ECDSA in TLS, GPG, SSH, and OpenVPN.

Ingestion

The project will acquire crypto materials from:

• AIL clearnet/darknet crawlings,
• D4 through sensor-d4-tls-fingerprinting collections,
• a ReST API.
• existing databases of broken keys (eg. CVE-2008-0166)

Analysis

A good starting point is all Nadia Heninger et al.'s work:

• latticehacks
• facthacks

Some of these techniques and others are already implemented in RsaCtfTool.

Dissemination

Outputs (means of identifying cracked keys and along with their solutions) will be exposed through a ReST API, and MISP feeds.

Requirements

• Debian derivative, tested under Ubuntu 18.04
• python 3.7 (Use virtualenv!)
• SageMath 8.8 compiled for python 3

Install and config

• Use ./install.sh to install in a virtualenv
• Modify config.conf for configuration

Use

$ sage --python ./sage-8.8/local/bin/rq worker
$ sage --python ./snake-oil-crypto.py

snake-oil-crypto's Issues

on insert: update slices generators, touch job priority of fastest growing slices

On insertion of a key, update the slices generators, and perform gcd on the most interesting ones.

Write tests / Add Travis

Slice generator: TD-IDF for x509 issuers / subjects

Create a Tf-IDF index analyzer to create a list of interesting queries for BatchGCD.

MISP connector

Push cracked keys into a daily MISP event.

Compile information regarding a cracked key

When a key is cracked, a report should be generated, which tries to bring as much information about the victim as possible in order to ease notification.

Periodic jobs

Run periodic jobs: attack, slice, period
With slice coming from TF-IDF, or other slice generator

Move DB datastore queries inside Workers

Redis String size limit is 512MB + it's goes easier on RAM + huge pickle :/