Are there instructions for configuring the this package to run against the Update API with a persistent database? It would appear doable after looking at safebrowsing.go file but as is the current endpoints seem to only interact with Lookup API.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
Hi Dylan,The package on Github actually implements its own Lookup API on top of an implementation of the Update API. It persists the database to a path defined in the config in safebrowser.go: https://github.com/google/safebrowsing/blob/master/safebrowser.go#L198Let me know if that makes sense!Thanks,Alex
On Tue, Nov 1, 2016 at 2:54 PM Dylan Warnock <warnoc...@gmail.com> wrote:
Are there instructions for configuring the this package to run against the Update API with a persistent database? It would appear doable after looking at safebrowsing.go file but as is the current endpoints seem to only interact with Lookup API.--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
Is it just going to write the blacklist to a file on the host machine?
On Tuesday, November 1, 2016 at 7:37:30 PM UTC-5, Dylan Warnock wrote:
Hey Alex,
Does that mean it saves the results to a database as they are gathered from the LookUp api? Or does it create a db of hash prefixes as specified in the Update API docs? Would the file referenced at https://github.com/google/safebrowsing/blob/master/safebrowser.go#L198 be similar to rails database.yml file? I'm not super familiar go.Thanks,
Dylan
On Tuesday, November 1, 2016 at 4:58:06 PM UTC-5, Alex Wozniak wrote:
Hi Dylan,The package on Github actually implements its own Lookup API on top of an implementation of the Update API. It persists the database to a path defined in the config in safebrowser.go: https://github.com/google/safebrowsing/blob/master/safebrowser.go#L198Let me know if that makes sense!Thanks,Alex
On Tue, Nov 1, 2016 at 2:54 PM Dylan Warnock <warnoc...@gmail.com> wrote:
Are there instructions for configuring the this package to run against the Update API with a persistent database? It would appear doable after looking at safebrowsing.go file but as is the current endpoints seem to only interact with Lookup API.--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
Hi Dylan,It creates a database of hash prefixes using the Update API. The database is stored in a file as shown here: https://github.com/google/safebrowsing/blob/c2df0f33af31470035c6adf857e60670d582374c/database.go#L296. It's basically the gob encoded hash prefixes in gzipped format.Hopefully that helps!Alex
On Tue, Nov 1, 2016 at 6:08 PM Dylan Warnock <warnoc...@gmail.com> wrote:
Is it just going to write the blacklist to a file on the host machine?
On Tuesday, November 1, 2016 at 7:37:30 PM UTC-5, Dylan Warnock wrote:
Hey Alex,
Does that mean it saves the results to a database as they are gathered from the LookUp api? Or does it create a db of hash prefixes as specified in the Update API docs? Would the file referenced at https://github.com/google/safebrowsing/blob/master/safebrowser.go#L198 be similar to rails database.yml file? I'm not super familiar go.Thanks,
Dylan
On Tuesday, November 1, 2016 at 4:58:06 PM UTC-5, Alex Wozniak wrote:
Hi Dylan,The package on Github actually implements its own Lookup API on top of an implementation of the Update API. It persists the database to a path defined in the config in safebrowser.go: https://github.com/google/safebrowsing/blob/master/safebrowser.go#L198Let me know if that makes sense!Thanks,Alex
On Tue, Nov 1, 2016 at 2:54 PM Dylan Warnock <warnoc...@gmail.com> wrote:
Are there instructions for configuring the this package to run against the Update API with a persistent database? It would appear doable after looking at safebrowsing.go file but as is the current endpoints seem to only interact with Lookup API.--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
So I believe this is where you set the file path: https://github.com/google/safebrowsing/blob/c2df0f33af31470035c6adf857e60670d582374c/cmd/sbserver/main.go#L225 ?How do I go about setting the ThreatLists values? It appears by default phishing pages are not returned
Dylan
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
Dylan
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
Dylan
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
Dylan
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
Dylan
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
--
Why keep the prefixes in a file instead of memory? I think this is my last question.
Hi Dylan, unfortunately I don't have much experience with docker containers.
On Tue, Nov 8, 2016 at 7:08 AM Dylan Warnock <warnoc...@gmail.com> wrote:
One last question. Have you had any luck setting up this package inside of a docker container?--
On Tuesday, November 1, 2016 at 4:54:39 PM UTC-5, Dylan Warnock wrote:Are there instructions for configuring the this package to run against the Update API with a persistent database? It would appear doable after looking at safebrowsing.go file but as is the current endpoints seem to only interact with Lookup API.
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
Why keep the prefixes in a file instead of memory? I think this is my last question.
On Tuesday, November 8, 2016 at 11:37:25 AM UTC-6, Alex Wozniak wrote:Hi Dylan, unfortunately I don't have much experience with docker containers.On Tue, Nov 8, 2016 at 7:08 AM Dylan Warnock <warnoc...@gmail.com> wrote:
One last question. Have you had any luck setting up this package inside of a docker container?--
On Tuesday, November 1, 2016 at 4:54:39 PM UTC-5, Dylan Warnock wrote:Are there instructions for configuring the this package to run against the Update API with a persistent database? It would appear doable after looking at safebrowsing.go file but as is the current endpoints seem to only interact with Lookup API.
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsi...@googlegroups.com.
Hey Dylan,An in-memory store is initialized via file, if available (https://github.com/google/safebrowsing/blob/c2df0f33af31470035c6adf857e60670d582374c/database.go#L104). The hashes are also persisted to disk so the client doesn't have to do a full update on every start up.Hopefully that helps!
On Tue, Nov 8, 2016 at 12:38 PM Dylan Warnock <warnoc...@gmail.com> wrote:
Why keep the prefixes in a file instead of memory? I think this is my last question.
On Tuesday, November 8, 2016 at 11:37:25 AM UTC-6, Alex Wozniak wrote:Hi Dylan, unfortunately I don't have much experience with docker containers.On Tue, Nov 8, 2016 at 7:08 AM Dylan Warnock <warnoc...@gmail.com> wrote:
One last question. Have you had any luck setting up this package inside of a docker container?--
On Tuesday, November 1, 2016 at 4:54:39 PM UTC-5, Dylan Warnock wrote:Are there instructions for configuring the this package to run against the Update API with a persistent database? It would appear doable after looking at safebrowsing.go file but as is the current endpoints seem to only interact with Lookup API.
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
To post to this group, send email to google-safe-...@googlegroups.com.--
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
--You received this message because you are subscribed to a topic in the Google Groups "Google Safe Browsing API" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-safe-browsing-api/qBGtM6wlilw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-safe-browsing-api+unsub...@googlegroups.com.
To post to this group, send email to google-safe-browsing-api@googlegroups.com.
Visit this group at https://groups.google.com/group/google-safe-browsing-api.
For more options, visit https://groups.google.com/d/optout.