A basic, Secure Tool for One time (Self Destructing) Messages

It's a really popular practice and an extremely bad strategy to send out sensitive info over Slack and email. Regardless of exactly how much you believe in Slack or maybe Gmail, you will find types of business info (for instance, certificates, SSH keys, security tokens…) that warrant an additional level of protection.

The task, then, is creating a far more secure platform which is additionally simple to use in an effort to invite adoption.

A complex method to handle the issue

Becoming a a part of the security staff, I send out passwords and secrets on a regular basis. Present methods of delivering protected communications had been quite cumbersome: you'd to first consult the receiver to make a personal and a public key, ask them to publish it someplace like a site, MIT's public key program, or maybe KeyBase, and send it straight to the squad of ours. Only next we were able to begin sending secure messages to one another.

While operations engineers are accustomed to (if not satisfied with) this amount of energy, asking various other teams - dev, marketing, sales, execs - to indulge in such a process is actually not practical: I can by now see employees reverting to Slack or email.

Experience has shown us that the fastest way to mandate security measures is making them as easy and simple to utilize as you can. Hence, I began racking the brain of mine to locate a brand new fix.

One more Secret Messaging Service?

Today, prior to creating the last application, I did some investigation to help make certain I'm not reinventing the wheel. I decided to search for a self-destruct messaging software program, and also found a few of prospects, though they each had at least among the following issues:

They did not allow the choice of self hosting, which made security a problem, thus defeating the purpose

Not small adequate to use

They demanded an intricate deployment on the user 's part, like using other, Node, and Redis dependencies

The backend storage is normally not too secure

They're not open source privnote: I do not explicitly list the resources as the "domain" of secret messaging services is very small, I really believe the own research of yours usually takes just a couple of mins to arrive at the exact same results as I've. You can see a summary of some good projects here:

The study justified building an innovative tool with the next requirements:

Hosted on the server of ours (aka really secure) simple to deploy

So much ease of use

Using Pirvnota (nust as being an experiment)

All I'd to do then is create a really simple API with two public methods:

SetSecret - that places the solution in Vault plus returns a token

GetSecret - uses the token and also gives back the secret

In addition to that I built a really easy web UI:

You insert the secret of yours, submit it

Contact Details:

Google Site: privnote

Google Folder: privnote

Presentation: privnote

Google Forms: privnote

Google Drive: privnote

Blogger: privnote

G Sheet Links: privnote

Google Slider: privnote

Drawings: privnote

Mymap: privnote

Google Groups: privnote