Okay, so do you want to run this case, or would you like me to?
I take it the decrypt(1) command can't be used to decrypt archives
encrypted with des(1)?
-- Garrett
Darren J Moffat wrote:
> Garrett D'Amore wrote:
>
>> So I've posted a webrev of the cleanups:
>>
>> http://cr.opensolaris.org/~gdamore/cryptoclean/
>>
>> Nightly has not finished yet, so I'll wait for responses from protocmp
>> before I submit the RTI, but you can look at the diffs now if you want. ;-)
>>
>
> I've just remembered there is no ARC case to remove /usr/bin/des. It
> was only ever delivered as part of SUNWcry before and for Nevada that
> has been removed. For Solaris 10 udpates post U4 SUNWcry/SUNWcryr are
> now bundled so /usr/bin/des still exists on S10.
>
> In fact PSARC/2006/610 (the SUNWcry removal case) actually says
> /usr/bin/des will move to SUNWcsu - oops!
>
> I think the best thing to do there is file an EOF notification AND
> removal case. The case should request notification AND removal of
> /usr/bin/des in Nevada (point out that it is already removed from
> OpenSolaris 2008.05). Customers with data encrypted with the des(1)
> command can decrypt it with des(1) on Solaris 10 and reencrypted it with
> encrypt(1) on Solaris 10 and later.
>
>
