[
https://issues.apache.org/jira/browse/TS-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070234#comment-13070234
]
John Plevyak commented on TS-866:
---------------------------------
Sorry for the delay. I am looking at this patch. It needs a little bit of
work:
1) it should be built on remove instead of read (it can still share internal
states with using the stack mechanism)
2) it should interlock writes from the aggregation buffer if they would overlap
these writes
3) it needs to support clustering
These are not huge changes, but they will require a bit of work. There are
other features which need to touch this code as well, so I'll poke around.
> Need way to clear contents of a cache entry
> -------------------------------------------
>
> Key: TS-866
> URL: https://issues.apache.org/jira/browse/TS-866
> Project: Traffic Server
> Issue Type: New Feature
> Components: Cache
> Affects Versions: 3.0.0
> Reporter: William Bardwell
> Priority: Minor
> Fix For: 3.1.0
>
> Attachments: cache_erase.diff
>
>
> I needed a way to clear a cache entry off of disk, not just forget about it.
> The worry was about if you got content on a server that was illegal or a
> privacy violation of some sort, we wanted a way to be able to tell customers
> that after this step there was no way that TS could serve the content again.
> The normal cache remove just clears the directory entry, but theoretically a
> bug could allow that data out in some way. This was not intended to prevent
> forensic analysis of the hardware being able to recover the data. And bugs
> in low level drivers or the kernel could theoretically allow data to survive
> due to block remapping or mis-management of disk caches.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
