Re: SSL application question

Thanks for getting back to me Scott.

I don't know where the request is being made, I just know it isn't
making it to my application.

You can see for yourself.

First browse to http://205.144.103.214:443

then go to HTTPS://205.144.103.214.443

My application sees you when you use the first addresss and, since I
don't know you, sends back an HTML document and flags you as a
potential hacker. If you keep trying eventually you will be locked
out.

When you use the second address I don't see you at all You just get
rejected. An associate tried it with his application software which
uses SSL and he is getting a warning message that his certfificate is
not valid and it is showing him my certifificate. He can bypass the
error and then he connects to my application.

My certificate is the only one defined and it is only assigned to my
application.

Albert

On Fri, May 21, 2010 at 8:18 PM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx> wrote:

Hi Albert,

However, when a non-AS/400 without my certificate tries to connect via
SSL to my server, it is not reaching my application. The O/S is trying
to establish the SSL connection using my certificate and fails.

Can you explain that a little better?  Why would the OS be handling the
SSL for you?   What software is being used?   INETD is the only thing
that I can think of, and it doesn't do the SSL for you, you'd have to do
it yourself...  so that doesn't fit your description.

So what component of the OS is receiving your connections and trying to
establish SSL for you?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.