Re: history and val-tags locks.

2005-05-18 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Derek Price <[EMAIL PROTECTED]> writes: > Mark D. Baushke wrote: > > > For pserver, the administrator has full control over > > the command line. > > > > For server, if the administrator is using a > > restricted shell for users, they may or may not

Re: history and val-tags locks.

2005-05-18 Thread Derek Price
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark D. Baushke wrote: > For pserver, the administrator has full control over > the command line. > > For server, if the administrator is using a > restricted shell for users, they may or may not be > able to restrict command-line arguments (it > depe

Re: history and val-tags locks.

2005-05-17 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Derek Price <[EMAIL PROTECTED]> writes: > Derek Price wrote: > > >Derek Price wrote: > > > >>I see your point. What about `cvs server'? I > >>can see both setups being useful... an admin > >>who allowed users access to the CVS repository > >>would pr

Re: history and val-tags locks.

2005-05-17 Thread Derek Price
Derek Price wrote: >Derek Price wrote: > > > >>I see your point. What about `cvs server'? I can see both setups being >>useful... an admin who allowed users access to the CVS repository would >>probably prefer not to allow the config file to be specified whereas an >>admin who restriced the c

Re: history and val-tags locks.

2005-05-17 Thread Derek Price
Patch actually attached this time. Cheers, Derek Derek Price wrote: >I've implemented this as an option to server & pserver. Installing as a >global option would have create problems in multiroot mode anyhow. > >Preliminary patch against 1.11.x attached. The final version will go >into featu

Re: history and val-tags locks.

2005-05-06 Thread Derek Price
Mark D. Baushke wrote: > I believe that most modern glob() implementations may indeed internally > be implemented using fnmatch(), but not all of them are. If you are > considering using an internal glob() instead of relying on a library > version from the system, then I don't have as much of a pr

Re: history and val-tags locks.

2005-05-05 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Derek Price <[EMAIL PROTECTED]> writes: > Mark D. Baushke wrote: > > > >Note that HistoryFile has an argument that would basically be run > > >through strftime, to enable log rotation. Also see the HistorySearch, > > >which would be used as a file gl

Re: history and val-tags locks.

2005-05-05 Thread Derek Price
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark D. Baushke wrote: > >Note that HistoryFile has an argument that would basically be run > >through strftime, to enable log rotation. Also see the HistorySearch, > >which would be used as a file glob to locate history files to be read > >for execut

Re: history and val-tags locks.

2005-05-02 Thread Derek Price
Derek Price wrote: >>HistoryFile=$CVSROOT/CVSROOT/logs/history/%Y%m%d >> >> So, if the history file path were configurable and run through strftime(), I can either (1) cache the history file name the first time it is determined and gaurantee that all the operations from the same server execut

Re: history and val-tags locks.

2005-04-27 Thread Derek Price
Derek Price wrote: > I see your point. What about `cvs server'? I can see both setups being > useful... an admin who allowed users access to the CVS repository would > probably prefer not to allow the config file to be specified whereas an > admin who restriced the command that SSH users could

Re: history and val-tags locks.

2005-04-27 Thread Derek Price
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark D. Baushke wrote: > >An associated change I was putting off talking about was adding a > >global `-c ' option to cause CVS to look elsewhere for > >its configuration file. > > I worry about the security implications of this one. I don't believe i

Re: history and val-tags locks.

2005-04-27 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Derek Price <[EMAIL PROTECTED]> writes: > Mark D. Baushke wrote: > > > Derek Price <[EMAIL PROTECTED]> writes: > > I won't. My apologies for cutting and pasting the list above out of > context from an email I received. Good, sorry for sounding ala

Re: history and val-tags locks.

2005-04-27 Thread Derek Price
Mark D. Baushke wrote: > Derek Price <[EMAIL PROTECTED]> writes: > > >I'm getting ready to make two changes, possibly on stable. > > >The first would be to add file locking for the CVSROOT/history and > >CVSROOT/val-tags files. I have some reports of massively corrupted > >history files in large

Re: history and val-tags locks.

2005-04-27 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Derek Price <[EMAIL PROTECTED]> writes: > I'm getting ready to make two changes, possibly on stable. > > The first would be to add file locking for the CVSROOT/history and > CVSROOT/val-tags files. I have some reports of massively corrupted > histor