Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #211013
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: fix for no ssh |
| Date | 2019-07-08 18:30 +0200 |
| Message-ID | <yhEGD-nw-19@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <yhxYu-4Ox-23@gated-at.bofh.it> <yhy89-4RP-7@gated-at.bofh.it> <yhyrv-4Yr-3@gated-at.bofh.it> <yhyBc-51M-3@gated-at.bofh.it> <yhz4d-5qG-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Lu, 08 iul 19, 10:19:35, Curt wrote: > > I thought you were saying that > '/etc/udev/rules.d/70-persistent-net.rules' remains a valid mechanism > for defining interface names in Buster (fixed). But the release-notes > (hmm, I think they've been modified since I last looked and now state > that that file is no longer "officially" supported by udev---but may > work in some cases). So I wouldn't be filing a bug report against that > stanza any longer, as current situation seems unverifiable. For the record, the current wording (no official support) is based on input from the Debian systemd maintainers. They should know what is supported or not ;) As far as I know the /etc/udev/rules.d/70-persistent-net.rules method can fail to properly rename the interfaces in certain situations which can leave your system without networking. Not nice on remote machines. It is also my understanding that systems with only one interface (of a given type[1]) are pretty safe with it or net.ifnames=0, so the impact on regular[2] desktop/laptop users should be minimal. [1] assuming ethernet cards are always named ethX and wireless cards are always named wlanX by the kernel. I might have had a wireless card that came up as ethX, but that was a long time ago. Still, something to be aware of. [2] one ethernet interface, usually integrated in the motherboard and one (additional) wireless interface for the laptops. Anything more complicated than that might break without warning. > Well, at the very least people should be informed who is likely to be > affected by the bug In my understanding a lot of daemons are affected. Would it make sense to (try to) list them all? > and for those using amd64 how to check for the RDRAND > instruction, I agree that checking for the RDRAND instruction would indeed be a good addition. Someone (tm) needs to do the research and come up with a patch. As I currently don't own any amd64 systems I can only offer to support with the wording, process of submitting the patch, etc. > as well as what to do about it if they don't have it (that's what I'd > like to know, at any rate). haveged is mentioned in the Release Notes. jitterentropy-rngd was mentioned here on list as a newer alternative to haveged. Using an external hardware random generator is another option I know of, possibly the most secure, if you trust the implementation. I considered all of them. Ultimately I settled on none, because I only get about 5 seconds delay on my PINE A64+ (arm64): amp@pine64:~$ sudo dmesg | grep 'random.*done' [ 6.785377] random: fast init done [ 11.632783] random: crng init done Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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