I'm a senior software engineer with thirteen years of experience - mainly in Python development. I started off working at small agency, a couple startups, a biotech company, and most recently an enterprise insurance leads sales company.
I really enjoy working with Python, and try to focus my career and communities around Python. I've worked with and would work with again both Go and Ruby. For Ruby I've done Rails and Sinatra, and Go I've built a CLI tool and and APIs. While primarily backend focused, I have progressively expanded my front-end skills over time, transitioning from jQuery to VueJS. Collaborating well with fellow engineers is one of my strengths, and I find great satisfaction in mentoring and supporting others in their growth.
Location: Durham, NC
Remote: Only.
Willing to relocate: No.
Technologies: Primarily looking for Python [13y], Go[4y], Ruby on Rails [4y]
Résumé/CV: https://tyrel.dev/blog/pages/Tyrel-Souza-Resume.pdf
Email: REDACTED because of spammers like [khawlael444@gmail.com]
Https://tyrel.dev/
A decade of intermittent blogging. Nothing much of substance but I still try to maintain it. Combines Tech, Flying, Coffee, and more.
Will you be adding more customization of the "User" or is all customization per channel?
It was difficult to figure out how to set an avatar at first, I had to go under my stream page and edit there, rather than in the settings. Maybe I'm confused between the distinction between a user and a stream?
You can think of your channel as like your profile - so that is where the customization happens. It should perhaps be made clearer where you should upload your avatar, thanks for the feedback.
I've used this before and it works really well. I migrated the same wordpress install multiple times with it (once to move domain, the other to change it to https) and I didn't have a problem either time.
Of course -- YMMV, and you should definitely back up your database before.
Not much point in upgrading from 2048 bit RSA to 4096 bit RSA. Instead, you should plan to upgrade to ed25519 keys when your client and servers support them - faster and better security than RSA.
Of course that is an "if" one should carefully think about -- e.g. it is OK if all you are using is OpenSSH at version 6.5 or later. (That can be a problem with many older boxes). But other than that, last I checked only SSH.NET and tinyssh supported ed25519 keys. Shameless plug for some more data on this: http://ssh-comparison.quendi.de/comparison.html (yeah, that page could be a lot better -- pull requests are welcome)
If you have experience with RSA key pairs, using ed25519 key pairs is easy. To generate a key pair just run: ssh-keygen -t ed25519
As with RSA, this command generates a public and private key file. Put the public key in the authorized_keys file on the server side.
You'll need OpenSSH 6.4 on both the server and the client side. If you have an older version, I would not recommend upgrading outside of your operating system's normal upgrade channel because then you'll be responsible for security updates. Instead I would wait until your operating system has it.
2048 is fine for the foreseeable future; it's the same key length used for most SSL certificates (including CAs!). Your next key upgrade should probably be to another key type entirely, most likely ED25519.
I don't have a qualified answer but given he says it would take 24 minutes to crack a 256bit key and 3 days to do a 512bit, I would extrapolate (given exponentially difficulty as you add more bits) to roughly:
- 180x per doubling bit size would be
- 512 doubled twice, would mean 3 days * 180 * 180 = 97,200 days
First, 2048 bits is not 512 bits doubled twice, but rather doubled 1536 times (512 doubled twice would be 514). If this were a symmetric cipher, you could stop here and conclude that a 2048 bit key was 2^1536 times stronger than a 512 bit key.
However, RSA has diminishing returns on security as you increase the key length. The strength is determined by the complexity of the GNFS, the fastest known way of breaking RSA[1]. That tells us that breaking 256-bit RSA takes ~2^46 operations, 512-bit RSA takes ~2^63, 2048-bit RSA takes ~2^116, and 4096-bit RSA takes ~2^156. 2^116 is a lot of operations - they say the amount of energy required to break that would be nearly enough to boil all the water on earth.
