in reply to Re^6: IO::Socket::SSL problem
in thread IO::Socket::SSL problem

:) surely that client has a debug/trace/verbose option?

Replies are listed 'Best First'.
Re^8: IO::Socket::SSL problem
by balle (Novice) on Sep 27, 2012 at 10:54 UTC
    Which client? Its oldschool telnet and even in tcpdump I can only see the tcp handshake and this error message being send from the server afterwards.

      Which client?

      The one you're using :) whatever that is

      For example telnet

      debug Toggles socket level debugging (useful only to the super-user). The initial value for this toggle is FALSE. authdebug Turns on debugging information for the authenti- cation code.

      Crank up whatever trace/verbose/debug option you can find until you get output you can correlate to what you get from IO::Socket::SSL debug3

      Common source of error is using the wrong port

        Tcpdump cannot show me more information so debug mode of telnet also cannot ;)

        The port is the right one, but maybe I cannot talk standard SSL to it, because even stunnel complains about "unknown protocol" :-/