[RFC] permissions mgmt

[Robert Collins]

I think the bunch of interactions between permissions and performance
are a hint :).. and our inability to do the right thing on sftp [at all]
hints this too...

I'd like to propose the following changes to our permission support
logic:

 - over sftp we dont chmod at all - we do whatever the umask is
configured to do by the user. We should offer a helper script to set the
umask before invoking the sftp-server process.
 - over ssh we offer a umask-setting facility. We will have a native ssh
non-smart server protocol in 0.11 I think - its the substrate for the
smart-server-over-ssh.
 - on local disk we offer a umask setting facility.

Both the umask-setting facilities are off by default, controlled by a
file in the repository.

The idea is that by default we can just create files with the right mode
that we need - read or read-write, and forget about the detail. And when
permission mgmt is needed, we do it via umask setting rather than
explicit chmodding.

Thoughts ?

-Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060821/474b10a7/attachment.pgp