Re: [Fwbuilder-discussion] Firewall Builder 2.0 beta, new build #206
Brought to you by:
mikehorn
From: Vadim K. <va...@vk...> - 2004-06-05 20:10:40
|
On Jun 5, 2004, at 12:40 PM, Doug Lytle wrote: > Vadim, > > It would appear that the doughboi.fw script is compiled in the > c:\Program Files\FWbuilder folder, not the working directory > specified, so scp doesn't find it. Log below: > Did you recompile firewall script using the new code ? Compiler is supposed to put the script it produces in the working directory if it is specified, or in the same directory where .fwb file is located if working directory is not specified. Please recompile and check manually where did .fw file appear, is it in c:\ or somewhere else ? also installer expects .fwb file to be in the working directory as well. Is it there? I need to add few checks to the code to make sure it behaves reasonably if the files are not where they are expected to be. --vk > Summary:* firewall name : doughboi > * user name : root > * management address : 66.227.xxx.xxx > * platform : iptables > * host OS : linux24 > * Loading configuration from file C:/doughboi.fwb > Running command 'C:/Program Files/PuTTY/pscp.exe -pw XXXXXX -v -q C:/ > ro...@66...:/etc/fw' > > Server version: SSH-1.99-OpenSSH_3.6.1p2 > We claim version: SSH-2.0-PuTTY-Release-0.54 > Using SSH protocol version 2 > Doing Diffie-Hellman group exchange > Doing Diffie-Hellman key exchange > Host key fingerprint is: > ssh-rsa 1024 59:69:37:a4:b9:3a:80:a1:c4:a0:33:10:7b:xx:xx:xx > Initialised AES-256 client->server encryption > Initialised AES-256 server->client encryption > Using username "root". > Keyboard-interactive authentication refused > Sent password > Access granted > Opened channel for session > Started a shell/command > Using SFTP > Connected to 66.227.xxx.xxx > > scp: C:/: not a regular file > > Sent EOF message > Server sent command exit status 0 > All channels closed. Disconnecting > SSH terminated, exit status: 1 > Error activating firewall policy > > Vadim Kurland wrote: > >> >> - added some more debugging printing in installer, trying to >> troubleshoot problem reported by Doug >> > > |