From: Felix Lechner via <help-guix@gnu.org>
To: William <willbilly@fedora.email>
Cc: help-guix@gnu.org, Abdelhakim Qbaich <abdelhakim@qbaich.com>
Subject: Re: Configuring mount for NTFS partition at boot makes the system unbootable.
Date: Sun, 03 Mar 2024 16:15:56 -0800 [thread overview]
Message-ID: <87ttlmzwar.fsf@lease-up.com> (raw)
In-Reply-To: <20240303233648.55a40747@fedora.email>
Hi William,
It seems that help-guix was inadvertently left off of the recipients. I
hope you don't mind that I copied the mailing list on your response.
On Sun, Mar 03 2024, William wrote:
> Hello.
>
> Thanks for the input, this certainly helped me diagnose the issue.
>
> I set some options so Guix keeps booting if mounting the filesystem
> fails, now I can boot.
>
> I potentially figured out what the issue may be, the filesystem entry is
> defined on /etc/fstab so I tried running "mount -a" without root, and it
> printed this:
>
>> Mount is denied because setuid and setgid root ntfs-3g is insecure
>> with the external FUSE library. Either remove the setuid/setgid bit
>> from the binary or rebuild NTFS-3G with integrated FUSE support and
>> make it setuid root.
>> Please see more information at
>> https://github.com/tuxera/ntfs-3g/wiki/NTFS-3G-FAQ
>
> It seems it's another issue with setuid/setgid. I think this could be
> solved if ntfs-3g is compiled with integrated FUSE support, so
> it doesn't require libfuse at all, then the declaration to load the FUSE
> module wouldn't be needed either I suppose.
I also use FUSE every day and believe it's compiled into our kernels
(i.e. no module). Perhaps someone can help you find our kernel
configurations.
The security concern may also be further explained here. [1]
> Maybe this should be reported as an issue on the Guix tracker?
There is already a bug about it. [2] The filing is from 2021. There is
no proposed solution.
I would write to the bug [3] and ask if there are workarounds. Please
make sure to cc Abdelhakim, whose address you can find here. [4] (I also
copied him on this message.) No one else will receive or read your
message to the bug tracker.
Kind regards
Felix
P.S. Sorry about the complexity of our bug reporting tools. Some work is
being done to simplify them.
[1] https://unparalleled.eu/blog/2022/20220607-help-to-heap-suid-privilege-escalation/
[2] https://issues.guix.gnu.org/46980
[3] 46980@debbugs.gnu.org
[4] https://debbugs.gnu.org/46980
next prev parent reply other threads:[~2024-03-04 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 20:57 Configuring mount for NTFS partition at boot makes the system unbootable William
2024-03-03 21:23 ` Saku Laesvuori
2024-03-03 21:26 ` Felix Lechner via
[not found] ` <20240303233648.55a40747@fedora.email>
2024-03-04 0:15 ` Felix Lechner via [this message]
2024-03-04 19:17 ` William
2024-03-07 14:41 ` Felix Lechner via
2024-03-07 23:55 ` William
2024-03-08 2:01 ` Felix Lechner via
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=87ttlmzwar.fsf@lease-up.com \
--to=help-guix@gnu.org \
--cc=abdelhakim@qbaich.com \
--cc=felix.lechner@lease-up.com \
--cc=willbilly@fedora.email \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.