Closed Bug 511081 Opened 15 years ago Closed 14 years ago

Run safebrowsing from a local file

Categories

(Toolkit :: Safe Browsing, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: Siyivan, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6
Build Identifier: 

Consider a central server with many users logging in and using firefox. Each one will download the safebrowsing database. Moreover, if the server also runs ClamAV, it will also download and mantain another copy.
The phising/attack lists are common to all those users, yet it is present and several times, contributing to big firefox profiles (and quotas) and downloaded many times (proxys don't help here) even though all files are identical.
Discussion about the file size can be seen on bug 383031, although space is cheap, there's no reason to waste it, specially when the file will get bigger over time.

The use cases I'd like Firefox to support are:
1. The file is downloaded and updated externally (eg. freshclam). All installs point to the same read-only file to verify the urls.
2. The file is updated by one Firefox profile (eg. the admin one), the other browsers use that file as read-only.
3. Same as above but misconfigured with write access for everybody so there're concurrent updates. It should be able to still work (since it is using sqlite, it should just work).



Reproducible: Always
In summary; you want some way to cache safebrowser better/completely?
Cache in terms of security is useless. safebrowsing api consider out of date data older than 30 minute.
There is currently no read-only SQLite API in MozStorage at this time. 

As far as the "freshness guarantee" of the malware and site data this will not work within Google's terms of service for the safebrowsing service
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.