No need for this; ~/.subversion/auth/ is already chmod 700.
Thanks, though. :-)
Kenneth Vestergaard Schmidt <kvs@binarysolutions.dk> writes:
> Hello.
>
> According to the HACKING-document, sensitive files should only have user
> read/write permissions, but it seems they are created with whatever the OS
> defaults to.
>
> I'm kind of new at this, so if I'm talking crazy, please ignore me.
>
> Index: subversion/libsvn_subr/config_auth.c
> ===================================================================
> --- subversion/libsvn_subr/config_auth.c (revision 5850)
> +++ subversion/libsvn_subr/config_auth.c (working copy)
> @@ -112,7 +112,7 @@
> SVN_ERR_W (svn_io_file_open (&authfile, auth_path,
> (APR_WRITE | APR_CREATE | APR_TRUNCATE
> | APR_BUFFERED),
> - APR_OS_DEFAULT, pool),
> + APR_UREAD | APR_UWRITE, pool),
> "unable to open auth file for writing");
>
> status = svn_hash_write (hash, authfile, pool);
>
> --
> Kenneth Vestergaard Schmidt
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 8 22:47:46 2003