Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Encryption\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Encryption\s*$/: 23 ]

Total 23 documents matching your query.

1. Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Tue, 3 Oct 2006 16:17:40 -0700; Hi, I have a client that is trying to encrypt their data on the client side and then pass the data to the TSM server for backups. I have been looking into what configuration are needed. They have set; /lists/html/ADSM-L/2006-10/msg00013.html (8,974 bytes)
2. Re: Encryption (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Tue, 3 Oct 2006 19:43:38 -0400; Roger - Have your client personnel crack open the Windows Backup-Archive User's Guide manual, which describes all that they need to do. A vital piece is the Include.Encrypt specification of the data; /lists/html/ADSM-L/2006-10/msg00014.html (8,515 bytes)
3. Re: Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Tue, 3 Oct 2006 19:42:26 -0700; Richard, I know there is a part in windows where you can encrypt the files yourself, but there is also an "ENCRYPTIONType AES128" line to add to the dsm.opt file also that will do this, Right? Thanks; /lists/html/ADSM-L/2006-10/msg00017.html (9,040 bytes)
4. Re: Encryption (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Wed, 4 Oct 2006 08:43:40 -0400; Roger - Yes, that 5.3 client option is one of the elements which will achieve the sought encryption. Be sure to get the full picture of all the elements from the Windows client manual. Richard Sims R; /lists/html/ADSM-L/2006-10/msg00023.html (9,461 bytes)
5. Re: Encryption (score: 1): Author: Roger Silva <rogsilva AT STANFORD DOT EDU>; Date: Wed, 4 Oct 2006 09:02:29 -0700; Thanks Richard. Yes, that 5.3 client option is one of the elements which will achieve the sought encryption. Be sure to get the full picture of all the elements from the Windows client manual. Richar; /lists/html/ADSM-L/2006-10/msg00033.html (9,738 bytes)
6. Encryption (score: 1): Author: William Sherrill <billsh AT US.IBM DOT COM>; Date: Wed, 15 Jun 2005 08:47:00 -0400; I have some questions for anyone using encryption. How are people maintaining the encryption keys for recoveries, specifically disaster recovery (not stored in the TSM.PWD)? What effects does it have; /lists/html/ADSM-L/2005-06/msg00318.html (8,388 bytes)
7. Re: Encryption (score: 1): Author: Alexei Kojenov <kojenova AT US.IBM DOT COM>; Date: Wed, 15 Jun 2005 09:38:30 -0700; Hello Bill, One needs to either remember the encryption key password(s) or store them in a safe place. Once the password is lost, there is no way to restore the encrypted data. Generally, it will slo; /lists/html/ADSM-L/2005-06/msg00328.html (9,349 bytes)
8. Re: Encryption (score: 1): Author: Thomas Denier <Thomas.Denier AT MAIL.TJU DOT EDU>; Date: Wed, 15 Jun 2005 13:41:44 -0400; We ran some tests of TSM encryption when we thought it might be required for regulatory compliance. We concluded that encryption was not required before we got as far as implementing a key storage s; /lists/html/ADSM-L/2005-06/msg00332.html (9,765 bytes)
9. Encryption (score: 1): Author: "Jones, Eric J" <eric.j.jones AT LMCO DOT COM>; Date: Tue, 24 May 2005 21:32:53 -0400; Good Evening. Running TSM 5.2.2 on AIX 5.2 Clients are a mix of Solaris 7,8,9 AIX 4.2, AIX 5.2, Windows NT, Windows 2000 and Windows 2003 most running TSM 5.2.2. I've been reading the forums and was; /lists/html/ADSM-L/2005-05/msg00583.html (8,995 bytes)
10. Re: Encryption (score: 1): Author: Henrik Wahlstedt <shwl AT STATOIL DOT COM>; Date: Wed, 25 May 2005 09:36:29 +0200; Hi Eric, Yes TSM can encrypt your data, both in 5.2 (des56) and 5.3 (aes 128). You add the lines in a client optionset or in dsm.opt. INCLUDE.ENCRYPT "c:\...\*" ENCRYPTKEY PROMPT or SAVE. Check the c; /lists/html/ADSM-L/2005-05/msg00586.html (9,585 bytes)
11. Re: Encryption (score: 1): Author: "Johnson, Milton" <milton.johnson AT CITIGROUP DOT COM>; Date: Wed, 25 May 2005 11:55:07 -0400; My concerns with TSM based encryption are: 1) Since encrypted data does not compress well the TSM clients must do both the compression and encryption. 2) TSM compression and encryption can be a perfo; /lists/html/ADSM-L/2005-05/msg00616.html (11,215 bytes)
12. Encryption (score: 1): Author: J D Gable <josh.gable AT EDS DOT COM>; Date: Mon, 21 Oct 2002 16:13:03 -0500; Does anybody have any evidence/research as to what kind of additional overhead encryption puts on a client when processing a backup (CPU, Memory, etc.)? I am running some tests myself, but the number; /lists/html/ADSM-L/2002-10/msg00952.html (8,887 bytes)
13. Re: Encryption (score: 1): Author: "Cook, Dwight E" <DWIGHT.E.COOK AT SAIC DOT COM>; Date: Tue, 22 Oct 2002 05:34:04 -0700; Been a while and I'd have to double check but... You might not want to use compression if you use encryption... I believe it encrypts first then tries to compress and encrypted data doesn't compress; /lists/html/ADSM-L/2002-10/msg00959.html (9,075 bytes)
14. Re: Encryption (score: 1): Author: Jim Smith <smithjp AT US.IBM DOT COM>; Date: Tue, 22 Oct 2002 09:37:53 -0600; Dwight, You are correct that compressed data would not encrypt well, since TSM uses a compression algorithm that works well with redundant data (and compression kills redundancy) - but, the TSM b/a c; /lists/html/ADSM-L/2002-10/msg00998.html (9,819 bytes)
15. Encryption (score: 1): Author: "Paul L. Bradshaw" <pbradshaw AT VNET.IBM DOT COM>; Date: Mon, 7 Nov 1994 10:05:38 PST; We are looking at encryption, but one of the key stumbling blocks is in the area of key management. Questions: 1. Should ADSM allow for keys to be changed on a time basis? 2. Should ADSM administrato; /lists/html/ADSM-L/1994-11/msg00030.html (9,277 bytes)
16. Re: Encryption (score: 1): Author: Nick Laflamme <NLAFLAMM AT VMA.CC.ND DOT EDU>; Date: Mon, 7 Nov 1994 14:31:54 EST; I would think so! You're going to need cooperation from both the users and the administrators unless you're storing the data in encrypted format (see below). I would see a system where the user sets; /lists/html/ADSM-L/1994-11/msg00031.html (11,191 bytes)
17. Re: Encryption (score: 1): Author: Paul Zarnowski <VKM AT CORNELLC.CIT.CORNELL DOT EDU>; Date: Mon, 7 Nov 1994 21:35:47 EST; Paul, No. In answer to the above two questions, I would argue that the data encryption keys should be stored on the ADSM server, encrypted with the user's password. When the user's password is change; /lists/html/ADSM-L/1994-11/msg00032.html (12,476 bytes)
18. Encryption (score: 1): Author: "Paul L. Bradshaw" <pbradshaw AT VNET.IBM DOT COM>; Date: Tue, 8 Nov 1994 08:49:24 PST; Good data and suggestions...keep it coming. Please be sure to indicate your business/environment so we can try to correlate the requirements with the industry (education, banking, insurance, high-tec; /lists/html/ADSM-L/1994-11/msg00035.html (8,484 bytes)
19. Encryption (score: 1): Author: Mickey Bennett <mbennet AT MBENNET.DOA.STATE.LA DOT US>; Date: Wed, 9 Nov 1994 13:58:25 CST; Not a requirement Control at Admin level is sufficient Prompting O.K. for restore (only for *encrypted* data) It is not *necessary* for ADSM to encrypt data when stored (the physical media *is* prot; /lists/html/ADSM-L/1994-11/msg00038.html (9,771 bytes)
20. Re: Encryption (score: 1): Author: "Keith A. Crabb" <KEITH AT UHUPVM1.UH DOT EDU>; Date: Wed, 9 Nov 1994 14:36:25 CST; I don't see this as a requirement. Just admin control would be sufficient. Ugh, only for data that has been encrypted. I'm not wild about changing keys, we don't even expire passwords though (althoug; /lists/html/ADSM-L/1994-11/msg00039.html (10,065 bytes)

Current List: 1 - 20
Page: [1] [2]