You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Summary

Chuck has generated workbook pages describing how to use SSH and how to get CVS going:

http://glast-ground.slac.stanford.edu/workbook/pages/getting_connected/ssh_forwindows.htm
http://glast-ground.slac.stanford.edu/workbook/pages/installingOfflineSW/devWindowsDesktopInstall.htm

Remaining issues

Line mode CVS and MrVCMT

Create the following file

c:\Program Files\PuTTY-GSSAPI\cvs-ssh.cmd
@echo off
"c:\Program Files\PuTTy-GSSAPI\plink.exe" -g -2 -batch %*%

set the following environment variable.

set CVS_RSH=c:\Program Files\Putty-GSSAPI\cvs-ssh.cmd

Log in once manually using PuTTY to centaurusa.slac.stanford.edu to make sure you have the key cached.

You should be set to go:

cvs status

Generic node names (e.g. noric)

If you use generic names like noric putty will complain about the yet each time you login. For tera-term SCCS had some known-hosts file which could work around this, but it is not currently known how to make this work for PuTTy.

Toby's problem

Toby gets the following error when connecting...

d:\users\burnett>"C:\Program
Files\PuTTY-0.58-GSSAPI-2005-07-24\plink.exe" -v -g -l burnett noric05 Server version: SSH-2.0-OpenSSH_4.4 We claim version: SSH-2.0-PuTTY_Release_0.58_GSSAPI Using SSH protocol version 2 Doing Diffie-Hellman group exchange Doing Diffie-Hellman key exchange Host key fingerprint is:
ssh-rsa 1024 53:1b:54:a5:49:f3:31:21:08:83:bf:e0:bf:aa:4a:ab
Initialised AES-256 client->server encryption Initialised HMAC-SHA1 client->server MAC algorithm Initialised AES-256 server->client encryption Initialised HMAC-SHA1 server->client MAC algorithm Using username "burnett".
GSSAPI: trying GSSAPI auth
GSSAPI: ssh_gss_acquire_cred
GSSAPI error: Miscellaneous failure
GSSAPI error: Miscellaneous failure
GSSAPI mech specific error: Can't open/find Kerberos configuration file GSSAPI mech specific error: Can't open/find Kerberos configuration file GSSAPI error: Miscellaneous failure GSSAPI error: Miscellaneous failure GSSAPI mech specific error: Can't open/find Kerberos configuration file GSSAPI mech specific error: Can't open/find Kerberos configuration file GSSAPI error: Miscellaneous failure GSSAPI error: Miscellaneous failure GSSAPI mech specific error: No error GSSAPI mech specific error: No error

Leon's problem

Leon reports

One of my problems is that the keys seem to get lost from one session to the next. I can log on to say noric08 two times, and each time it asks to register the key. The key it displays is the same each time.

Also when tortoise accesses cvs I get a page of complaints related to the key, even though I've logged on to centaurusa many times.

Heather's problem

I have a slightly different and new problem (smile) Last week when I set up and tired out the network Identity Manager, I was able to log in with my password and all was fine. Today, I tried, and after submitting my password, I receive the following message

I do have SLAC.STANFORD.EDU in all caps. Is there something obvious that may have changed since last week.. other than that ssh1 is now off?

  • No labels