Changes between Version 1 and Version 2 of MalwareRepositoryDiscussion
- Timestamp:
- Nov 18, 2010 2:29:27 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MalwareRepositoryDiscussion
v1 v2 2 2 3 3 '''Needs attention:''' 4 * When Steve finds out how large the repo is, update the storage section5 * Someone investigate encrypted loopback images and expand that section6 4 * Policy issues needs more work 7 5 … … 29 27 === Storage === 30 28 31 Where/how we store it depends on how large it is. Steve is looking into this.29 The archive is 60 GB (in two 30 GB archives). We will receive approximately 1 GB per day in updates. In light of the size, we will store it on scratch. 32 30 33 * Loopback encrypted file system on users:/share, read only 34 * Encryption options 35 * Shared password 36 * Revocation (is this necessary) 37 * OS ID with strict access controls 38 * Is it possible to limit the projects this is exported to? 31 It will be exported using SMB in a password-protected share. 39 32 40 33 == Policy Issues == … … 45 38 == Miscellaneous == 46 39 47 Updates will probably be done via HTTPS with a client certificate. This depends on the GA guys.40 Updates occur over SSH. We need to provide GA tech with a key. 48 41 49 42 How will we annotate the experiment file to let the testbed know this needs special treatment (i.e., read-only mounts, copy encryption key/token to box)?