[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sks-devel] SKS apocalypse mitigation
From: |
Andrew Gallagher |
Subject: |
Re: [Sks-devel] SKS apocalypse mitigation |
Date: |
Fri, 23 Mar 2018 13:05:06 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 |
On 23/03/18 11:10, Andrew Gallagher wrote:
> Another effective method that does not require an ongoing management
> process would be to blacklist all image IDs
It occurs to me that this would be more wasteful of bandwidth than
blocking objects by their hash, as the server would have to request the
object contents before deciding whether to keep it or not. This is
assuming that recon is calculated on pure hashes with no type hints (I'm
99% sure this is the case, correct me if I'm wrong).
We could minimise this by maintaining a local cache of the hashes of
already-seen image objects. This would be consulted during recon and
submission in the same way as an externally-sourced blacklist.
--
Andrew Gallagher
signature.asc
Description: OpenPGP digital signature
- [Sks-devel] SKS apocalypse mitigation, Andrew Gallagher, 2018/03/23
- Re: [Sks-devel] SKS apocalypse mitigation, Yaron Minsky, 2018/03/23
- Re: [Sks-devel] SKS apocalypse mitigation,
Andrew Gallagher <=
- Re: [Sks-devel] SKS apocalypse mitigation, Daniel Kahn Gillmor, 2018/03/23
- Re: [Sks-devel] SKS apocalypse mitigation, Kristian Fiskerstrand, 2018/03/24
- Re: [Sks-devel] SKS apocalypse mitigation, Phil Pennock, 2018/03/24
- Re: [Sks-devel] SKS apocalypse mitigation, Andrew Gallagher, 2018/03/25
- Re: [Sks-devel] SKS apocalypse mitigation, brent s., 2018/03/25
- Message not available
- Message not available
- Message not available
- Message not available
- Re: [Sks-devel] SKS apocalypse mitigation, Michael Jones, 2018/03/25
- Re: [Sks-devel] SKS apocalypse mitigation, Hendrik Visage, 2018/03/26
Re: [Sks-devel] SKS apocalypse mitigation, Alin Anton, 2018/03/24