[p4] trigger icon on NT machine - Andrew Dalgleish - com.perforce.perforce-user

3 messages in com.perforce.perforce-user[p4] trigger icon on NT machine

From	Sent On	Attachments
Gina Lacava	19 Jul 2000 06:55
Paul Goffin	19 Jul 2000 07:17
Andrew Dalgleish	20 Jul 2000 02:09

Subject:	[p4] trigger icon on NT machine
From:	Andrew Dalgleish (andr...@axonet.com.au)
Date:	07/20/2000 02:09:47 AM
List:	com.perforce.perforce-user

Message: 2 Date: Wed, 19 Jul 2000 08:55:57 -0500 From: "Gina Lacava" <glacava at theocc.com> To: perforce-user at perforce.com Subject: [p4] trigger icon on NT machine

I'm looking for a way to place an icon on the NT desktop which will sync from the depot (on a UNIX box) to a client workspace which also resides on the UNIX box, (NOT to the client workspace which resides on the local machine). Any ideas?

[Andrew Dalgleish]

Install the p4 client on your unix box. Install SSH server on your unix box. Install SSH client on your NT machine. Create a SSH1 identity file (or SSH2 id_dsa file) which does not require a password. Create a short cut on your NT box which uses SSH to execute a command on your unix box.

Problem: If your NT box is compromised the intruder could use the SSH identity file to gain access to the unix box.

Solution: Get rid of your NT box. :-)

Work-around: Have the NT shortcut login to the unix box using a *very* restricted account on the unix box, and create or modify a flag file. (You could even create a login shell executable whose only function is touch a file in the user's home directory.) On the unix box, have a script running in a *different* account watch for changes to the flag file, then do the sync.

Which SSH client on the NT box?

I use cygwin for all my build scripts, and cygwin supports SSH1 and SSH2. http://sources.redhat.com/cygwin/ (Cygwin even includes an SSH server :-)

If you do not need scripting on the NT box have a look at MindTerm, a GPL Java client for SSH1. http://www.mindbright.se/mindterm/

Both of these clients work well for tunneling through firewalls.

Another thing which might interest you: My scripts use SSH2 to copy the build log and binaries onto an OpenBSD box, and I use BigBrother to display success/failure for each build process. http://bb4.com If a build fails, BB can send an email/page/sms to you (or the responsible developer).