Private keys should be locked away and treated like the company's crown jewels. 
If you have their private key it is likely many other sites also have. 

That renders their site completely untrustworthy. I would not send anything 
confidential or, arguably, anything at all to that site.

On the other hand, their public key is exactly what it says, public, and no 
risk.

Mike Wawiorko 

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Joel M Ivey
Sent: 22 August 2019 13:57
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: vendor distributes their private key


This mail originated from outside our organisation - ji...@cio.sc.gov

A vendor has an ftps server for us to connect to from a batch job on zos.  
Similar setups with vendors have required the vendor to provide their server's 
public cert chain for import into RACF.   This vendor insists on providing not 
just their server public cert chain but also their private key.  

First, they provided a password-protected p12 file, describing it as containing 
the "root, intermediate, and private certs".  I requested their public 
certificate chain only, they sent me a DER file -- with both the server cert 
and its private key.  I have asked them to elaborate on their need to 
distribute their private key to me, their response has essentially been, that's 
the way we do it. 

I'm not comfortable accepting anyone's private key.   There has been no mention 
of "client authentication", and I'm still not sure I'd be comfortable with that 
config, either. 

Help me understand two things: 1) what I'm missing as to why any vendor would 
require me to install their private key on my side when installing the public 
cert on my side should suffice as in many other instances, and 2) arguments 
for/against client authentication (not password authentication, but client) in 
case that is why they're sending me their private key.

Joel

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to