Comment 4 for bug 1973321
Revision history for this message
| Andrew Conway (acubuntuone) wrote Re: snaps dont't start when current working directory is on sshfs | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
The setup where root cannot access is the default for NFS (unless you want to run it with no authentication at all).
I have not seen or heard any options for making root able to access Kerberos/nfs. They may exist, but it is not an easy thing to do - the root user has to authenticate itself to the user server as a particular user. It is not obvious which user it should choose. Well, you could come up with a set of heuristics that would often but not always work, and then see if that user has any credentials lying around, and grab them. Alternatively you could make a root user in kerberos (the reason for sudo's existance is because this is a bad idea), and make a file containing the root password in plaintext in a standard place that Kerberos could access if it wants to do something as root, but this seems like a very bad idea.
P.S. It turns out that the workaround of using the debian firefox packages doesn't work reliably - ubuntu 22.04 keeps regularly reinstalling firefox as a snap even if you explicitly give the debian package higher priority.