Re: [Dav-linuxfs] DAVFS2/pam_mount interaction resolution

[Werner B. <wer...@on...>]

Jan Engelhardt wrote:
> The username option is actually all that is needed, because the
> password code, by means of getpass(), already trims \n.

Does that mean getpass() does not block, but gets the password from 
mount/pam_mount?
In this case there would be no need to change this soon. As pam_mount 
does not send the username over stdin, the missing newline will not be a 
problem for username. So this changes may be delayed.

So the only point would be:
Are your users willing to put the username in the davfs2 secrets file, 
as expected by davfs2?
Please show me the scenario where this is really a problem. It should be 
realistic and it should not be a WebDAV-servers that replaces NFS.

As mentioned, there is a reason, why there is no '-o username='. Why 
should I change the userinterface of davfs2, including the 
documentation, only because somebody is too lazy to edit three lines in 
/etc/davfs2/secrets?

Cheers
Werner

P.S.: Typical use cases for davfs2 are described in README. To use a 
WebDAV resource all that is needed:
- root makes an entry in fstab
- the user edits her personal secrets file
- some broken servers may need editing of davfs2.conf

The resource can be mounted either by some clicking in 
Gnome/Nautilus/KDE/..., or by just typing 'mount <mountpint>.