spacecow99/ciphersuites

Repository of YAML ciphersuite fixtures vaguely in the form ciphersuite.info

ciphersuites's Issues

Add support for mbedTLS

Add reference to standards documents where available

Currently we do not track where a particular ciphersuite is defined in a standards document, however I would like to. Unsure of what the ideal approach would be (I believe ciphersuite.info maintains a separate mapping) but worth investigating.

Consider combining in to a single python package

Should consider combining this, complete_cs_instance, and complete_cs_instance, in to a single python package that supports all actions required to update the remote ciphersuite resources as well as loading in to a single data structure.

Add support for NSS

https://hg.mozilla.org/projects/nss/raw-file/tip/lib/ssl/sslproto.h

Add support for Amazon s2n ciphersuites

https://github.com/aws/s2n-tls/blob/main/tls/s2n_tls_parameters.h

Add support for LibreSSL

Add support for BoringSSL

Remove workflow from main and move it to a build branch

In order to keep main clean and free of unnecessary clutter for submodules, should look at potentially moving the workflow to a build branch and seeing if it can be run from there with changes pushed to main. Since we don't trigger on push/pull right now this should be feasible...

Add support for Schannel SSP

Add support for a mapping of ciphersuites support by various versions of the Schannel SSP.

Add a gh-pages site for visualizing data

I would like there to be a simple gh-pages site similar to those of the lolbas project to visualize the details of the available ciphersuites and different technologies/vulnerabilities. Unsure if this is best split off in to its own repo.

Remove reference to ciphersuite.info model from technologies and output

Currently models are broken up in to 5 categories with the naming convention directory.XXX, considering we are not using these in the same fashion as ciphersuite.info it is probably a good idea to remove that section of the model. For now I would like to keep to XXX portion to distinguish the different components until a better solution comes to mind.

Explore support for WolfSSL

I am honestly not sure how widely used this library is but seeing as it has so many references in the literature we should explore adding support for it.

Add support for DELL BSAFE Micro Edition Suite

We know that Oracle DB uses BSAFE MES to handle TLS, considering it is a major DBMS we should look in to adding support for it. Considering everything seems to be behind a paywall for it, I'm not sure we will be able to scrape it like the other OSS libraries so it may need to be a static fixture.

Expand technologies.yaml fixture to include additional technologies

Because we pull additional non-IANA registered ciphersuites, not all technologies in technologies.yaml account for what will be found in ciphersuites.yaml. These additional entries need to be added to technologies.yaml.

Add support for OpenJDK JSSE

https://raw.githubusercontent.com/openjdk/jdk/master/src/java.base/share/classes/sun/security/ssl/CipherSuite.java

Add support for Go crypto/tls

https://raw.githubusercontent.com/golang/go/master/src/crypto/tls/cipher_suites.go