[279] in DeathTongue Changes
Re: deathtongue
daemon@ATHENA.MIT.EDU (Richard Edelson)
Tue Oct 29 23:36:54 2002
Date: Tue, 29 Oct 2002 23:36:29 -0500
To: "Thomas L. Thornton" <tomt@MIT.EDU>, hartmans@konishi-polis.MIT.EDU
From: Richard Edelson <redelson@MIT.EDU>
Cc: rotenberg@washofc.cpsr.org, licks@MIT.EDU, pismere-ops@MIT.EDU
In-Reply-To: <200210292350.SAA15886@the-rim.mit.edu>
Regardless of how this was run, I can say I have had this problem running
SecureCRT 3.4.6 on my WinAthena
workstation with the H: drive mapped to my AFS home directory. What I found
was that there was a bug in
SecureCRT that prevented the application from writing any data to AFS. The
application tries to run it's config
data to the following path:
"H:\WinData\Application Data\Van Dyke Technologies\SecureCRT\Config'
this is because it is trying to write it to %APPDATA%\Config, which resides
on AFS.
When you set SecureCRT to write the Config directory to a path on C it
works fine.
Also, to store host keys, you will need to change SSH2.ini because it still
will try using the old path :
S:"Host Key Database Location"=H:\WinData\Application Data\Van Dyke
Technologies\SecureCRT\HostKeyDatabase\
I changed it to S:"Host Key Database Location"=C:\Program Files\SecureCRT
3.0\Config which is the path I am using for
the config data, and it's working now.
Richard
At 06:50 PM 10/29/2002 -0500, Thomas L. Thornton wrote:
>Sam,
>
>Following:
>
> > "Thomas" == Thomas L Thornton <tomt@MIT.EDU> writes:
> >
> >> Regarding:
> >>> While logged in as sipb0, I tried to run SecureCRT. It asked
> >>> me to create a config file in my homedir, and when I clicked
> >>> "Ok", it failed with the error
> >>>
> >>> The folder is not valid: 'H:\WinData\Application Data\Van Dyke
> >>> Technologies\SecureCRT\Config' Please choose another folder.
> >>>
> >>> If this is failing due to some customization made by someone on
> >>> this list, then they should fix what they broke. If SecureCRT
> >>> is normally installed on WinAthena and it's broken out of the
> >>> box, someone should report it upstream.
> >
> >> One of our students encountered this last year, but we
> >> have yet to alter, or even port, the installer:
> >> ...
> >
> > Interesting. I've actually noticed similar failures with some
> > applications I've tried to install. The application tries to create a
> > file in a non-existent directory in my home directory.
> >
> > Why does the application fail on Pismere but not on a normal setup?
>
>Maybe a couple things. First, a (I presume) local account like sipb0
>would not have an AFS profile mapped to its H: drive, to which a
>pismere machine redirects profiles. Second, the app and pismere ACLs
>might prevent anyone but a local admin account to write to other
>registry or configuration dirs. I can't remember if SecureCRT
>requires local admin privilege.
>
>Note SecureCRT v3.1.2 has newer versions. There is a 3.4, but
>according to the VanDyke FAQ, it still wants you to copy your profile
>to the default location: C:\Documents and Settings\<user>\Application
>Data\VanDyke\SecureCRT\Config, which means a non-redirected profile
>per machine.
>
>Paul says he has a version 4, but no installer yet. Instead of the
>manual registry and config dir changes you have to use on v3, perhaps
>the new one will behave better. I would like to see pismere-team test
>it first, but if you would like to try to build an installer, please
>speak up.
>
>-Tom
