updated takedowns.md to add S3 info
This commit is contained in:
parent
7b96c46e39
commit
aedfba795e
|
@ -4,7 +4,7 @@ In cases of a DMCA notice, or other abuse yet to be determined, a file has to be
|
|||
|
||||
Files can be delisted and made inaccessible by removing their record from Redis.
|
||||
|
||||
Send share links contain the id of the file, for example `https://send.firefox.com/download/3d9d2bb9a1`
|
||||
Send share links contain the `id` of the file, for example `https://send.firefox.com/download/3d9d2bb9a1`
|
||||
|
||||
From a host with access to the Redis server run a `DEL` command with the file id.
|
||||
|
||||
|
@ -14,4 +14,6 @@ For example:
|
|||
redis-cli DEL 3d9d2bb9a1
|
||||
```
|
||||
|
||||
Other redis-cli parameters like `-h` may also be required. See [redis-cli docs](https://redis.io/topics/rediscli) for more info.
|
||||
Other redis-cli parameters like `-h` may also be required. See [redis-cli docs](https://redis.io/topics/rediscli) for more info.
|
||||
|
||||
The encrypted file resides on S3 as the same `id` under the bucket that the app was configured with as `S3_BUCKET`. The file can be managed if it has not already expired with the [AWS cli](https://docs.aws.amazon.com/cli/latest/reference/s3/index.html) or AWS web console.
|
Loading…
Reference in New Issue