(Sorry, forgot to send earlier)
Steve Litt writes:
Something that used to
take no more than correctly configuring grub now requires execution
of the volumes of information in these links, with much of that
execution being trial and error because of different UEFI/secureboot
implementations.
Th
On Oct 21, 2017 10:05, "Dr. Nikolaus Klepp" wrote:
> Tobias, until I read your posting a couple of days ago I did not realise
> that UEFI/Secure Boot can be configured such that ONLY my kernels can be
> booted, not even fresh install media from the vendor. Thank you very much.
>
> Arnt
Well, tha
On Sat, 21 Oct 2017 16:54:36 -0400
John Franklin wrote:
> > On Oct 21, 2017, at 5:51 AM, Didier Kryn wrote:
> >> Tobias, until I read your posting a couple of days ago I did not
> >> realise that UEFI/Secure Boot can be configured such that ONLY my
> >> kernels can be booted, not even fresh ins
Le 21/10/2017 à 22:54, John Franklin a écrit :
A generic guide to Secureboot and updating Secureboot keys in your
uEFI firmware:
https://www.rodsbooks.com/efi-bootloaders/secureboot.html
https://www.rodsbooks.com/efi-bootloaders/controlling-sb.html
Ubuntu’s guide to signing things for Secureb
> On Oct 21, 2017, at 5:51 AM, Didier Kryn wrote:
>
> Le 21/10/2017 à 09:58, Arnt Gulbrandsen a écrit :
>> John Franklin writes:
>>> That’s not an apology. Would you like to try again?
>>
>> I'm not Steve, but the occasion fits:
>>
>> Tobias, until I read your posting a couple of days ago I d
On Sat, 21 Oct 2017 at 11:51:42 +0200
Didier Kryn wrote:
> Le 21/10/2017 à 09:58, Arnt Gulbrandsen a écrit :
>> John Franklin writes:
>>> That’s not an apology. Would you like to try again?
>>
>> I'm not Steve, but the occasion fits:
>>
>> Tobias, until I read your posting a couple of days a
Dr. Nikolaus Klepp writes:
Sorry to say, it's not. These keys don't allow booting your retail windows.
Uh-huh. Are we talking about black helicopter keys?
Arnt
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/list
Am Samstag, 21. Oktober 2017 schrieb Arnt Gulbrandsen:
> Dr. Nikolaus Klepp writes:
> > Well, that's not true: If you are lucky, your vendor installed
> > a bios that allows you seamingly do so. But most likely he
> > didn't. Most likely his implementation has a backdoor for
> > windows.
>
> Yo
Dr. Nikolaus Klepp writes:
Well, that's not true: If you are lucky, your vendor installed
a bios that allows you seamingly do so. But most likely he
didn't. Most likely his implementation has a backdoor for
windows.
You're saying most vendors do this? Not just some but MOST? Name one or two
Le 21/10/2017 à 09:58, Arnt Gulbrandsen a écrit :
John Franklin writes:
That’s not an apology. Would you like to try again?
I'm not Steve, but the occasion fits:
Tobias, until I read your posting a couple of days ago I did not
realise that UEFI/Secure Boot can be configured such that ONLY m
Am Samstag, 21. Oktober 2017 schrieb Arnt Gulbrandsen:
> John Franklin writes:
> > That’s not an apology. Would you like to try again?
>
> I'm not Steve, but the occasion fits:
>
> Tobias, until I read your posting a couple of days ago I did not realise
> that UEFI/Secure Boot can be configured
John Franklin writes:
That’s not an apology. Would you like to try again?
I'm not Steve, but the occasion fits:
Tobias, until I read your posting a couple of days ago I did not realise
that UEFI/Secure Boot can be configured such that ONLY my kernels can be
booted, not even fresh install me
On 2017-10-20 20:24, Steve Litt wrote:
On Wed, 18 Oct 2017 12:33:33 -0400
John Franklin wrote:
You owe him an apology.
Perhaps you're right. Here it is. Tobias, instead of railing against
this list's primary priority, why don't you go join the systemd project
and make it the init of your dre
> On Oct 20, 2017, at 9:24 PM, Steve Litt wrote:
>
>> You owe him an apology.
>
> Perhaps you're right. Here it is. Tobias, instead of railing against
> this list's primary priority, why don't you go join the systemd project
> and make it the init of your dreams. Lead, follow, or get the hell o
On Wed, 18 Oct 2017 12:33:33 -0400
John Franklin wrote:
> > On Oct 16, 2017, at 1:51 PM, Steve Litt
> > wrote:
> >
> > On Mon, 16 Oct 2017 17:18:43 +0200
> > "Dr. Nikolaus Klepp" wrote:
> >
> >> Am Samstag, 7. Oktober 2017 schrieb Tobias Hunger:
> >>> On Sat, Oct 7, 2017 at 3:46 PM, Didie
@Nikolaus: UEFI is closed source software (just as BIOS), so of course
the usual problems with closed source also apply here. I trust my
notebook vendor just enough to not fuck this up badly enough so that
random thieves will be able to get around secure boot though:-)
I am pretty sure though that
Perhaps this helps you for a more static configuration:
https://git.actiu.net/libre/mactoname/
El 06/10/17 a les 18:12, J. Fahrner ha escrit:
> Hello,
> I found the message
> "systemd-udevd[415]: renamed network interface eth0 to eth1"
> in my dmesg log.
> 1. why is there a systemd daemon?
> 2. w
> On Oct 16, 2017, at 1:51 PM, Steve Litt wrote:
>
> On Mon, 16 Oct 2017 17:18:43 +0200
> "Dr. Nikolaus Klepp" wrote:
>
>> Am Samstag, 7. Oktober 2017 schrieb Tobias Hunger:
>>> On Sat, Oct 7, 2017 at 3:46 PM, Didier Kryn wrote:
Then maybe I misunderstood the reason for EFI.
>>>
> On Oct 17, 2017, at 9:08 AM, Arnt Gulbrandsen
> wrote:
>
> Alessandro Selli writes:
>> Plus, it's purported security is mostly a mith. It only checks if the
>> first-stage bootloader was signed by a known, authorized key, everything else
>> is as exposed to malware and rootkits as it's alwa
On Tue, 17 Oct 2017 at 14:08:20 +0100
Arnt Gulbrandsen wrote:
> Alessandro Selli writes:
>> Plus, it's purported security is mostly a mith. It only checks if the
>> first-stage bootloader was signed by a known, authorized key,
>> everything else
>> is as exposed to malware and rootkits as it'
Alessandro Selli writes:
Plus, it's purported security is mostly a mith. It only checks if the
first-stage bootloader was signed by a known, authorized key,
everything else
is as exposed to malware and rootkits as it's always been. It protects from
one of the smallest attack vectors that wa
On Mon, 16 Oct 2017 at 17:35:26 +0200
"J. Fahrner" wrote:
> Am 2017-10-07 17:23, schrieb Tobias Hunger:
>
>> With UEFI the firmware just loads a efi binary with everything:-) MUCH
>> simpler.
>
> I cannot see where UEFI boot is simple. I'm always wondering why booting
> an OS on PC is rocket sc
On 2017-10-16 15:31, Dr. Nikolaus Klepp wrote:
Am Montag, 16. Oktober 2017 schrieb Steve Litt:
> > * UEFI allows for more security with secure boot. E.g. my thinkpad
> > *only* boots things that I have signed with my key.
Does Devuan have a key? If not, I guess that's all we need to know
about
On Mon, 16 Oct 2017 22:31:28 +0200
"Dr. Nikolaus Klepp" wrote:
> Am Montag, 16. Oktober 2017 schrieb Steve Litt:
> > > > * UEFI allows for more security with secure boot. E.g. my
> > > > thinkpad *only* boots things that I have signed with my key.
> >
> > Does Devuan have a key? If not, I gues
Am Montag, 16. Oktober 2017 schrieb Steve Litt:
> > > * UEFI allows for more security with secure boot. E.g. my thinkpad
> > > *only* boots things that I have signed with my key.
>
> Does Devuan have a key? If not, I guess that's all we need to know
> about what distro Tobias Hunger REALLY uses. I
On Mon, 16 Oct 2017 17:18:43 +0200
"Dr. Nikolaus Klepp" wrote:
> Am Samstag, 7. Oktober 2017 schrieb Tobias Hunger:
> > On Sat, Oct 7, 2017 at 3:46 PM, Didier Kryn wrote:
> > > Then maybe I misunderstood the reason for EFI.
> >
> > UEFI is a huge step forward in pretty much all areas an
> On Oct 16, 2017, at 11:18 AM, Dr. Nikolaus Klepp wrote:
>
> Am Samstag, 7. Oktober 2017 schrieb Tobias Hunger:
>> On Sat, Oct 7, 2017 at 3:46 PM, Didier Kryn wrote:
>>>Then maybe I misunderstood the reason for EFI.
>>
>> UEFI is a huge step forward in pretty much all areas and makes boot
Am 2017-10-07 17:23, schrieb Tobias Hunger:
With UEFI the firmware just loads a efi binary with everything:-) MUCH
simpler.
I cannot see where UEFI boot is simple. I'm always wondering why booting
an OS on PC is rocket science (try googling "grub boot problems").
Ever had an Apple Computer? C
Am Samstag, 7. Oktober 2017 schrieb Tobias Hunger:
> On Sat, Oct 7, 2017 at 3:46 PM, Didier Kryn wrote:
> > Then maybe I misunderstood the reason for EFI.
>
> UEFI is a huge step forward in pretty much all areas and makes booting
> both simpler and more powerful.
>
> Grub on BIOS basically w
On Sat, Oct 7, 2017 at 3:46 PM, Didier Kryn wrote:
> Then maybe I misunderstood the reason for EFI.
UEFI is a huge step forward in pretty much all areas and makes booting
both simpler and more powerful.
Grub on BIOS basically works like this: the one MBR is read by BIOS
and executed (512 byt
Can you rename the files, instead, by adding _removed_by_rc.local.
Sent from my MetroPCS 4G LTE Android Device
Original message From: Didier Kryn Date:
10/11/17 2:03 AM (GMT-06:00) To: dng@lists.dyne.org Subject: Re: [DNG]
systemd-udevd: renamed network interface eth0 to
On Wed, 11 Oct 2017 09:08:15 +0200, Alessandro wrote in message
<20171011090815.3265eeae@ayu.localdomain>:
> Il giorno Tue, 10 Oct 2017 22:25:23 -0500
> John Morris ha scritto:
>
> > On Tue, 2017-10-10 at 01:49 +0200, Alessandro Selli wrote:
> >
> >> By the manual, the correct solution in c
Le 11/10/2017 à 09:32, Dr. Nikolaus Klepp a écrit :
Am Mittwoch, 11. Oktober 2017 schrieb Didier Kryn:
Le 11/10/2017 à 08:10, Dr. Nikolaus Klepp a écrit :
Am Mittwoch, 11. Oktober 2017 schrieb John Morris:
On Tue, 2017-10-10 at 01:49 +0200, Alessandro Selli wrote:
By the manual, the corr
Am Mittwoch, 11. Oktober 2017 schrieb Didier Kryn:
> Le 11/10/2017 à 08:10, Dr. Nikolaus Klepp a écrit :
> > Am Mittwoch, 11. Oktober 2017 schrieb John Morris:
> >> On Tue, 2017-10-10 at 01:49 +0200, Alessandro Selli wrote:
> >>
> >>>By the manual, the correct solution in configuring Grub as to
Il giorno Tue, 10 Oct 2017 22:25:23 -0500
John Morris ha scritto:
> On Tue, 2017-10-10 at 01:49 +0200, Alessandro Selli wrote:
>
>> By the manual, the correct solution in configuring Grub as to pass the
>> kernel these parameters:
>>
>> biosdevname=0 net.ifnames=0
>
> Those fix similar problem
Le 11/10/2017 à 08:10, Dr. Nikolaus Klepp a écrit :
Am Mittwoch, 11. Oktober 2017 schrieb John Morris:
On Tue, 2017-10-10 at 01:49 +0200, Alessandro Selli wrote:
By the manual, the correct solution in configuring Grub as to pass the
kernel these parameters:
biosdevname=0 net.ifnames=0
Tho
Am Mittwoch, 11. Oktober 2017 schrieb John Morris:
> On Tue, 2017-10-10 at 01:49 +0200, Alessandro Selli wrote:
>
> > By the manual, the correct solution in configuring Grub as to pass the
> > kernel these parameters:
> >
> > biosdevname=0 net.ifnames=0
>
> Those fix similar problems but not e
On Tue, 2017-10-10 at 01:49 +0200, Alessandro Selli wrote:
> By the manual, the correct solution in configuring Grub as to pass the
> kernel these parameters:
>
> biosdevname=0 net.ifnames=0
Those fix similar problems but not exactly the same ones. The udev
persistent rules get you when you m
On Mon, 09 Oct 2017 at 14:45:47 -0500
John Morris wrote:
> On Sat, 2017-10-07 at 10:06 -0300, Renaud (Ron) OLGIATI wrote:
>> On Sat, 7 Oct 2017 13:51:02 +0100
>> Simon Hobson wrote:
>>
>>> The topic was discussed to death not long ago and the consensus seemed
>>> to be that "there is no soluti
Am 2017-10-09 21:45, schrieb John Morris:
There is. Make /etc/udev/rules.d/70-persistent-net.rules a symlink
to /dev/null and it will leave you alone.
Great idea!
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman
On Sat, 2017-10-07 at 10:06 -0300, Renaud (Ron) OLGIATI wrote:
> On Sat, 7 Oct 2017 13:51:02 +0100
> Simon Hobson wrote:
>
> > The topic was discussed to death not long ago and the consensus seemed to
> > be that "there is no solution that works for everyone" ! As Jochen says,
> > for "simple"
On Sat, 7 Oct 2017 13:51:02 +0100
Simon Hobson wrote:
> The topic was discussed to death not long ago and the consensus seemed to be
> that "there is no solution that works for everyone" ! As Jochen says, for
> "simple" machines with no more than one ethernet and one wifi, nothing needs
> to b
Le 07/10/2017 à 12:29, J. Fahrner a écrit :
Am 2017-10-07 11:43, schrieb Didier Kryn:
EFI responds to a need for security, because, without it, it is so
easy, in a few minutes, with a simple USB memory stick to steal and/or
fuck-up the contents of any PC. It's a bad response because, IIUC, i
Am 2017-10-07 14:51, schrieb Simon Hobson:
For everything else then there is a
problem that needs solving.
As I said before, this can be solved manually by adding a udev rule.
There is no need to do that "automagically".
Jochen
___
Dng mailing lis
Didier Kryn wrote:
>This has nothing to do with Linux becoming Windows-like, nor Systemd. Udev
> started doing that a dozen years ago, at least, and Windows desktop or
> laptops do not need that feature more than Linux's. This feature is
> essentially dedicated to servers with multiple net
Am 2017-10-07 11:43, schrieb Didier Kryn:
EFI responds to a need for security, because, without it, it is so
easy, in a few minutes, with a simple USB memory stick to steal and/or
fuck-up the contents of any PC. It's a bad response because, IIUC, it
is enough to have an EFI-compatible boot-lo
Le 07/10/2017 à 10:39, J. Fahrner a écrit :
Am 2017-10-07 09:43, schrieb Florian Zieboll:
From another point of view one could argue, that your device had
already been unstable... why else would you have had to repair it?
In this case, the modification of your "persistent-net-rules" file
could
Am 2017-10-07 09:43, schrieb Florian Zieboll:
From another point of view one could argue, that your device had
already been unstable... why else would you have had to repair it?
In this case, the modification of your "persistent-net-rules" file
could be seen as (the most easy) part of a successf
Am 6. Oktober 2017 18:52:10 MESZ schrieb "J. Fahrner" :
> The new logic makes them unstable when you have to change devices on repair.
From another point of view one could argue, that your device had already been
unstable... why else would you have had to repair it?
In this case, the modificat
J. Fahrner [2017-10-06 18:52]:
> That's a perfect example why renaming devices (to make them "stable") is
> not a good idea. Most consumer devices have not more than one ethernet
> card and one wireless card. So naming was already "stable". The new
> logic makes them unstable when you have to c
Le 06/10/2017 à 18:52, J. Fahrner a écrit :
Hi Didier,
Am 2017-10-06 18:36, schrieb Didier Kryn:
If you aren't satisfied witht the current numbering of your
interfaces, there is a simple way to change the numbering:
find the file /etc/udev/rules.d/70-persistent-net-rules. You will
see t
Hi Didier,
Am 2017-10-06 18:36, schrieb Didier Kryn:
If you aren't satisfied witht the current numbering of your
interfaces, there is a simple way to change the numbering:
find the file /etc/udev/rules.d/70-persistent-net-rules. You will
see there is a line per known interface, containin
Le 06/10/2017 à 18:12, J. Fahrner a écrit :
Hello,
I found the message
"systemd-udevd[415]: renamed network interface eth0 to eth1"
in my dmesg log.
1. why is there a systemd daemon?
2. why is my ethernet device renamed?
I would like it as eth0 and wlan0, not eth1 and wlan1.
Jochen
If yo
Hello,
I found the message
"systemd-udevd[415]: renamed network interface eth0 to eth1"
in my dmesg log.
1. why is there a systemd daemon?
2. why is my ethernet device renamed?
I would like it as eth0 and wlan0, not eth1 and wlan1.
Jochen
___
Dng mai
54 matches
Mail list logo
