Re: fix for no ssh

From	Curt <curty@free.fr>
Newsgroups	linux.debian.user
Subject	Re: fix for no ssh
Date	2019-07-08 16:50 +0200
Message-ID	<yhD7P-7Nb-5@gated-at.bofh.it> (permalink)
References	(2 earlier) <yhiwq-3HJ-7@gated-at.bofh.it> <yhjsu-4gT-3@gated-at.bofh.it> <yhvN0-3jt-11@gated-at.bofh.it> <yhxOO-4Kp-7@gated-at.bofh.it> <yhyUx-5nD-1@gated-at.bofh.it>
Organization	Unorganized

Show all headers | View raw

On 2019-07-08, Andrei POPESCU <andreimpopescu@gmail.com> wrote:
>
> The timing was also not very good for the buster release cycle.
> Hopefully this will be sorted out properly in time for bullseye.

Earlier I thought bullseye was some sort of idiom for Buster going live.
Color me ignorant. 

But concerning the currently proposed workaround for x86 CPU's (from
which I cannot "benefit," apparently), it's edifying to note what Ted
himself said about his own patch:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=39a8883a2b989d1d21bd8dd99f5557f0c5e89694

 random: add a config option to trust the CPU's hwrng

 This gives the user building their own kernel (or a Linux distribution)
 the option of deciding whether or not to trust the CPU's hardware
 random number generator (e.g., RDRAND for x86 CPU's) as being correctly
 implemented and not having a back door introduced (perhaps courtesy of
 a Nation State's law enforcement or intelligence agencies).

 This will prevent getrandom(2) from blocking, if there is a
 willingness to trust the CPU manufacturer.

 Signed-off-by: Theodore Ts'o <tytso@mit.edu>

So Debian Buster, as it now stands and I understand it, trusts in the
correctness of the hardware random number generator, as well as in the
absence of any back door that might compromise it, universally and
without qualification, of every Debian Buster user's x86 cpu (default
kernel command line CONFIG_RANDOM_TRUST_CPU), in the name of security.

That's a safer solution than installing haveged? 

I know, I know, I can use any kernel command line I want. I could switch
to another distribution without these problems. I could go fuck myself.
But as an innate altruist (just kidding), I'm wondering whether the
regular user is aware of the implications of all this. What about people
in Nation States ...  Well, you get the idea.

> Kind regards,
> Andrei

-- 
"These findings demonstrate that under appropriate conditions the isolated,
intact large mammalian brain possesses an underappreciated capacity for
restoration of microcirculation and molecular and cellular activity after a
prolonged post-mortem interval." From a recent article in *Nature*. Holy shit.

Thread

fix for no ssh Gene Heskett <gheskett@shentel.net> - 2019-07-07 16:30 +0200
  Re: fix for no ssh Tixy <tixy@yxit.co.uk> - 2019-07-07 16:50 +0200
    Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-07 18:50 +0200
      Re: fix for no ssh Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-07-07 19:50 +0200
        Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 09:00 +0200
          Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 11:10 +0200
            Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 12:20 +0200
              Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 13:00 +0200
              Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 16:50 +0200
                Re: fix for no ssh Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-08 17:40 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 18:20 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-08 18:50 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-09 10:20 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-10 10:20 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-10 11:30 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-10 13:50 +0200
                Re: fix for no ssh Reco <recoverym4n@enotuniq.net> - 2019-07-10 14:30 +0200
                Re: fix for no ssh Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-10 15:10 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-10 16:10 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-11 14:10 +0200
                Re: fix for no ssh Reco <recoverym4n@enotuniq.net> - 2019-07-11 16:20 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-11 17:10 +0200
                Re: fix for no ssh Reco <recoverym4n@enotuniq.net> - 2019-07-11 17:20 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-10 16:00 +0200
                Re: fix for no ssh David Wright <deblis@lionunicorn.co.uk> - 2019-07-10 21:20 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-10 21:30 +0200
                [OT] Trustfulness. Was: Re: fix for no ssh "Thomas Schmitt" <scdbackup@gmx.net> - 2019-07-08 18:00 +0200
                Re: [OT] Trustfulness. Was: Re: fix for no ssh Reco <recoverym4n@enotuniq.net> - 2019-07-08 18:10 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-08 18:10 +0200
          Re: fix for no ssh Henrique de Moraes Holschuh <hmh@debian.org> - 2019-07-09 01:30 +0200
      Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 10:50 +0200
        Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 11:00 +0200
          Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 11:20 +0200
            Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 11:30 +0200
              Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 11:50 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 12:00 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 12:30 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 18:30 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-08 19:50 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-08 20:20 +0200
                Re: fix for no ssh Gene Heskett <gheskett@shentel.net> - 2019-07-08 21:00 +0200
                Re: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-08 22:50 +0200
                Fwd: fix for no ssh Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-07-08 23:50 +0200
                Re: Fwd: fix for no ssh Andy Smith <andy@strugglers.net> - 2019-07-09 00:40 +0200
                Re: fix for no ssh John Hasler <jhasler@newsguy.com> - 2019-07-09 01:20 +0200
                Re: fix for no ssh Nicholas Geovanis <nickgeovanis@gmail.com> - 2019-07-09 01:30 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-09 09:50 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 23:00 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-08 23:00 +0200
                Re: fix for no ssh Curt <curty@free.fr> - 2019-07-10 09:50 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-10 21:40 +0200
                Re: fix for no ssh David Wright <deblis@lionunicorn.co.uk> - 2019-07-09 01:30 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-09 10:00 +0200
                Re: fix for no ssh David Wright <deblis@lionunicorn.co.uk> - 2019-07-10 01:20 +0200
                Re: fix for no ssh Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-10 05:40 +0200
    Re: fix for no ssh Gene Heskett <gheskett@shentel.net> - 2019-07-07 22:50 +0200

csiph-web