unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Simon Streit <lists@netpanic.org>
To: Leo Famulari <leo@famulari.name>
Cc: help-guix@gnu.org
Subject: Re: mount.davfs: program is not setuid root
Date: Tue, 11 May 2021 22:59:44 +0200	[thread overview]
Message-ID: <ygua6p1nfzz.fsf@netpanic.org> (raw)
In-Reply-To: <YJrcOLRhhQRcQ9xO@jasmine.lan> (Leo Famulari's message of "Tue, 11 May 2021 15:34:16 -0400")

Leo Famulari <leo@famulari.name> writes:

> On Tue, May 11, 2021 at 09:30:56PM +0200, Simon Streit wrote:
>> Leo Famulari <leo@famulari.name> writes:
>> 
>> > On Tue, May 11, 2021 at 07:42:40PM +0200, Simon Streit wrote:
>> >> Thanks for posting the diff.  I did manage to build the package locally,
>> >> but that in itself isn't of much use.  I'm afraid I have to ask now, how
>> >> to I apply this package into my declaration so that it is available from
>> >> my system to test?
>> >
>> > If I understand your use case correctly, you can use the built
>> > mount.davfs program directly from /gnu/store, like this:
>> >
>> > $(guix build -f davfs2)/sbin/mount.davfs [...]
>> 
>> hm.. alright, then I did test that already.  It fails saying:
>> --8<---------------cut here---------------start------------->8---
>> ./sbin/mount.davfs: program is not setuid root
>> --8<---------------cut here---------------end--------------->8---
>> and nothing else. :/
>
> Sorry, I don't remember the earlier discussion or what you are trying to
> accomplish. But it's expected that nothing in /gnu/store is setuid.
> You'd have to use sudo or become root.

The problem is, that davfs2 mount points can't be mounted as user,
despite the binary being setuid.  To make that work I added a line in my
declaration.  But it doesn't work as expected.  Hence Efraim's patch,
that should test if this would make a difference.

Mounting with as root has been working all the time and no errors are
returned.

So the next step would be to have this patched package put into my
system declaration to test and see if setuid has been set now.  My
knowledge is to limited to go this far yet.  Will just leave it as where
it is for now.  I don't need to access this mount point very often.


Cheers,
Simon


  reply	other threads:[~2021-05-11 21:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 13:31 mount.davfs: program is not setuid root Simon Streit
2021-04-16 16:34 ` Leo Famulari
2021-04-18 13:36   ` Simon Streit
2021-04-18 13:36   ` Simon Streit
2021-04-18 23:01     ` Leo Famulari
2021-04-19 10:50       ` Simon Streit
2021-04-19 17:18         ` Leo Famulari
2021-04-21 21:46           ` Simon Streit
2021-04-19 20:30       ` Simon Streit
2021-04-20  0:47         ` Leo Famulari
2021-04-20  6:57           ` Efraim Flashner
2021-04-20  7:20           ` Efraim Flashner
2021-04-21 21:43             ` Simon Streit
2021-05-11 17:42             ` Simon Streit
2021-05-11 18:41               ` Leo Famulari
2021-05-11 19:30                 ` Simon Streit
2021-05-11 19:34                   ` Leo Famulari
2021-05-11 20:59                     ` Simon Streit [this message]
2021-05-13 13:25             ` Simon Streit
2021-04-18 20:07   ` Simon Streit

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=ygua6p1nfzz.fsf@netpanic.org \
    --to=lists@netpanic.org \
    --cc=help-guix@gnu.org \
    --cc=leo@famulari.name \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).