On Tue, 27 Nov 2001 21:58:57 -0700, Gregory J. Feig wrote: > On Tue, 27 Nov 2001, Clarence Verge wrote:
>> As I mentioned on AQC, I don't know about the APM - don't trust ANY >> ..APMs - but if you can extract SSHDOS.exe from it, put it where the >> sun from wattcp.cfg can't shine on it and type SSHDOS -?. >> I have it in arachne main directory and renamed wattcp.cfg to .sav. >> You can use it at the command prompt (if you are already online) or >> you can set up a .dgi in MIME.cfg to run it for you. > Gee, Clarence, that was sure fun....<g g g>...after I did all that, > then tried to redial, I found that WATTCP.CFG is ABSOLUTELY required > for my setup to connect....<g> That's a shame Gregy - I don't know what you are using Wattcp on reglar connection for - never had a use for it myself - but if I let SSHDOS find it, it can never resolve the address, and if I hide wattcp.cfg then SSHDOS says: Configuration file not found...configuring via BOOTP.DHCP - and it works fine. <G> > .....so...what's the next step...??? > ....I feel like we're making progress....<g g g>....and the thought > of having a MIME.CFG .dgi-type set up so that whenever I run into an > https URL, MIME will just automagically kick SSHDOS in, giving me the > Username/Password boxes....which I fill in and click the SEND button, > whereupon Arachne continues on, with me NOW signed on to that https > site and smoothly surfing away....hmmm.... Aint gonna happen. SSH is Secure SHell. Not https. Different port. Lemme see. Here are some familiar port names and numbers snipped and edited from the file SERVICES with SSHDOS: ftp 21/tcp ssh 22/tcp # Secure Shell Login ssh 22/udp # Secure Shell Login telnet 23/tcp smtp 25/tcp mail www-http 80/tcp pop3 110/tcp postoffice https 443/tcp https # Secure http, MCom https 443/udp https # MCom Very strangely, the two ssh lines were NOT in the SSHDOS file and I had to pull them from DragonLinux. I hope that clarifies it a bit more ? - Clarence Verge - Back to using Arachne V1.62 ....
