[ On Friday, June 20, 2003 at 09:02:42 (+0200), address@hidden wrote: ] The important difference is between :pserver: and :ext:, especialy when you set "CVS_RSH=ssh" in your environment with the latt
still problems with cvs login this is the error I get: <server>:/homedir/<user>> cvs login (Logging in to <user>@<server>) CVS password: cvs login: authorization failed: server <server> rejected acce
My concerns were merely that I had heard noises about using CVS on disk shares and was worried (in some part) about corruption, though I could not foresee it. All the clustered machines will be on a
what is your concern? The only one that I can see would be large files with frequent changes over a slow network. But even that wouldnt seem like much of an issue. Tom <address@hidden> | To: <address
Indeed, unfortunately I'm the new guy, and it's a small setup, and they've just been throwing stuff together for the past 30 years or so, simply to get it to work in the easiest way possible with the
Hi all ! I have a little problem with security. Is there any way to avoid changing group when i commit a file ? I'm using pserver and i have a file with this permissions in the repository directory:
I've been having a horrible time accessing this list - this is try #4. Forgive it if it is a dup;I'd also like some help from the cvs group owner to figure out what the #$$% is going on. I shouldn't
I'm setting up a cvs repository on a Linux machine for multiple developers and have been reading through a lot of the documentation about how to set up security for the repository. The best behavior
cvs can fall back to use system authentication. When authenticating a password, the server first checks for the user in the $CVSROOT/CVSROOT/passwd file. If it finds the user, it will use that entry
Ops, I stand corrected, I was replying and not thinking. I thought he was trying to connect to a pserver not ssh, sorry. Mark is right, I am wrong. Ron
If you do not have pserver running, then checking to see if it will respond seems rather pointless. If you use the -t switch cvs -t -d :ext:address@hidden:/path/to/repository checkout foo you will se
With ssh, you are using strong authentication and there is no possibility that someone else will be able to utilize any possible security holes in cvs to spoof being someone else on your server machi
I have updated the access control list patch to add some new features. An upgrade is not required, this release fixes minor annoyances and adds new features. A special thanks goes to the users who he
Hello, How do I get rid of these messages? Do I have to modify the source code or is there an option that can be used when compiling that I haven't found yet? (PS: I know that a pserver is not a very
Today I wanted to figure out how to set up read-only anonymous access to CVS. When I think "anonymous CVS", I think "pserver", so looked that up in the Cederqvist and Karl Fogel's cvsbook. Seems easy
After receiving the fairly recent security notices about the double-free bug in pserver, I upgraded all our linux hosts to the current CVS version (1.11.5). As a result, anonymous check-out via pserv
A CVSROOT is defaulted if you're in a tree which you have checked out - the info comes from CVS/Root. If you're outside of any CVS tracked directory you need to specify the root with -d and/or CVSROO
You still need a CVSROOT environment variable or -d option, even though you logged in. Logging in just means that a weak security token is deposited into a file in your home directory, which allows y