Re: Auto configuration failed

On Sep 13, 10:30 am, Uwe Seher <red.bu...@xxxxxxxxxxxxxx> wrote:
Hello group!

i get a strange error when i try to start an sshd (v5.4) on an opensuse
11.3 machine. It is installed by the packetmanager. The first time it
worked, but when i did some configuration the daemon suddenly refused to

By "some configuration", what do you mean? Could you have added an
error in /etc/ssh/sshd_config that is confusing the daemon?

Revert your changes, or back up your changes, rip out the package and
re-install it to compare the config files.

Now when i try to start the daemon, by startscript, manual or at
boottime the message below shows up and the daemon doesnt start.

Auto configuration failed
140472990594728:error:0200100D:system library:fopen:Permission

What in the? OK, what did you do to /etc/ssl/openssl.conf? Have you
been trying to replace or overwrite your OpenSSL components? That
would be.... begging to introduce incompatibilities with other tools,
if you didn't use RPM deployment for them.

140472990594728:error:2006D002:BIO routines:BIO_new_file:system
140472990594728:error:0E078002:configuration file
routines:DEF_LOAD:system lib:conf_def.c:199:

The konfiguration doesnt matter, it doesnt work with original setup nor
with a working configutration. Logfile entries (in /var/log/messages)
are not written.
As a workaround i downloaded and compiled the v5.6-openssh, which works
without problem, with the same konfiguration and the same settings like
the opensuse-version. Has someone a hint for me, what produces this
strange error? Aunt Google seems also a little bit clueless in this case....

OpenSuSE is its own unique environment, and gods only know what
manually installing a new OpenSSH overlaid on top of your old one. Set
aside the manually compiled one, as much as possible, and use 'rpm -V
openssh' or 'rpm -V openssh-server', or whatever it is called for
OpenSuSE, to see what configurations you changed.

I can see where Google might have issues finding this: I think you've
managed to accidentally muck up sshd_config, and that's a fairly
unusual issue, different everytime it happens.

Thank you

Uwe Seher