Hi all,
I am a newbie trying to setup a Version control system. I have setup
the CVSNT server on a Windows 2000 Advanced Server machine. Locally i
have been able to log into the Repository, commit the changes etc
using Torsoise CVS. Now i am trying to checkout the files from a
remote client. I am
Hello. Please help fix the error with CVS below. I'm a beginner, running the
standard GNU CVS server on a solaris machine, and running the standard GNU
CVS client on a OSX Panther Darwin console. Thanks.
-Jeff
jmyunes-pb:~ jeff$ cvs checkout bigProj
[EMAIL PROTECTED]'s password:
stty: standard
Jeff Yunes writes:
jmyunes-pb:~ jeff$ cvs checkout bigProj
[EMAIL PROTECTED]'s password:
stty: standard input: Invalid argument
You're using :ext: (or :rsh:) mode and you have an stty command in your
.profile or .cshrc (or perhaps even in the system profile) that isn't
protected against
-
From: MKlinke [mailto:[EMAIL PROTECTED]
Sent: Monday, June 14, 2004 5:06 PM
To: Fouts Christopher (IFNA RTP)
Subject: Re: Remote CVS access via SSH
On Monday 14 June 2004 15:47, [EMAIL PROTECTED] wrote:
Sorry if this does NOT belong to this group. I'm only hoping someone
has done this before
On Tue, 2004-06-15 at 10:39, [EMAIL PROTECTED] wrote:
Thanks. This worked. However, instead of entering
the password 100,000 times (every CVS command), I
now have to enter the paraphrase 100,000 times (every
CVS command.) Again as you know this is combersome.
How can I manage this so I don't
Du, why didn't I think of that. It worked!
Thanks.
-chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] On Behalf Of Tom Copeland
Sent: Tuesday, June 15, 2004 10:49 AM
To: [EMAIL PROTECTED]
Subject: RE: Remote CVS access via SSH
On Tue, 2004-06-15
On Jun 15, 2004, at 10:49 AM, Tom Copeland wrote:
On Tue, 2004-06-15 at 10:39, [EMAIL PROTECTED] wrote:
Thanks. This worked. However, instead of entering
the password 100,000 times (every CVS command), I
now have to enter the paraphrase 100,000 times (every
CVS command.) Again as you know this is
On Tue, 2004-06-15 at 10:58, [EMAIL PROTECTED] wrote:
Du, why didn't I think of that. It worked!
Thanks.
Cool, no problemo...
Tom
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/info-cvs
Ok, I'll look into this too. Thanks...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] On Behalf Of Geoff Beier
Sent: Tuesday, June 15, 2004 10:53 AM
To: Tom Copeland
Cc: [EMAIL PROTECTED]
Subject: Re: Remote CVS access via SSH
On Jun 15, 2004, at 10:49 AM, Tom
This worked too. You folks are cool! Thanks...
-chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] On Behalf Of Geoff Beier
Sent: Tuesday, June 15, 2004 10:53 AM
To: Tom Copeland
Cc: [EMAIL PROTECTED]
Subject: Re: Remote CVS access via SSH
On Jun 15, 2004
I have a cvs server v1.11.15 running on a Linux Fedora
machine, and cvs client v1.11.16 on HPUX 10.20 machine.
(Could this be the problem, ie, different versions?)
I get
echo $CVSROOT
:ext:[EMAIL PROTECTED]:/cvsroot
cvs co proj
-l: A specified flag is not valid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
I have a cvs server v1.11.15 running on a Linux Fedora
machine, and cvs client v1.11.16 on HPUX 10.20 machine.
Okay.
(Could this be the problem, ie, different versions?)
No.
I get
echo $CVSROOT
Sorry if this does NOT belong to this group. I'm only hoping
someone has done this before...
Ok, I finally got this working. Understandly so, whenever I enter
a CVS command, I'm prompted for a password so I can tunnel through.
As you folks know, this is a LOT of passwords to enter per session.
My
ssh-keygen
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: Monday, June 14, 2004 1:47 PM
To: [EMAIL PROTECTED]
Subject: Remote CVS access via SSH
Sorry if this does NOT belong to this group. I'm only hoping
someone
Hello list,
I recently installed cvs 1.11.13 (from source) on a Red Hat 9 box, and
am having issues connecting from remote machines. My setup is below...
CVSROOT is set to /webserver/vhosts with these lines in /etc/profile...
CVSROOT=/webserver/vhosts
export PATH USER LOGNAME MAIL HOSTNAME
John Nichel wrote:
CVSROOT is set to /webserver/vhosts with these lines in /etc/profile...
CVSROOT=/webserver/vhosts
export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC CVSROOT
Echoing out CVSROOT return this...
[EMAIL PROTECTED] CVSROOT]# echo $CVSROOT
/webserver/vhosts
The xinetd
Geoff Beier wrote:
snip
Why are you specifying /CVSROOT as your CVSROOT remotely when you've
specified /webserver/vhosts locally and in your pserver config? Try it
with /webserver/vhosts.
HTH,
Geoff
That was it. Thank you.
--
By-Tor.com
It's all about the Rush
http://www.by-tor.com
John Nichel writes:
server_args = -f --allow-root /webserver/vhosts pserver
That should be --allow-root=/webserver/vhosts.
cvs -d :pserver:[EMAIL PROTECTED]:/CVSROOT login
/CVSROOT: no such repository
cvs login: authorization failed: server devbox.local rejected access
to
Larry Jones wrote:
John Nichel writes:
server_args = -f --allow-root /webserver/vhosts pserver
That should be --allow-root=/webserver/vhosts.
In my reading, I think this argument will allow the user 'root' to
connect/change/etc to CVS. Is this correct? If this is the case, and I
John Nichel writes (quoting me):
That should be --allow-root=/webserver/vhosts.
In my reading, I think this argument will allow the user 'root' to
connect/change/etc to CVS. Is this correct?
Not even close; it specifies allowable root directories (i.e.,
repositories), it doesn't have
Eric Siegerman wrote:
On Wed, Oct 08, 2003 at 10:59:37AM -0700, [EMAIL PROTECTED] wrote:
but in general, someone who accesses cvs [via SSH] has system access.
not only can my co-developer do things like cvs checkout and cvs
commit, but he can also ssh into the machine and work at a remote
shell.
first, thanks everyone who answered my question.
second, this works like a charm. and i learned a WHOLE LOT in the
process.
On Tue 07 Oct 03, 9:38 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] said:
On Tue, 7 Oct 2003 [EMAIL PROTECTED] wrote:
hi all,
i've read about remote cvs access
On Wed, Oct 08, 2003 at 10:59:37AM -0700, [EMAIL PROTECTED] wrote:
this ssh method requires that my co-developer has an account on the
system containing the repository. i don't mind that, since he's a
friend.
but in general, someone who accesses cvs this way has system access.
not only can
On Wed, Oct 08, 2003 at 10:59:37AM -0700, [EMAIL PROTECTED] wrote:
but in general, someone who accesses cvs [via SSH] has system access.
not only can my co-developer do things like cvs checkout and cvs
commit, but he can also ssh into the machine and work at a remote
shell.
is there a way
hi all,
i've read about remote cvs access, and there are a LOT of options: ssh,
rsh, kerberos, pserver, and more.
my needs are simple. i'm writing a latex book with just one other
person. the repository is sitting on a debian gnu/linux machine that i
have root access to.
can someone suggest
On Tue, 7 Oct 2003 08:29:33 -0700, [EMAIL PROTECTED] wrote
hi all,
i've read about remote cvs access, and there are a LOT of options:
ssh, rsh, kerberos, pserver, and more.
my needs are simple. i'm writing a latex book with just one other
person. the repository is sitting on a debian
]
Subject: remote cvs access - recommendations
hi all,
i've read about remote cvs access, and there are a LOT of
options: ssh,
rsh, kerberos, pserver, and more.
my needs are simple. i'm writing a latex book with just one other
person. the repository is sitting on a debian gnu/linux
[EMAIL PROTECTED] writes:
on a related issue, i setup a pserver and was horrified to discover that
when i issued a cvs login, it was ignoring $CVSROOT/CVSROOT/passwd and
instead was authenticating using /etc/shadow. i inadvertantly sent a
plaintext password over the internet!
It doesn't
From: Terrence Brannon [EMAIL PROTECTED]>
Date: Wed Mar 27, 2002 09:38:40 AM US/Eastern
To: [EMAIL PROTECTED]
Subject: Re: [netlabs #457] Re: ready for dbi.perl.org
On Wednesday, March 27, 2002, at 03:21 AM, Robert (via RT) wrote:
When I run this command:
cvs -d :pserver:[EMAIL
CVS 1.11.1p1
I am attempting to setup a cvs server. The docs say to add
2401 stream tcp nowait root /usr/local/bin/cvs cvs -b /usr/local/bin
pserver
to the inetd.conf file but pserver doesn't seem to exist on my system.
cvs works fine otherwise. Should I already have the pserver app,
Shane McDaniel writes:
CVS 1.11.1p1
I am attempting to setup a cvs server. The docs say to add
2401 stream tcp nowait root /usr/local/bin/cvs cvs -b /usr/local/bin
pserver
No, they don't. Please see the 1.11.1p1 docs:
http://www.cvshome.org/docs/manual/cvs.html
-Larry
On Tue, 29 Jan 2002, Larry Jones wrote:
Shane McDaniel writes:
CVS 1.11.1p1
I am attempting to setup a cvs server. The docs say to add
2401 stream tcp nowait root /usr/local/bin/cvs cvs -b /usr/local/bin
pserver
No, they don't. Please see the 1.11.1p1 docs:
Shane McDaniel writes:
When I try to do a cvs login from another machine I get the error message
Unknown command: 'pserver' after I specify a password.
That indicates that your CVS executable doesn't include the server
functionality. If you run cvs -v, you should see something like:
On Sat, Nov 10, 2001 at 02:41:56PM -0500, Robert Nikander wrote:
I would like to use CVS to keep up with the 'bleeding edge' code for some
of these open-source development projects. Basically my question is...
can CVS be used to just download the differences every few days, without
getting
Hi,
I would like to use CVS to keep up with the 'bleeding edge' code for some
of these open-source development projects. Basically my question is...
can CVS be used to just download the differences every few days, without
getting all the files? And if so, what is the best way? Or do I need a
Harry Putnam writes:
Yeah, that already came up and was one of the reasons I started
posting here. Two fellow users posted CVS/Root. It looked exactly
like mine.
:pserver:[EMAIL PROTECTED]:/usr/local/cvsroot
Some are saying it has something to do with my IP not showing an A
record but
Harry Putnam writes:
Larry's response only repeated the patently obvious.
And as I mentioned. I'm able to connect to other cvs servers.
So a misconfiguration is a pretty good guess. Question is, how to
determine what is misconfigured. (From my end)
Let me spell it out more completely:
Harry Putnam wrote:
Gianni Mariani [EMAIL PROTECTED] writes:
maybe you can try a tcp forwarding thingy.
http://freshmeat.net/projects/tcp_forward/
and tweak it to dump the transaction.
That looks promising .. thanks.
If I knew more about tcpdump I guess I could find out
[EMAIL PROTECTED] (Larry Jones) writes:
[...]
Let me spell it out more completely: It's a server problem. Either the
And did you ever... A very nice help, thank you.
[...]
telnet cvs.myhost.com 2401
If the connection is immediately closed, then the server is
misconfigured (most
Harry Putnam writes:
Here I get a connection:
Trying 195.204.10.66...
Connected to cvs.gnus.org.
Escape character is '^]'.
Connection closed by foreign host.
That indicates that the CVS server is never getting started. Usually
that indicates an error in /etc/inetd.conf but...
I do
[EMAIL PROTECTED] (Larry Jones) writes:
That implies that the server has some kind of access control (perhaps
tcpd?) that is denying you access. You can find out how people are
connecting by asking them to tell you what's in CVS/Root in their
working directories.
Yeah, that already came up
Harry Putnam writes:
$ cvs -d :pserver:[EMAIL PROTECTED]:/usr/local/cvsroot login
Logging in to :pserver:[EMAIL PROTECTED]:2401/usr/local/cvsroot
CVS password: password
cvs [login aborted]: recv() from server cvs.gnus.org: Connection reset by peer
Either the server is misconfigured or
Harry Putnam [EMAIL PROTECTED] writes:
[...]
I wondered if there is a way to force verbosity, where the negotiation
get printed to tty or something similar so that I can see what is the
problem. The normal flags for that kind of stuff -[vV] are taken for
other things and I see no `debug'
PROTECTED]
Subject: Re: remote cvs connection analasys (debug)
Harry Putnam [EMAIL PROTECTED] writes:
[...]
I wondered if there is a way to force verbosity, where the negotiation
get printed to tty or something similar so that I can see what is the
problem. The normal flags for that kind
Setup: Redhat Linux 7.1
Cvs : 1.11.1p1 (client/server)
Having trouble with a remote connection that has worked in the past.
The server moved and ever since I cannot connect to it. I'm using the
right address far as I know and other people are successfully
connecting remotely to it.
I am able
Thanks for help, but i still couldn't solve my
problem.
First of all, my account on the server was already
configured to allow connection based on my ssh key.I
can do anything on cvs via ssh as long as i provide my
username and password each time i try to do something
on cvs.
I followed your
Hi everyone,
when i try to commit in cvs in KDevelop 1.4 i get a
message like this
You have no controlling tty.Cannot read Passphrase
our cvs repository is configured to accept remote
connections via SSH, i can do any changes in
repository if i try to access it in linux
console(providing
On Mon, Sep 10, 2001 at 08:41:34AM -0500, Colin Bester wrote:
Creating CVSROOT/passwd file is fine for attempting to protect users
system passwords, but still leaves the repository vunerable itself.
This is a red herring.
Avoid using pserver,
Give users accounts, and set them up using ssh.
Look in the archives for this message:
Subject: CVS passwd patch
Date:Thu, 16 Aug 2001 08:50:32 -0400
This patch offers one solution.
If you are paranoid about security then I recommend you also disconnect
your computer from the internet, remove any floppy drives, cd burners,
zip drives,
Sent: Monday, September 10, 2001 8:51 AM
To: [EMAIL PROTECTED]
Subject: Re: Remote cvs and security
On Mon, Sep 10, 2001 at 08:41:34AM -0500, Colin Bester wrote:
Creating CVSROOT/passwd file is fine for attempting to protect users
system passwords, but still leaves the repository vunerable
[ On Monday, September 10, 2001 at 14:22:25 (-0700), Josh Baudhuin wrote: ]
Subject: RE: Remote cvs and security
Well, pserver + CVSROOT/passwd is one thing, but using pserver with the
default authentication of the system isn't so bad. Passwords are stored
in the same way that /etc/passwd
PM
To: Josh Baudhuin
Cc: CVS-II Discussion Mailing List
Subject: RE: Remote cvs and security
[ On Monday, September 10, 2001 at 14:22:25 (-0700), Josh
Baudhuin wrote: ]
Subject: RE: Remote cvs and security
Well, pserver + CVSROOT/passwd is one thing, but using pserver
Quoting Colin Bester ([EMAIL PROTECTED]):
I am pretty new to these aspects as I have always worked in a closed and
'safe' environment and now find myself at the other end of the spectrum.
I would really appreciate some comments on what the correct steps would
be to secure this link.
CVS
[ On Monday, September 10, 2001 at 19:37:23 (-0500), Colin Bester wrote: ]
Subject: RE: Remote cvs and security
Greg, I would like to know what alternatives you are referring to.
SSH, even within the VPN, for one. Kerberized rsh for another. Even
just plain old rsh is better than pserver
[ On Tuesday, September 11, 2001 at 02:58:11 (+0100), Alex Holst wrote: ]
Subject: Re: Remote cvs and security
CVS can tunnel it's traffic over SSH, which provides you with encryption,
and you are free to use whatever method of authentication your SSH client
and server supports.
Careful
Mike Castle [EMAIL PROTECTED] writes:
On Mon, Feb 05, 2001 at 05:05:51PM -0600, David H. Thornley wrote:
I recommended setting CVS_RSH=ssh, and was told that the users
then had to type in their password for every file being transferred,
and that is more typing than they're willing to put
I think this is a ssh issue. Have you tried using ssh-agent?
In the past, I've been able to configure CVS to use SSH in such a way as not to
experience the problems you describe, so, it is possible, although I may have
forgotten details of this implementation.
Noel
We have a lot of source
and +/- of them.
HTH
Eugene.
: -Original Message-
: From: David H. Thornley [mailto:[EMAIL PROTECTED]]
: Sent: Monday, February 05, 2001 3:06 PM
: To: [EMAIL PROTECTED]
: Subject: Secure remote CVS
:
:
: We have a lot of source code that needs to be kept secure. Right now,
: we're using
We have a lot of source code that needs to be kept secure. Right now,
we're using a LAN protected from the outside world by a firewall,
and that seems to be working.
Now we'd like to be able to use CVS over considerably longer
distances, securely.
I recommended setting CVS_RSH=ssh, and was
On Mon, Feb 05, 2001 at 05:05:51PM -0600, David H. Thornley wrote:
I recommended setting CVS_RSH=ssh, and was told that the users
then had to type in their password for every file being transferred,
and that is more typing than they're willing to put up with.
What implementation of ssh are
On Mon, 5 Feb 2001, David H. Thornley wrote:
Now we'd like to be able to use CVS over considerably longer
distances, securely.
I recommended setting CVS_RSH=ssh, and was told that the users
then had to type in their password for every file being transferred,
and that is more typing than
Howard Zhou wrote:
... verifymsg doesn't help much since it doesn't allow you to modify
cvs log. ...
FYI. The FreeBSD variant of cvs 1.11 does allow verifymsg to modify
the log message. It is a very useful feature that I would like to see
rolled back into the cvshome.org version of cvs. The
- Original Message -
From: "Larry Jones" [EMAIL PROTECTED]
To: "Mike McKay Jr." [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, January 24, 2001 7:38 AM
Subject: Re: Remote CVS and CVSROOT/editinfo scripts requiring tty input
Mike McKay Jr. writes:
I ha
Mike McKay Jr. writes:
I have scripts specified from CVSROOT/editinfo that require user input
during a commit (the perl script does something like "$answer =
STDIN"). These scripts work fine using local CVS. However, when I
use remote CVS (using ssh), the scripts do not promp
Larry Jones wrote:
Mike McKay Jr. writes:
I have scripts specified from CVSROOT/editinfo that require user input
during a commit (the perl script does something like "$answer =
STDIN"). These scripts work fine using local CVS. However, when I
use remote CVS (using ssh), t
Hey,
I have scripts specified from CVSROOT/editinfo that require user input
during a commit (the perl script does something like "$answer =
STDIN"). These scripts work fine using local CVS. However, when I
use remote CVS (using ssh), the scripts do not prompt the user for
info.
Is t
Larry Jones wrote:
[EMAIL PROTECTED] writes:
Hum... I think that it isn't inheriting $HOME from tcpserver. I have
tried using other uid/gid (btw, I created an new user for this
purpose), and I received the following error message:
setuid failed: Operation not permitted
cvs
Feng Sian writes:
Bad news: it didn't worked. I created an user named devel, and in
$CVSROOT/CVSROOT/passwd I set the following line
feng::devel
and then I started tcpserver with -udevel-uid -gdevel-gid ...
, but it continue to complain with the following error message:
setuid
Larry Jones wrote:
What is $CVSROOT set to?
/works/CVS
# ls -lF /works
...
drwxrwxr-x 4 feng devel4096 Oct 3 15:24 CVS
...
I have switched back to run the process as root, but I have some questions:
- if tcpserver is invoked from root, and the program is ran as root (#
Feng Sian writes:
What is $CVSROOT set to?
/works/CVS
I meant for the client -- it should start with :pserver:.
The correct $HOME value should then be the users' home? I'm wondering if running
a script to set the correct values for $HOME would work... But this solutin seems
pretty
Hi,
I'm having trouble checking code out of a CVS server using the
WinCVS.
Running from a terminal connected to the server, everything seems
okay: I can import, checkout, update, commit. Using the WinCVS, I
can
also login, import, but I can't checkout anything!
The CVS pserver run on a
Hi,
I bit more info: the very same error happens when I try
cvs -d :pserver:[EMAIL PROTECTED]:/works/CVS co multifretes
on the machine where the pserver is running. The is somway to disable
the pserver to chdir into /root?
--- In [EMAIL PROTECTED], [EMAIL PROTECTED] wrote:
Hi,
I'm
[EMAIL PROTECTED] writes:
The CVS pserver run on a Slackware 7; the pserver being started with
the following command:
/sbin/tcpserver -v -u0 -g0 0 2401 /usr/local/bin/cvs \
--allow-root=/works/CVS pserver 21 | /sbin/splogger cvs 3
Why are you using tcpserver instead of
hi,all!
i'm a newer of cvs. We want to develop a
project through a LAN network. i use cvs in Linux and i had modified the files
/etc/services and /etc/inetd.conf, telnet test was also OK.
But, when i connect the server from another machine or
localhost.The error message is :
Pavel Roskin writes:
CVS operating as _server_ has absolutely no business in $HOME,
whether it is set or not.
That's why the Cederqvist manual (now) recommends using -f for servers
-- the only reason CVS looks in $HOME is to find ~/.cvsrc, and I've not
heard anyone claim that ~/.cvsrc was
75 matches
Mail list logo