Ask HN: What are the U.S. requirements for releasing OSS that uses encryption?

This page summarizes the projects mentioned and recommended in the original post on news.ycombinator.com

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • plusaes

    Header only C++ AES cipher library

  • I want to release a terminal based text editor I wrote, on GitHub, that uses another open source library that implements AES-CBC 256 bit encryption. The library it specifically uses is https://github.com/kkAyataka/plusaes

    I'm wondering, what are any United States legal requirements for releasing my text editor as open source software?

    My text editor only uses existing available open source software and does not implement any new cryptographic algorithm, but based on my reading of United States export restrictions I'm not entirely certain if there's reporting requirements I must follow. To clarify, I don't need to release this, I just wanted to contribute something back to the community that's been useful to me.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts