I think the fact that it's not possible to be perfectly safe is not a good
reason to not earnestly consider what you _can_ do to try to protect
yourself. Of course you won't stand a chance if a nation-state is
determined to get you, but that doesn't mean you should just give up and
wing it, because
Hi Jens, *,
Am 23.06.19 um 13:05 schrieb Jens John:
> On Sun, 23 Jun 2019, at 00:22, Friedrich Strohmaier wrote:
>> Anyone around who knows or did this already?
[..]
> Going by these facts, it seems like there is no way to archieve what you
> want just with journalctl.
Thats definitly not wha
You want to make the packages available for general use. Does general
use require behavioral biometric verification and spring guns?
Black hats are able to hack Google and Facebook, what ever you
will do, you never ever will be able to reach the level of security
those and the other most successfu
Some ballpark numbers, rounded to one significant figure:
10 characters chosen truly randomly from an alphabet of 70 characters (e.g.,
[a-zA-Z0-9#$&_() =+/%]) is ~61 bits of entropy and will take just about 90
years to brute-force at 1e9 guesses per second, or 30 days at 1e12/s.
The Bitcoin swarm
On 6/24/19 5:45 PM, Jude DaShiell wrote:
> The last standard the United States Navy used before it migrated to
> smartcards was 16 characters with at least two digits; at least two
> upper-case, at least two lower-case, and at least two special
> characters. A slight improvement on that would have
On 6/24/19 4:31 PM, Manuel Reimer wrote:
> On 24.06.19 18:00, mpan wrote:
>> If you’re using a password manager, you should not care about the
>> password being “too long”. After all it’s not you who type it. Go for 16
>> or 20 random chars.
>
> If the key is too complicated to remember or to t
On 24.06.19 18:00, mpan wrote:
If you’re using a password manager, you should not care about the
password being “too long”. After all it’s not you who type it. Go for 16
or 20 random chars.
If the key is too complicated to remember or to type in manually, then I
have to use a password manag
tl;dr: follow standard practices — there is nothing special about
passwords for private keys.
> I want to publish a package repository with some packages that I need
> and only want to build once for all my systems.
>
> I want to make the packages available for general use. I have server
> spac
The last standard the United States Navy used before it migrated to
smartcards was 16 characters with at least two digits; at least two
upper-case, at least two lower-case, and at least two special
characters. A slight improvement on that would have been to insure the
pass phrase started and ended
Hello,
I want to publish a package repository with some packages that I need
and only want to build once for all my systems.
I want to make the packages available for general use. I have server
space for that so I only have to rsync my final repo to my server after
compiling my packages.
I
10 matches
Mail list logo
