Re: SSL and public facing web site on the i

There are 2 .crt files to install one appears to be the Certificate
for the CA and the other is the certificate for our domain.

I don't recall having to deal with 2 .crt files from a trusted authority.

I think you only need the 1 for your domain. Use DCM to import that into
the IBM i local *System store and assigned it to the IBM i HTTP server
instance you're using.

Could be the CA's intermediate cert + the domain cert.


On Wed, Apr 24, 2013 at 11:41 AM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

LOL! Now that's funny right there, Nathan! And actually makes the point I
Was going to about these auditors.



On Wed, Apr 24, 2013 at 11:27 AM, Nathan Andelin <nandelin@xxxxxxxxx>
wrote:

You need to go through a PCI audit someday.
You'll change your position very quickly :-)

Nah, PCI auditors are wimps. Try dealing with IT auditors from the DCAA.

I

did that for 5 years ;-)

Just tell them that you don't allow ODBC access to your database. That
will confuse them because that eliminates about 95% of known hacks. Then
tell them that you protect your DB with RPG. They will think you're

insane

for using rocket propelled grenades, but they'll back off ;-)

-Nathan

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

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