You can, simply encrypt them differently. I'm just extremely paranoid on principle, so I use different media. If your encryption techniques are sound, then it doesn't really matter that a potential threat knows that the first file on the archive tape is the private key for the archive, unless you believe the rumours about AES being subporned by the NSA, but that still leaves blowfish, twofish, threefish, etc., etc., etcfish.. Or multiple encryption with different algorithms. Now that could fry someone's brain pretty quickly. Caper sauce anyone?
I am for encryption but just privacy related data and not whole database encryption, on the .NET platform Blowfish code is usually provided by product vendors because there is no native definition like Rijndael or Elliptic curve.
I like Elliptic curve encryption because even mathematicians don't understand elliptic curve math because of the complexity which means with proper management implemented most data can be protected from employers hiring the unskilled (VA employee), theft by both insiders and outsiders like laptop at the airport. When data is stolen or computer is stolen only a few people are skilled to access the data and the skilled will not aid thieves or the disgruntled employees.
I think encryption is good but only as needed, I also think website like MSN or Facebook that asks for personal data should be required to encrypt the labels because Ebay and Amazon usually ask for much less information for the base user and both sells to the public.
Kind regards,
Gift Peddie