[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: GLva8P-bkAAXrA5.jpg (186 KB, 1200x831)
186 KB
186 KB JPG
>I can't generate a GPG key or import an existing one to my Debian machine because of low entropy that comes with my session being through one terminal via ssh
>because I am low iq, I thought of using Gnu pass for logins in important database handling programs.

How do I encrypt my passwords serverside then? Do I just use environment variables instead defined in .bashrc? What is the best practice? What about encrypting passwords IN a database (not my personal ones that I want to use in a program)? What do?
>>
Use symmetrical rather than asymmetric encryption. Gpg -c
>>
>>102428729
It puts in the entropy



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.