4 ms·

It's still revealing two levels of filename extesions - type of encryption and file format. Full filename should be simply random alphanumeric ASCII string with

It's still revealing two levels of filename extesions - type of encryption and file format. Full filename should be simply random alphanumeric ASCII string without any filename extensions, although this requires to manage and store a map of keys and filenames.

exikyut 6y ago
Hmm. A possible counterargument: filenames like dRDDrOu44Rr84vzXJv2mcr2eg83zDN43mzUQ0N4 xzrI5Ha7HJ7gK3T8XfkGqNtvc7LMQPFjSwi 5Wb1XhHeR6LxQUC8XfyX9kvvooYvrp9fnxQVvH9C jgAzjd56DGWFjcae0gw9A1LZxJEqVHW7UmkZ XrpNNAZalPp6D4mnpLvVcCE3uWkDQzthSQwK9 (as generated by for example `head -c 30 /dev/urandom | base64 | tr -d '+/='`) are extremely suspicious-looking. To me that screams "obsessively paranoid". I reckon that if I were in law enforcement, the fact that there is absolutely nothing I can infer from these filenames, combined with the obvious complexity associated with correctly maintaining something like this, would actually make me that much more interested in decrypting this information simply to take a look at it and rule it out. Which is exactly why this would be a scenario in which I _would_ want to "reuse someone else's password", if you will, and I'd theoretically go digging for common archival file patterns, and use the most common I came across.
- quchen 6y ago
  On-disk filenames should be hashes, much like .git contains lots of hash-named files. My Restic backup folders don’t show much beyond that they are Resic backup folders (if even?).
- DVk6dqsfyx5i3ii 6y ago
  > as generated by for example `head -c 30 /dev/urandom | base64 | tr -d '+/='` If you want exactly 30 alphanumeric characters you could do `tr -dc '[:alnum:]' < /dev/urandom | head -c 30`
- thebean11 6y ago
  Rclone crypt backends generate filenames like this, and are really not very difficult to set up.
- KptMarchewa 6y ago
  >I reckon that if I were in law enforcement, the fact that there is absolutely nothing I can infer from these filenames, combined with the obvious complexity associated with correctly maintaining something like this, would actually make me that much more interested in decrypting this information simply to take a look at it and rule it out. If I ever did something shady, I'd absolutely make a ton of honeypots like this.

exikyut 6y ago

Hmm. A possible counterargument: filenames like dRDDrOu44Rr84vzXJv2mcr2eg83zDN43mzUQ0N4 xzrI5Ha7HJ7gK3T8XfkGqNtvc7LMQPFjSwi 5Wb1XhHeR6LxQUC8XfyX9kvvooYvrp9fnxQVvH9C jgAzjd56DGWFjcae0gw9A1LZxJEqVHW7UmkZ XrpNNAZalPp6D4mnpLvVcCE3uWkDQzthSQwK9 (as generated by for example `head -c 30 /dev/urandom | base64 | tr -d '+/='`) are extremely suspicious-looking. To me that screams "obsessively paranoid". I reckon that if I were in law enforcement, the fact that there is absolutely nothing I can infer from these filenames, combined with the obvious complexity associated with correctly maintaining something like this, would actually make me that much more interested in decrypting this information simply to take a look at it and rule it out. Which is exactly why this would be a scenario in which I _would_ want to "reuse someone else's password", if you will, and I'd theoretically go digging for common archival file patterns, and use the most common I came across.

quchen 6y ago
On-disk filenames should be hashes, much like .git contains lots of hash-named files. My Restic backup folders don’t show much beyond that they are Resic backup folders (if even?).
DVk6dqsfyx5i3ii 6y ago
> as generated by for example `head -c 30 /dev/urandom | base64 | tr -d '+/='` If you want exactly 30 alphanumeric characters you could do `tr -dc '[:alnum:]' < /dev/urandom | head -c 30`
thebean11 6y ago
Rclone crypt backends generate filenames like this, and are really not very difficult to set up.
KptMarchewa 6y ago
>I reckon that if I were in law enforcement, the fact that there is absolutely nothing I can infer from these filenames, combined with the obvious complexity associated with correctly maintaining something like this, would actually make me that much more interested in decrypting this information simply to take a look at it and rule it out. If I ever did something shady, I'd absolutely make a ton of honeypots like this.