Our mission is to make the world a safer place to do business online -- for people and for companies. We're doing this by building tools to help people make software (or at least the data it handles) fundamentally more secure against attack and fundamentally more private. We'd like to invite our users, fans, people thinking about these topics, and people thinking about using IronCore's products to join our community to talk openly (or not, if needed) about what you're building, to solicit help, give advice, ask and answer questions, make feature suggestions and so forth. Please join us and let's make the world a bit better together!
Please join us in one of these two places:
- The IronCore Github Forum is the best place to ask questions whose answers might be helpful to others, to post feature requests, to report bugs, and to have in-depth discussions on how we tackle the bigger problems. This is a space where interactions may be long-lived.
- The IronCore Discord Server is a great place to ask quick questions, share your work and to get to know other IronCore users over asynchronous chat. This is meant to be a bit less formal. This is a somewhat ephemeral community space.
As part of our mission, we have a strong emphasis on open-source software. Much, but not all, of the IronCore products are released as open source under various licenses. You can browse our repos or jump straight to one of interest. Here are some of the noteworthy projects we maintain:
- Data Control Platform
- Low-level crypto libraries
- recrypt-rs -- proxy re-encryption / transform cryptography library in rust (audited, constant time)
- gridiron -- constant time big number math library used by recrypt-rs
- recrypt -- proxy re-encryption / transform cryptography library in scala (audited, not constant time)
- recrypt-wasm-binding -- build recrypt-rs for use in browsers
- recrypt-node-binding -- build recrypt-rs for use in node
- High-level crypto libraries (these use recrypt)
- ironoxide -- rust library for interacting with the proxy re-encryption service
- ironnode -- node bindings for ironoxide
- ironweb -- web bindings for ironoxide
- ironoxide-swift -- swift bindings for ironoxide for iOS
- ironoxide-swig-bindings -- bindings to ironoxide for C++, Java and Android
- ironoxide-scala -- bindings to ironoxide for Scala
- Command line tools
- ironoxide-cli -- command line interface for IronOxide functions to create users, devices, and groups
- ironhide -- command line tool for encrypting files to groups or users
- Low-level crypto libraries
- SaaS Shield
- tenant-security-client-nodejs -- NodeJS client for the tenant security proxy
- tenant-security-client-java -- Java client for the tenant security proxy
- tenant-security-client-php -- PHP client for the tenant security proxy
- Other
- phonentic-normalizer -- store latin-language words in pseudo-phonetic form
- futurejs -- promise-alternative library for asynchronous operations
- cats-scalatest -- Scalatest bindings for Cats
If you contribute to the IronCore organization on GitHub, we'd love to offer you some free swag. You can claim your swag by logging into the IronCore Store and requesting a discount code. With five or more contributions, you can claim your swag credit.
If you've contributed in other ways, such as giving talks about IronCore, teaching others to use it, writing IronCore articles/tutorials, participating in an IronCore research project, or any other way, please fill reach out to let us know!
It should go without saying, but a community is a place for respectful interactions and the IronCore community is a place where people are meant to debate ideas, architect solutions, and help each other. This is not a place for shaming people (for example, for poor security practices or lack of knowledge or understanding) or any other behavior that would make people feel unwelcome. The unwritten rules of the physical world, sadly need to be written down and enforced in the digital one. To that end, we have a fairly standard code of conduct that applies to our community.