So I just found out the web portal for the school I attended stored passwords as bcrypt hashes. Nice, right?

Except the next column in the database stores the plaintext password.

And 95% percent of the passwords are just the default, 4.99% are crappy non-defaults.

@nobody facepalm

Hello! I just got lately interested in the concept of "singing my commits" on github; so I started to read online about pgp keys and such, then I remembered I needed to setup a key to connect to my web host via ssh. Long story short, I have both the private and associated public key stored on my web host. I suppose that it's not supposed to be like that? (i.e. I should only have the public key there so I can connect to it via SSH.)

@CaffeineAddiction Yeah, okay, so I should generate a new key and upload only the public one and keep the private key, well, private.

I suppose they let users upload private keys in case the sever has to interact with another service, but that would need to be a private key for that server only.

Thanks!

The office would be very interesting indeed if everyone sang their commits :D

@FireQuacker ♪♪♪ f***ing tabs ♪♪♪

♪♪♪ fixing lint errors ♪♪♪

It's a bitch to set up but once done, it's so good

@MechMK1 only reason I don't use it was it doesn't like my /mnt drives ._.

Might be going full zfs next media box build which should sort it out