|
The recent series of cryptographic APIs by Example articles are based on
the key managament APIs introduced with release V5R4. Some time ago I
wrote another series of articles covering this topic and providing the
same functionality, that were based on the APIs available in release
V5R3. You'll find links to these earlier articles at the end of the
article published yesterday, but I've also included them here:
APIs by Example: Cryptographic Services APIs, Part 1:
http://systeminetwork.com/article/apis-example-cryptographic-services-ap
is
APIs by Example: Cryptographic Services APIs, Part 2:
http://systeminetwork.com/article/apis-example-cryptographic-services-ap
is-part-2
APIs by Example: Cryptographic Services APIs, Part 3:
http://systeminetwork.com/article/apis-example-cryptographic-services-ap
is-part-3
APIs by Example: Cryptographic Services APIs, Part 4:
http://systeminetwork.com/article/apis-example-cryptographic-services-ap
is-part-4
APIs by Example: Cryptographic Services APIs, Part 5:
http://systeminetwork.com/article/apis-example-cryptographic-services-ap
is-part-5
APIs by Example: Cryptographic Services APIs, Part 6:
http://systeminetwork.com/article/apis-example-cryptographic-services-ap
is-part-6
APIs by Example: Cryptographic Services APIs, Part 7:
http://systeminetwork.com/article/apis-example-cryptographic-services-ap
is-part-7
Happy reading!
Best regards,
Carsten
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: 25. april 2008 12:44
To: Midrange Systems Technical Discussion
Subject: Re: Encrypted Data to File
Very nice...looks I have some more reading in store! :)
Question: What can be used in V5R3? Some of the key management utilities
are only available in V5R4 and higher, correct?
Thanks...
On Thu, Apr 24, 2008 at 4:25 PM, Flensburg, Carsten
<Flensburg@xxxxxxxxxx> wrote:
>
> Your assumption is correct, Michael. - Here's some more information
> on the subject that might help explain the use of a salt in this
> specific
> context: http://en.wikipedia.org/wiki/Initialization_vector
>
> As coincidence would have it, this week's programming newsletter also
> includes an article covering this topic, together with more code
> examples:
>
> http://systeminetwork.com/article/apis-example-cryptographic-key-manag
> em ent-encrypting-and-decrypting-data-using-key-hierarchy
> The article doesn't appear to be on-line yet, but it should be soon.
> A
> (free) associate membership to the System iNetwork is required to
> access the article.
>
>
> Best regards,
> Carsten
>
>
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
>
> Sent: 24. april 2008 18:37
> To: Midrange Systems Technical Discussion
> Subject: Re: Encrypted Data to File
>
>
>
> Good refs Buck...thanks.
>
> How would this be implemented in the cryptographic APIs? Would this
> be used for the Initialization Vector?
>
> On Thu, Apr 24, 2008 at 12:21 PM, Buck <kc2hiz@xxxxxxxxx> wrote:
> > Julius wrote:
> > > Carsten, could you please explain what "salt value" is.
> >
> > http://en.wikipedia.org/wiki/Salt_(cryptography)
> >
> > I've found Bruce Schneier approachable: http://www.schneier.com/
> > -- > > > 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.
>
> --
>
>
> 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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.