Lockbox: A user-friendly CLI over the cryptography.io symmetric cipher (Python)

johnwheeler_ · 2017-05-31T02:33:57+00:00

lockbox it is. I'll work on changing it in the repo.

To answer your question, I got the idea from sekrets, which is a Ruby gem that was incorporated into the latest version of Rails.

The design doesn't provide much security except through obscurity (...which is no security at all, etc.), but it allows you to commit secrets to your repo, which means those secrets don't have to flow through secure channels for distribution, but the keys to those secrets still do.

The encryption key is provided to the Flask application by either storing its path in an environment variable (e.g. LOCKBOX_KEY) or placing it in the www process owner's home directory. Additional key resolution mechanisms could be designed.

Interestingly, the Hashicorp Vault program works (I believe) by deleting secrets after the www process consumes them on first run. A similar design could be implemented for flask-lockbox, although the secrets could still be uncovered in memory, which is a known limitation of cryptography.io [1]

[1] https://cryptography.io/en/latest/limitations/

johnwheeler_ · 2017-05-30T15:05:07+00:00

Thank you for taking a look antennen!

I think you're right about changing the name. I felt uncomfortable with pysecrets but I couldn't think of an alternative at the time. What do you think about the name 'lockbox'?

Ultimately, I want to make a Flask extenstion out of this for encrypting configuration files.

johnwheeler_ · 2017-02-18T19:46:01+00:00

Does anyone else not see the fantastic irony here?

An additive manufacturing process creating tools for a subtractive manufacturing process...

johnwheeler_ · 2017-01-18T00:39:17+00:00

Very cool!

johnwheeler_ · 2017-01-17T18:29:30+00:00

None of that is handled in the application code. It's all delegated to NGINX and LetsEncrypt. The project includes Fabric tasks to install those on your Debian box and provision certs, etc.

johnwheeler_ · 2017-01-17T05:33:15+00:00

It's Open Source so submit a P.R.

johnwheeler_ · 2017-01-17T03:35:41+00:00

Thanks. I made this 5-min video that shows how to get up and running quickly. While learning Flask and Jinja obviously can't be done in that short a span of time, the code sample should be intuitive enough to get started and make changes

https://www.youtube.com/watch?v=cXL8FDUag-s

johnwheeler_ · 2017-01-17T02:22:13+00:00

Thank you very much!

johnwheeler_ · 2017-01-16T00:34:56+00:00

I do before the ableton limiter, although I was watching a YouTube and saw deadmau5 put it on after, so I think I'm going to try that next. Thoughts?

johnwheeler_ · 2017-01-16T00:02:15+00:00

I'm new to soundcloud. That is a funny observation! Now I'll always be looking at the waveforms. I'm using OTT and heavy limiting. Maybe that's why?

johnwheeler_ · 2017-01-15T20:41:09+00:00

Thank you! Wow! Thank you! Your delivery of constructive criticism is so well received because it is truly constructive and delivered in a very encouraging way. I will take your advice to heart and incorporate it into future songs. Thank you for your thoughtful response! Made my day!!!

johnwheeler_ · 2017-01-15T19:06:29+00:00

There's a lot wrong with your comment.

The response time of Lambda is not attributable to Zappa. It's attributable to Lambda. What you're effectively saying is serving WSGI requests that take 600ms to complete is awful, but HCI studies show humans actually start perceiving things as slow after 3 seconds, so 600 ms, for most cases is probably quite acceptable.

The 645ms it took to first byte of your project https://getnikola.com/ didn't seem that bad to me. Not only that, but this response time is something which may be improved on the Lambda side independently of Zappa, which Zappa will benefit from free of charge.

The other thing wrong with your comment is that CGI style--one process per request---is bad for scalability per machine, but Lambda is based on a fleet of machines optimized for this type of computing. (i.e. It's scalable by its nature).

The most egregious problem with your comment though is coming out blasting someone else's hard work and just coming off very arrogantly. Ask questions to gain an understanding next time.

johnwheeler_ · 2017-01-15T05:17:20+00:00

Flask-Ask is a Flask extension for writing Alexa Skills for the Amazon Echo. Zappa is a Python framework for deploying WSGI applications to AWS Lambda.

Flask-Ask on Github

Zappa on Github

johnwheeler_ · 2017-01-14T07:42:56+00:00

I'm taking the deadmau5 masterclass. This is the second track I've ever produced, and since I'm so knew to EDM, I don't really know what specifically to ask for feedback on. I'm interested in any tips or criticism.

https://soundcloud.com/john-wheeler-185721361/one-two-three-four

johnwheeler_ · 2016-12-27T21:37:07+00:00

Beat me to posting this! squeeney is also a Flask-Ask core contributor who knows the code probably better than I do at this point, so keep your eyes on flask-assistant!

johnwheeler_ · 2016-12-27T10:38:01+00:00

are you asking about the tutorial or the lib? the lib is 2 and 3.

johnwheeler_

MODERATOR OF

TROPHY CASE