Jeffrey D. Smith wrote:
[...]
How about key IMPORT ? Could I keep the key in encrypted form and import
it from CKDS ?
Of course, but you can't use CPACF in that case.
I can use both: ICSF for key extract and CPACF.
BTW: I understand using CPACF as using CPACF directly OR via ICSF API.
[...]
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of R.S.
Sent: Sunday, September 10, 2006 11:35 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ICSF with CPACF (was RE: Encrypting tape drives... anyone
considering field encryption?)
Jeffrey D
Jeffrey D. Smith wrote:
[...]
I dare to disagree. ICSF's CKDS is ready to use key container. The keys
are encrypted using master key.
Wrong. The CPACF services offered by ICSF require CLEAR KEYS. They are
not encrypted by the master key. There are new key form keywords for
clear keys, CLRDES
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of R.S.
Sent: Thursday, September 07, 2006 1:22 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ICSF with CPACF (was RE: Encrypting tape drives... anyone
considering field encryption?)
Jeffrey D
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Altmark
/snip/
So, why did IBM update ICSF to support clear keys in the CKDS and
its address space? Because IBM is marketing its own CPACF solution
that requires clear keys. As long
Jeffrey D. Smith wrote:
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Alan Altmark
/snip/
So, why did IBM update ICSF to support clear keys in the CKDS and
its address space? Because IBM is marketing its own CPACF solution
that
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of R.S.
Sent: Wednesday, September 06, 2006 9:04 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ICSF with CPACF (was RE: Encrypting tape drives... anyone
considering field encryption?)
Jeffrey D
7 matches
Mail list logo
