× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



An client connecting to a server using SSL or TLS should "trust" the CAs
used in the Certificate.

That includes connecting to web servers, web services, SMTP servers, FTP
servers or anything else. Protocol has nothing to do with that.

Yes, you can bypass it, but that's user intervention.

Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any Cloud
Provider!

On Wed, Mar 8, 2017 at 12:35 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Also part of the basis for my "trust" question is the fact that setting up
TLS encryption between an SMTP server and a mail-relay host, the relay-host
doesn't require certificates from a certificate authority; just assign them
one created by the DCM.

Same with true for web services. Web service clients and servers don't mess
with certificate authorities. Why do browsers?



On Wed, Mar 8, 2017 at 11:28 AM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
wrote:

Agreed, but this is for internal webservices so browser warnings
shouldn't
be a problem.



-----Original Message-----
From: Nathan Andelin [mailto:nandelin@xxxxxxxxx]
Sent: Wednesday, March 08, 2017 11:45 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: DCM cert for Apache settings


I'm in Digital Certificate Manager and it's defaulting to *PGM for the
following...


Yes, the defaults work, at least as far as encryption is concerned. In
regard to assigning a self-signed certificate to the HTTP server,
browsers
will still show a message warning that the sky is falling...

--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.