Burn-Notice is now Free Open Source

Following the example of successful SaaS (Software as a Service) Platforms like GetSentry or Travis-CI,
Burn-Notice is publishing it's source code for free and public use on GitHub.

While it might sound risky to publish security sensitive application code, Open-Source has proven to be
an extremely useful process in order to improve application security or encryption standards.

With that we are hoping to find contributors to either improve the functionality of Burn-Notice or by
finding or fixing bugs in our application security mechanisms or encryption protocols.

(Just fork it!)[https://github.com/burn-notice/burn-notice]

Encrypted communication is hard

If you ever tried to send an encrypted e-mail with GMail, you know how dispropostional hard it still is nowadays...

Even with things like GPG for Mail you have to understand how public- and private-keys work and everbody participating in the conversation has to know it as well!

Same is true for security standards like S/MIME, that should have made it simple for consumer software like e-mail clients to use encrypted or at leased signed e-mail communication.
Apple is at least coming to the conclusion that those things should be pushed forward and so iOS8 has better support for S/MIME built-in, you will be able to choose encryption and signing on a mail-by-mail basis.

Another thing that Apple does well is with their messaging system iMessage, which is built into all recent Apple operating systems on iOS and OSX.
The messaging service is supposed to be a secure communication channel under the premisis that you consider Apple to be a non diablic company...
They can, at any point, insert something into their proprietary systems that would make it possible for 3rd parties to read all communication, or maybe they alread have a backdoor builtin?
The proprietary of iMessage is also the biggest disadvantage, it's not interoperable which is kind of a no-go nowadays.

Same is true for the recently hyped messaging app Threema, which is rated pretty good in terms of security.
While it's available for iOS and Android (Windows Phone is currently under development), it's still not interoperable with Desktop-PC or OSX due to it's proprietary communication protocol.

A really good alternative to Apple and Threema is the OTR crypto protocol which builds on top of well established chat protocols like XMPP (Jabber) to encrpyt messages between two parties.
Unfortunately in the time of smartphones, handhelds, laptops and other internet enabled devices, this type of encryption has one serious drawback.
The messages can only be encrypted between the two parties initiating the encrypted communication, so messages sent from your laptop won't be readable on your smartphone and vice versa, communication get's scrambled, which leads to a horrible user experience.

The internet already has everything we need to enable secure and encrypted communication channels, it's just not simple!

Sign up to our private βeta!

We are now accepting registrations for our fire Burn-Notice private βeta!

If you are interested in participating, just add your e-mail address in our signup form!

What is it good for?

Passwords, Credit-Card-Numbers, Key-Codes, Voucher-Codes etc etc...

All those things should never be sent directly via e-mail or SMS! These communication channels are insecure because messages are not encrypted by default. A malicious user can easily gain access to your messages and steal secret or valuable information.

There are ways to secure those communication channels like PGP for email, but most of them are far from trivial to use and understand.

How does it work?

Burn-Notice relies on the simple principle of a shared secret - a security question that only sender and recipient know about. We do not store the answer in our database, it's just used as a password during the encryption process. This makes it impossible to access a Burn-Notice unless you know the correct password to decrypt it.

Following the burn after reading approach, a Burn-Notice will get destroyed immidiately after it has been read, making it impossible for a 3rd party to gain access to the information after the fact.

Interested in more detail? Check out our FAQs!