Re: Securing tape backup drive

[Vernon Hamberg <vhamberg@xxxxxxxxxxx>]

As a vendor that supports customers on multiple releases, it matters 
what release I refer to when giving a function in SQL or and API. Not 
everyone is on the bleeding edge you are - and the community is in 
your debt for your efforts out on that edge.

In this case, V5R3 is still supported, so it matters that 
ENCRYPT_TDES is only available on V5R4 and later.

OK - back to bed and rest from this cold.

Regards
Vern

At 07:57 AM 3/20/2007, you wrote:

> Well, V5R4's been out now for over a year and I'd like to think that most
> people could have missed their Saturday morning cartoons at least once in
> that time period and taken the time to load it.
> V5R2's end of support is coming up in April.  Several of the major
> software houses have already said to upgrade because what IBM doesn't
> support, they don't either.
> End of marketing for V5R3 has already been announced.
> http://www-304.ibm.com/jct01004c/systems/support/i/planning/upgrade/suptschedule.html
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> Vernon Hamberg <vhamberg@xxxxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 03/20/2007 09:50 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
>
> Fax to
>
> Subject
> Re: Securing tape backup drive
>
>
>
>
>
>
> Depends on the version of OS/400 - I think I was looking at the V5R3
> manual. I see the TDES function in V5R4. I forgot to say this - have
> to, with all the changes in SQL on the iSeries - new stuff all the time.
>
> Vern
>
> At 07:39 AM 3/20/2007, you wrote:
>
> >triple des is supported along with RC2.  Two different BIFs.
> >
> >Rob Berendt
> >--
> >Group Dekko Services, LLC
> >Dept 01.073
> >PO Box 2000
> >Dock 108
> >6928N 400E
> >Kendallville, IN 46755
> >http://www.dekko.com
> >
> >
> >
> >
> >
> >Vernon Hamberg <vhamberg@xxxxxxxxxxx>
> >Sent by: midrange-l-bounces@xxxxxxxxxxxx
> >03/20/2007 12:22 AM
> >Please respond to
> >Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> >
> >
> >To
> >Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> >cc
> >
> >Fax to
> >
> >Subject
> >Re: Securing tape backup drive
> >
> >
> >
> >
> >
> >
> >Roger
> >
> >I just looked at it - the encryption is RC2 - so you'd need to write
> >a UDF to get anything else - but there are lots of algorithms
> >available on iSeries.
> >
> >HTH
> >Vern
> >
> >At 10:39 AM 3/19/2007, you wrote:
> >
> > >What is the encryption that SQL uses when you have it encrypt a column?
> > >I've only heard about this and am thinking of investigating it as
> > >another step to protect the specific column of the file that already
> has
> > >heavy object security on it.
> > >
> > >Roger
> > >
> > >On 3/19/2007 9:55 AM, Jones, John (US) wrote:
> > > > Yep, our 3582 has a lock.  Beyond that pretty much every equipment
> >rack
> > > > can be configured with locking front & rear panels.  Neither the
> tape
> > > > library nor the rack locks are particularly robust but they will at
> > > > least slow down anyone intent on accessing the media/equipment.
> > > >
> > > > BTW, IANAL but if you were using a 'modern' encryption method like
> > > > AES256 I'm pretty sure the breach notification can be avoided.  IBM
> is
> > > > severely behind the times on tape (and disk for that matter)
> >encryption
> > > > support for the iSeries.
> > > >
> > > >
> > >
> > >--
> > >*** Vicker Programming and Service *** Have bits will byte ***
> > >www.vicker.com ***
> > >Pick two: [1] Fast   [2] Right   [3] Cheap
> > >
> > >--
> > >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.