Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*client\s+schedule\s+security\s+question\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*client\s+schedule\s+security\s+question\s*$/: 9 ]

Total 9 documents matching your query.

1. client schedule security question (score: 1): Author: Dirk Kastens <dkastens AT RZ.UNI-OSNABRUECK DOT DE>; Date: Thu, 3 Apr 1997 10:52:04 +0200; Hi, the client schedule gives the possibility to define an operating system command that is executed on the client at a specific point in time. I played around a bit with this option and could succes; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1997-04/msg00064.html (11,854 bytes)
2. client schedule security question (score: 1): Author: John Viksne <viksnej AT VNET.IBM DOT COM>; Date: Thu, 3 Apr 1997 07:13:57 PST; Hallo Dirk, Any workstation running an ADSM schedule can prevent ANY OS command from being executed by entering (for UNIX in the dsm.sys file) either a "PREschedulecmd" or "POSTschedulecmd" with eith; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1997-04/msg00073.html (11,401 bytes)
3. Re: client schedule security question (score: 1): Author: Steven P Roder <tkssteve AT ACSU.BUFFALO DOT EDU>; Date: Thu, 3 Apr 1997 11:08:50 -0500; Not true. The password is encrypted, and then sent. To decrypt it, one would need to know the key being used. Steve (unVMix Systems Programmer/Dude) Roder (tkssteve AT ubvm.cc.buffalo DOT edu | tkss; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1997-04/msg00086.html (11,506 bytes)
4. Re: client schedule security question (score: 1): Author: Tom Denier <tom AT STAFF.UDC.UPENN DOT EDU>; Date: Thu, 3 Apr 1997 11:56:36 -0500; If the person running dsmadmc is using telnet or an X terminal to connect to the system where dsmadmc actually runs, the password will probably go from the desk top to dsmadmc in clear text (there ar; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1997-04/msg00089.html (11,690 bytes)
5. Re: client schedule security question (score: 1): Author: Steven P Roder <tkssteve AT ACSU.BUFFALO DOT EDU>; Date: Thu, 3 Apr 1997 13:59:04 -0500; I think you are mistaken. The clear text password never leaves the server or the client. Perhaps someone from ADSM development can jump in here and clearly explain how the negotiation works. Steve (u; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1997-04/msg00096.html (11,864 bytes)
6. Re: client schedule security question (score: 1): Author: Tom Denier <tom AT STAFF.UDC.UPENN DOT EDU>; Date: Thu, 3 Apr 1997 14:40:59 -0500; You have missed the point of my note entirely. In some environments the password will pass over the network in clear text before the administrative client code ever sees it. For example, I interact w; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1997-04/msg00097.html (12,515 bytes)
7. Re: client schedule security question (score: 1): Author: "Paul L. Bradshaw" <paulb AT DATATOOLS DOT COM>; Date: Thu, 3 Apr 1997 12:01:17 -0800; At client "signon" to the server, ADSM will create a session key (pulls it out of the hat) and use the current password to encrypt this a few different ways. If after multiple exchanges between the c; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1997-04/msg00099.html (14,066 bytes)
8. Re: client schedule security question (score: 1): Author: Steven P Roder <tkssteve AT ACSU.BUFFALO DOT EDU>; Date: Thu, 3 Apr 1997 17:30:33 -0500; Sorry, I see your point. However, that is not a failing of ADSM, but of your use of it. We use ssh here, which can encrypt remote X sessions. Steve (unVMix Systems Programmer/Dude) Roder (tkssteve AT; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1997-04/msg00103.html (12,522 bytes)
9. Re: client schedule security question (score: 1): Author: Dirk Kastens <dkastens AT RZ.UNI-OSNABRUECK DOT DE>; Date: Fri, 4 Apr 1997 10:52:53 +0200; Yes, that really works. It's also explained in the client's options.doc but not in the "define schedule" section of the Administrator's Reference, where I think it should be mentioned. That's good to; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1997-04/msg00111.html (12,102 bytes)

Current List: 1 - 9
Page: [1]