News Feed
- DrugHub has agreed to fully refund all users who lost money in the SuperMarket exit scam.
- Retro Market has gone offline. Circumstances of the closure unknown.
- SuperMarket has closed following an exit scam by one of the admins.
- The admin of Incognito Market, Pharoah, has been arrested by the FBI several months after exit scamming.
- Silk Road
- darknet markets list
- Popular P2P exchange LocalMonero has announced it is closing.
One possibility is to create an encrypted 7Z archive, with a simple script, stored in a convenient place, that way no need to navigate to the specific directory each time (plus it should be much more compact).
notes:
* A slightly more elaborate script could automatically set the archive's name with the current time, I don't know how to do that on Linux.
* A long password made of simple words is better than a shorter password made of gibberish, see: xkcd.com/936/
* Other options could improve the compression ratio, for instance -mx=7 -md=128m to set the compression strength to "7" and the dictionary size to 128MB.
* -mhe enables header encryption (the filenames can not be displayed until the correct password is inputted)
* -mtc=on and -mta=on enable the storage of creation and access timestamps, respectively; by default only the modification timestamps are stored.
* -ms=off disables the "solid" compression mode. By default 7-Zip compresses in "solid" mode which can considerably improve the compression ratio if there are many files with similar contents, but makes the archive very vulnerable to corruption, as a single corrupted byte makes the whole contents located beyond that byte unreadable, whereas in "non solid" mode only the file containing that corrupted byte will be unreadable. So if the difference in compressed size is less than ~10% (with or without "-ms=off"), or if you generally favor robustness over compacity when it comes to backups, I would advise to disable "solid" compression. For "solid" compression to be optimal, the dictionary size should be set to a value that is slightly higher than the total size of the uncompressed files (for instance, if the total size is 180MB, set the dictionary size to the available value immediately higher which is -md=192m), but if set too high the compression can fail because the available RAM is insufficient.
What are the other sensitive files?
According to the reference other files include these data: