Openssl Certification Keys?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Openssl Certification Keys?

Hokhold, Mark

 

Users,

 

      I'm not exactly sure what is causing this problem, but it doesn't seem (to me anyway) that syslog-ng likes the default certificate keys that I setup.  Any help would be greatly appreciated.

 

 

      I have the following on my server and client solaris 9 systems:

 

      Syslog-ng 1.6.8

      Stunnel-4.10

      Libol-0.3.16

      Openssl-0.9.7g

 

      All compiled and installed successfully on both systems. 

 

 

Errors logged during and after startup of /etc/init.d/syslog-ng

 

 

On the server (within the messages file):

 

[ID xxxxxx daemon.notice]     5140 connected from `client IP address`:34580

[ID xxxxxx daemon.error]      SSL accept: Peer suddenly disconnected

 

 

On the client (within the syslog file):

 

Syslog-ng[2782]:  syslog-ng version 1.6.8 starting

Syslog-ng[2782]:  io.c do_write write() failed (errno 32), broken pipe

Syslog-ng[2782]:  pkt_buffer::do_flush(): Error flushing data

Syslog-ng[2782]:  Connection broken to AF_INET(127.0.0.1:514), reopening in 60 seconds

 

On the client (within the messages file):

 

Stunnel[2777]:    [ID xxxxxx daemon.notice] stunnel 4.10 on sparc-sun-solaris2.9 UCONTEXT+POLL

+IPv4 with OpenSSL 0.9.7g 11 Apr 2005

stunnel[2777]:    [ID xxxxxx daemon.notice] 125 client allowed

stunnel[2777]:    5140 connected from 127.0.0.1:33610

rsh[2824]:  [ID xxxxxx daemon.notice] connection from localhost (127.0.0.1) - bad port

 

 

Regards,

 

Mark

 

 

Reply | Threaded
Open this post in threaded view
|

Re: Openssl Certification Keys?

Andy W. Clements
It might be Stunnel-4.10.  The developer states in the change-log that
the 4.10 version is experimental and that the 4.09 is the stable
version.  I had connection problems on a FreeBSD 5.3 box with 4.10 and
the 4.09 version cleared it up and everything works.

--Andy


On Tue, 2005-06-21 at 11:04 -0400, Hokhold, Mark wrote:

>  
>
> Users,
>
>  
>
>       I'm not exactly sure what is causing this problem, but it
> doesn't seem (to me anyway) that syslog-ng likes the default
> certificate keys that I setup.  Any help would be greatly appreciated.
>
>  
>
>  
>
>       I have the following on my server and client solaris 9 systems:
>
>  
>
>       Syslog-ng 1.6.8
>
>       Stunnel-4.10
>
>       Libol-0.3.16
>
>       Openssl-0.9.7g
>
>  
>
>       All compiled and installed successfully on both systems.  
>
>  
>
>  
>
> Errors logged during and after startup of /etc/init.d/syslog-ng
>
>  
>
>  
>
> On the server (within the messages file):
>
>  
>
> [ID xxxxxx daemon.notice]     5140 connected from `client IP
> address`:34580
>
> [ID xxxxxx daemon.error]      SSL accept: Peer suddenly disconnected
>
>  
>
>  
>
> On the client (within the syslog file):
>
>  
>
> Syslog-ng[2782]:  syslog-ng version 1.6.8 starting
>
> Syslog-ng[2782]:  io.c do_write write() failed (errno 32), broken pipe
>
> Syslog-ng[2782]:  pkt_buffer::do_flush(): Error flushing data
>
> Syslog-ng[2782]:  Connection broken to AF_INET(127.0.0.1:514),
> reopening in 60 seconds
>
>  
>
> On the client (within the messages file):
>
>  
>
> Stunnel[2777]:    [ID xxxxxx daemon.notice] stunnel 4.10 on
> sparc-sun-solaris2.9 UCONTEXT+POLL
>
> +IPv4 with OpenSSL 0.9.7g 11 Apr 2005
>
> stunnel[2777]:    [ID xxxxxx daemon.notice] 125 client allowed
>
> stunnel[2777]:    5140 connected from 127.0.0.1:33610
>
> rsh[2824]:  [ID xxxxxx daemon.notice] connection from localhost
> (127.0.0.1) - bad port
>
>  
>
>  
>
> Regards,
>
>  
>
> Mark
>
>  
>
>  
>
>
--
Andy Clements
Chief Engineer
C & H Software L.L.C.
[hidden email]

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [hidden email]
Automated List Manager                           [hidden email]