Re: [Re: support cvs login for rsh mode?]
Many thanks for the explanation. I will look into SSH. Are there any more detailed reference for configuring/using SSH with CVS? On another topic, I get following message: Must be attached to terminal for 'am I' option How can I get rid of this? Thanks again. regards, ls [EMAIL PROTECTED] (Greg A. Woods) wrote: [ On , July 2, 1900 at 00:51:37 (JST), lucky seven wrote: ] Subject: support cvs login for rsh mode? It would be nice to support cvs login for :ext: same as :pserver: , that is, a new line will generate in HOME/.cvspass for accessing via ext and that line will be removed at cvs logout. Due to security reason, .rhosts is not allowed. Ah, no, it wouldn't actually. Doing so would again make CVS the weak link in whatever security they provide. Any external remote execution facility will supply its own method of eliminating user interaction during authentication, if that should be safe to do given the style of authentication. Certainly rsh and all versions of ssh provide such mechanisms currently so there's definitely no need to make CVS the weak link in them. If ~/.rhosts is not allowed in your environment and yet you're still using RSH then you've got some seriously brain-damaged security people! The only major loop-hole in the ~/.rhosts facility is that it allows ordinary users to grant authorisation to other users. However if your site is auditing for the presence of ~/.rhosts files then they can just as easily audit their contents and thus prevent such a loop-hole with no additional added risk (and in fact in some scenarios the overall risks go *WAY* down when you allow ~/.rhosts because people stop typing their passwords in the clear -- in fact forcing ~/.rhosts can be enormously more secure than plain old telnet (it all depends on your exact circumstances of course, including what threats you face). Indeed if your site is not allowing ~/.rhosts then they certainly won't allow a ~/.cvspass for RSH! (at least not so long as they have two functioning neurons to rub together! ;-) You should probably switch to SSH in any case though. -- Greg A. Woods +1 416 218-0098 VE3TCP [EMAIL PROTECTED] robohack!woods Planix, Inc. [EMAIL PROTECTED]; Secrets of the Weird [EMAIL PROTECTED] Get your own FREE, personal Netscape WebMail account today at http://webmail.netscape.com.
Re: [Re: support cvs login for rsh mode?]
On Monday, July 3, lucky seven wrote: Many thanks for the explanation. I will look into SSH. Are there any more detailed reference for configuring/using SSH with CVS? On another topic, I get following message: Must be attached to terminal for 'am I' option How can I get rid of this? Thanks again. Usually a "problem" with your .login/.cshrc/.bashrc/.etc files. Don't make them run programs that may output strings upon a non-session login. IE: test from $prompt (or whatever the convention is in your shell), and don't use 'who am i' when the console is not defined... --Toby.
Re: WinCVS case problem
Hi Michael, "Michael S. Tsirkin" schrieb: I am using WinCVS 11b4 I have the following problem: when a file is created with a mixed-case (upper/lower) name, e.g. BuildFlow.html After I add it to cvs and commit, in the repository I see the file buildflow.html Which sort of repository access do you use and where is your repository located? I got a similar situation when I tried to copy files from Windows to a locally mounted Unix "drive" (via ASU). All file names were converted to lower case by ASU - the same situation with Samba on a Linux server however worked fine. So if you use (Win)CVS to access a Unix repository via local mode in such an environment you may get the same problems with CVS as I got with simply copying files. You may consider to use one of the client/server modes instead. At least with pserver I didn't get such problems. Best regards Martin
cvs login to remote system
Problem: I want use CVS to a remote system where is the reposity.1) I have modified /etc/inetd.confcvspserver stream tcp nowait root /usr/local/bin/cvscvs --allow-root=/home2/users/alberto/reposity pserver2) reboot the system3) I have created the file passwd in CVSROOT4) Connect using the command cvs login to the remote reposity:cvs -d :pserver:alberto@sunultra:/home2/users/alberto/reposity login(Logging in to alberto@sunultra)cvs [login aborted]: unrecognized auth response from sunultra: cvs pserver:No CVSROOT specified! Please use the `-d' optionI have specified -d Alberto Toietta
Unsubscribe
I'll view the messages through the web. Thanks.
Diff / Status problem on WinNT
Maybe this is an error which may come up in rare circumstances and maybe it is fixed yet (in which version???) We're using WinCVS 1.06 and commandline client 1.10.5 on NT machines and local access to the repo on a linux box via Samba. We detected the following problem: dir1 +subdir1 |+---File1.hpp |+---xxx | +---File1.hpp +---xxx The File1.hpp-files were added and commited at the same time and when I make cvs status I can see the same time stamps. But the files have definitly different contents. When I copy File1.hpp from subdir1 over File1.hpp in dir1 and wincvs is not running then neither cvs status nor cvs diff can detect that the file has changed. This is wrong since the project in dir1 gets broken. Anyone get an idea what went wrong? Tia Markus -- COLOUR CONTROL Farbmeßtechnik GmbH Markus Niebel Bornaer Straße 205 mail: [EMAIL PROTECTED] D-09114 Chemnitz / Germany
UNSUBSCRIBE
WOW! Email flood! I'll just view things via the web. Thanks! Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
Re: cvs login to remote system
Did you set the CVSROOT environment variable in profile? If you are running LINUX, see: http://www.michael-amorose.com/cvs/ -m - At 11:59 AM +0200 7/3/00, Alberto Toietta wrote: Problem: I want use CVS to a remote system where is the reposity. 1) I have modified /etc/inetd.conf cvspserverstreamtcpnowaitroot/usr/local/bin/cvs cvs--allow-root=/home2/users/alberto/repositypserver 2) reboot the system 3) I have created the file passwd in CVSROOT 4) Connect using the command cvs login to the remote reposity: cvs -d :pserver:alberto@sunultra:/home2/users/alberto/reposity login (Logging in to alberto@sunultra) cvs [login aborted]: unrecognized auth response from sunultra: cvs pserver: No CVSROOT specified! Please use the `-d' option I have specified -d Alberto Toietta
Re: Can't pass options when using pserver or ext
On Fri, Jun 30, 2000 at 10:08:22AM -0700, Eric / Chang-Cheng, Chao wrote: Hi, I am having problems trying to checkout a branch from a remote repository. I tried both methods, pserver and ext. Both didn't work. The problem seems to be that I can't pass any options to update at all. All options are seemed to be assumed for cvs. For example if I do "cvs update -r Release-05_20_2000-branch", cvs assumes that the "-r Release-05_20_2000-branch" is for cvs and not for update. The same goes for any other cvs commands, eg. cvs status, cvs log, etc. I just can't pass any options to them. If I execute the commands on the machine where the repository resides, everything is ok. Is there a way around this problem ?? There shouldn't be such a problem :). Maybe your specification of CVSROOT has an annoying glitch ... Cheers, Matthias -- Matthias Kranz [EMAIL PROTECTED] http://www.belug.org/~kranz "Ever tried. Ever failed. No matter. Try again. Fail again. Fail better." (Samuel Beckett)
Re: recent commits not being seen
On Sat, Jul 01, 2000 at 03:22:44PM -0400, David Storrs wrote: We've got a small team and none of us are very experienced with CVS...I've used it before, but I've never administered it. Of the three people who are working from this office, two of us have no problems whatsoever. The third guy (Paul), has constant problems...when he does an update (i.e.: "cvs update" in the top-level directory of the project), he does not get the most recent versions of the files. We discovered that he did not have a CVS directory in his top-level project directory, so we tried inserting one manually and allowing cvs to fill it. That didn't work; CVS started crashing right and left. I doubt I've given enough information for anyone to solve this problem, but I don't even know where I should be looking...if you can tell me what questions to ask or what information to provide so that our problem CAN be solved, I would be very grateful. Hmm, maybe you want to set the 'TopLevelAdmin' in $CVSROOT/CVSROOT/config to 'yes'? Otherwise you have always to either specify the repository via '-d' or through the CVSROOT environment variable when working at top of the project. Cheers, Matthias -- Matthias Kranz [EMAIL PROTECTED] http://www.belug.org/~kranz "Ever tried. Ever failed. No matter. Try again. Fail again. Fail better." (Samuel Beckett)
Description message, cvs add -m and cvs admin -t
It appears that 'cvs add -m "new file description message"' doesn't create an entry in the desc field of the ,v file in the repository. Additionally, I can't seem to get 'cvs admin -t' to work to change the description field. I've confirmed this with server and client version 1.10.5 and client 1.10.8 (using the same server). Am I missing something here? Has this been fixed in later versions of the server? ksb
Modifing files in/out of repository
Hello, I am trying to modify files during the checkout/checkin processes. For example, make sure and run JIndent prior to committing. I thought I might be able to get away with using the -i/-o/-u option of modules but it seems to me that this would have to work on the ,v files. (Is this true?) I would like any modifications to occur prior to cvs diff formatting. Is this possible? I have looked through the documentation and this egroup but seem to be coming up pretty much empty on finding anything. Just for info I am using pserver with a variety of client OS machines. Thanks for any info
Re: recent commits not being seen
Hello! On Sat, 1 Jul 2000, David Storrs wrote: [skipped] it. That didn't work; CVS started crashing right and left. It happens quite rare in other mailing lists I'm subscribed to, but it's very common for [EMAIL PROTECTED] that people post messages about problems without even giving the version of CVS, not to mention any other details. It gets annoying. People don't even think that the problem might have been fixed since the version they are using. They don't trust us any information about their systems, and yet they want us to help. Maybe somebody of us knows a URL describing how to report bugs properly - then whoever reading such messages could post that URL as a reply (after excluding [EMAIL PROTECTED] from cc:, of course) Regards, Pavel Roskin
