search for: chiaki

Hi, I use OpenSSH (thanks folks) to administer a mix of boxes at work and have seen some quite scary problems. I set up an ssh connection from the host to a central admin machine from a perl script running on the host. The script brings up an ssh connection to the central admin machine and sets up some reverse port redirection for administration (telnet for instance) and some forward

subject: ssh non-intuitive logging setting (priority names). I installed openssh 2.3.0p1 on Solaris 7 for x86 box and sshd worked fine. However, somehow the logging of connection and disconnection to sshd was not recorded as I wished. Time to investigate. On a host where sshd from data-fellows once ran, the log was recorded with auth.info level. After trying to modify sshd_config, I found that

...HAN_OUTPUT_CLOSED 0x80 Oh, I forgot. The remote server runs the sshd from the original ssh distributions (not sure which version). I wonder if there is a way to shut up ssh so that these warning lines won't be printed. Thank you again for the great free package! Happy Hacking Chiaki Ishikawa

Known issues: 1) Linux 'sleep 20' -- Unfixable before 2.5.0 (known work around) 2) HP/UX signal issue -- Patched and HP/UX 11 works in v2 3) SCO 2/ Native Compiler -- Unfixable before 2.5.0 (known work around) 4) NeXTStep -- Resynced, MAX_GROUPS vs NGROUPS unresolved (not major) 5) DG/UX regcomp/regexec -- Fixed. 6) Cray signal issues -- ??? 7) Solaris '$PATH' issue -- ??

X-PMC-CI-e-mail-id: 13726 Hi, I have been a successful user of Openssh for some time. I am attaching two articles from BugTraq. Hopefully, they show exactly the security problems reported in the BugTraq mailing list. [Pity that no one seemed to have bothered to contact the mailing list(s) for openssh development.] I am not sure what the right fixes would be. But at least, people need to be