All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: The development of GNU GRUB <grub-devel@gnu.org>,
	Steve McIntyre <steve@einval.com>
Cc: Daniel Axtens <dja@axtens.net>
Subject: Re: [PATCH] Remove HFS support
Date: Fri, 19 Aug 2022 20:38:30 +0200	[thread overview]
Message-ID: <a601f459-311a-28ba-95cb-3473ca4a6312@physik.fu-berlin.de> (raw)
In-Reply-To: <20220819180916.GG2668594@tack.einval.com>

On 8/19/22 20:09, Steve McIntyre wrote:
> On Fri, Aug 19, 2022 at 04:03:38PM +0200, John Paul Adrian Glaubitz wrote:
>>> On Aug 19, 2022, at 3:59 PM, Daniel Kiper <dkiper@net-space.pl> wrote:
>>>
>>> If I do not hear any major objections in the following weeks I will
>>> merge this patch or a variant of it in the second half of September.
>>
>> We’re still formatting our /boot partitions for Debian PowerPC for
>> PowerMacs using HFS, so this change would be a breaking change for
>> us.
>>
>> So, that would be a no from Debian’s side.
> 
> Not so fast please, Adrian. At the risk of sounding harsh, non-release
> old ports like powerpc *really* don't get to dictate things in Debian
> terms.

Add "Ports" to this.

> As Daniel Axtens has been finding out, the HFS code is terrible in
> terms of security. If you still need it for old/semi-dead machines,
> maybe you should fork an older grub release and stay with that?

I don't know what should be the deal with the security of a boot loader
to be honest. If someone has access to your hardware so they can control
your bootloader, you have much worse problems anyway.

Forking is also a terrible idea as every forked package means having to
track it manually.

Adrian

-- 
  .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



  reply	other threads:[~2022-08-19 18:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 13:38 [PATCH] Remove HFS support Daniel Axtens
2022-08-19 13:57 ` Daniel Kiper
2022-08-19 14:03   ` John Paul Adrian Glaubitz
2022-08-19 17:57     ` Vladimir 'phcoder' Serbinenko
2022-08-20 14:23       ` Daniel Axtens
2022-08-19 18:09     ` Steve McIntyre
2022-08-19 18:38       ` John Paul Adrian Glaubitz [this message]
2022-08-19 19:04         ` Dimitri John Ledkov
2022-08-19 19:45           ` Vladimir 'phcoder' Serbinenko
2022-08-20 14:05             ` Daniel Axtens
2022-08-24  7:17             ` John Paul Adrian Glaubitz
2022-08-24  7:16           ` John Paul Adrian Glaubitz
2022-08-20 14:13         ` Daniel Axtens
2022-08-19 19:01       ` Vladimir 'phcoder' Serbinenko
2022-08-26 15:46         ` John Paul Adrian Glaubitz
2022-08-26 17:02           ` Vladimir 'phcoder' Serbinenko
2022-08-20 13:53     ` Daniel Axtens
2022-08-24  7:21       ` John Paul Adrian Glaubitz
2022-08-26 13:31         ` Daniel Axtens
2022-08-26 15:17           ` Vladimir 'phcoder' Serbinenko
2022-08-30 18:28             ` Robbie Harwood
2022-09-01 14:01             ` Daniel Axtens
2022-08-26 15:27           ` John Paul Adrian Glaubitz
2022-08-30 16:37           ` Robbie Harwood
2022-08-30 17:21             ` John Paul Adrian Glaubitz
2022-08-30 18:43               ` Robbie Harwood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a601f459-311a-28ba-95cb-3473ca4a6312@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=dja@axtens.net \
    --cc=grub-devel@gnu.org \
    --cc=steve@einval.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.