PeerCache improves privacy by truncating file hashes in its log files. This reduces the amount of identifiable information stored while still allowing basic cache statistics and diagnostics.
PeerCache improves privacy by truncating file hashes in its log files. This reduces the amount of identifiable information stored while still allowing basic cache statistics and diagnostics.
No. PeerCache does not store file metadata such as filenames, descriptions, or content details. Files are identified only by their file hash values.
Yes. Logging can be disabled by setting the following option in the PeerCache.ini configuration file:
AccessLog=/dev/nullDisabling logging may prevent certain reporting and statistics features from functioning correctly, including:
No. Cached content is never included in Peer-to-Peer search results. Files stored in the cache can only be accessed when the same content is already available through the P2P network.
PeerCache logging is similar to a standard Squid cache log. Each request recorded in the access.log file may include:
datetime | request duration | request status | bytes transferred | GET http://10.0.0.1/
No. Starting with PeerCache version 1.2, full client IP addresses are no longer stored in logs.
Statistics are provided only in aggregated form, allowing administrators to measure information such as the number of unique users accessing the cache during a given period without identifying individual users.
PeerCache log files are typically retained for 10 days.