tech - God bless the AMD

>>14247
sounds like a good way to keep it all secure. are you going to encrypt your backup on owncloud with something like veracrypt or?

>>14247
I've had an owncloud server for a long time, but I've always been too affraid of not having secured my soykaf enough to actually use it. I use syncthing instead, as it is p2p based and encrypted by default it feels much more secure than having on relying on my own knowledge to make sure I didn't fuarrrk up anything.

As for the password thing, I'd recommend learning a list of 26 long words by heart and "generating" a password based on the domain name of the service you're using and the importance of the service instead. That's what I do and not storing my password somewhere else than in my head feels more secure tha using Keepass. Here's what my password for lainchan would be :
If I want a strong password :
Use the first letter, then the last, then the second one , then the second last etc.
^LitteratureNicotineAnonymousAnonymousImpregnableHierarchyNicotineChocolate$
If I want an easy to type password :
Use the first three letters.
%LitteratureAnonymousImpregnable*

>>14251
im confused by
>Use the first letter, then the last, then the second one , then the second last etc.

>>14253
Using my "algorithm", lainchan becomes lnaaihnc as lainchan's first letter is l, the last one is n, the second one is a...
Once I have that, I replace every letter of the new word with the word from my list that begins with the same letter.
So l = litterature, n = nicotine, a = anonymous...
Then I add special characters (always the same, unfortunately) at the beginning and the end of the password. This way I only have to remember 26 words in order to have a hugely different password for every service that I use.

>>14249
>>14251
I was not planning to use veracrypt or anything. I thought that a good passphrase for the database would suffice.

Should I be too worried about encrypting the db file itself?

>>14254
Nice, couldn't understand 100%, but I am interested in knowing more of these kind of mnemonic stuff so I can stay minimal but secure.

lesson learned the hard way: find a way to remember your pwds in your head:
a) it's the most secure storage
b) you won't always have your personal PC lying around
c) you won't always have the time to install third party software to retrieve pwds

>>14257
yeah and things like 2FA trip me out cuz i dont want to have my phone with me at all times. are there any good (open source) hardware 2fa keychains?

>>14258
or could 2fa be run through an application run on a sd card connected to offline devices?

>>14247

Your brain, if you can't remember passwords make sure your browser/software doesn't. Entering them multiple times a day will help you remember them.

Your brain will thank you.

>>14255
>Should I be too worried about encrypting the db file itself?
You should worry about : making sure that every service running on your machine is only accepting localhost connections except for apache/nginx and SSH and making those run on non-standard ports.
Having disabled root login on SSH (make sure sudo is installed before doing that).
Having installed fail2ban.
Having a strong owncloud password.
Making sure your server's partitions are correctly encrypted.
Encrypting the DB itself to prevent anyone from stealing it from you.
And probably other things I do not know about as I am not a security expert.

This soykaf is was way too stressful to me. Using Syncthing is way easier in my opinion.

Also, the point I was trying to make with >>14254 is that you should just try to find an "algorithm" that'll help you remember strong passwords easily.

I write my own password manager using image pixel data. Its probably not more secure then anything else but I enjoyed writing it.