Safebrowsing API suddenly refusing requests

[Jon Ribbens]

In the last couple of days we've suddenly started getting refusals to requests to:

http://safebrowsing.clients.google.com/safebrowsing/gethash?client=api&apikey=...&appver=1.0&pver=2.2

with "We're sorry... but your computer or network may be sending automated queries. To protect our users,

we can't process your request right now." Obviously yes we are sending automated queries - it's an API!

We've been doing so for many years. Does anyone know why we're suddenly getting these errors?

[Jon Ribbens]

I figured deprecation might be involved, but what's surprising me is that the API actually still works most of the time, it's just some sort of faulty rate-limiting that's getting in the way, which makes it seem like this isn't the deprecation process and is maybe just a bug.

On Friday, 15 February 2019 17:05:56 UTC, Alex Wozniak wrote:

Hey Jon,

The turndown of this API was announced in January 2018 and was effectively decommissioned as of October 1, 2018: https://security.googleblog.com/2018/01/announcing-turndown-of-deprecated.html

As a registered developer of pre-v4 API, you should have also received an email announcement of the deprecation.

I'd encourage you to move over to our v4 API: https://developers.google.com/safe-browsing/

We have a Golang client on Github that would ideally make this transition easier for you: https://github.com/google/safebrowsing

Thanks,

Alex

[Pree T]

0635389152

ในวันที่ ส. 16 ก.พ. 2019 2:04 ก่อนเที่ยง Jon Ribbens <jrib...@gmail.com เขียนว่า:

--
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.

[Pree T]

0642860780

ในวันที่ ส. 16 ก.พ. 2019 10:51 หลังเที่ยง Pree T <preech...@gmail.com เขียนว่า:

[Jon Ribbens]

Ok you've convinced me, we've moved to a system using the latest API based upon the reference Go implementation... just one final problem, the IP address from which we were accessing the old API is blocked from accessing the new API! It's getting a 403 response, how do we get ourselves off the blacklist please? :-) (It's been about 40 hours since we last attempted to access the old API.)

On Tuesday, 19 February 2019 17:27:01 UTC, Alex Wozniak wrote:

Thanks Jon. I can confirm this is intentional. We actually introduced flaky performance to see if anyone was still depending on this endpoint, and subsequently help them move to the latest API!

[Ben Sanders]

I'm guessing it is an API key issue. The API key will be different than what was used in v3 APIs. Furthermore, the SB API needs to be activated for your cloud project.

 https://developers.google.com/safe-browsing/v4/get-started

[Jon Ribbens]

You were basically right. I had properly set up a new key for the v4 API but had made a typo in one of the IP addresses in the key restrictions. Looks like it's all working now, thanks!

[Jordi Ribé]

Hi Alex!
We need your help! We have the same message in the same url in safebrowser. The answer is the same.

How I can migrate to v4? we suposse that we need change some fields in Firefox, but we don't know the content of this.
We try to find information about this change/migration and, maybe,  the impact that this have.

We're very gratefully if you can help us! :)

El dimecres, 20 febrer de 2019 17:55:52 UTC+1, Alex Wozniak va escriure:

Jon, glad the migration worked out for you.

Ben, thanks for the assistance :)

--
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.

--

Alex Wozniak | SWE, Safe Browsing | aw...@google.com | 734-748-3306

[Jordi Ribé]

Hi Alex,

We are using Firefox 25. Since february 15 some url (standard js files) get hooked randomly when Firefox calls safebrowsing. I we disable safebrowsing this problems doesn't appears. We suposse that this is because the answer of safebrowsing is the same like Jon Ribbens tells. 

We read that the problem is the API version and that if we migrate to v4 it would be fixed.

What options do we have?

El divendres, 29 març de 2019 16:26:55 UTC+1, Alex Wozniak va escriure:

Hi Jordi,

Thanks for reaching out. Can you comment on how you are integrating with the service currently? Based on your comment, it sounds like you're potentially using a fork of Firefox?

Thanks,

Alex

[Jordi Ribé]

Maybe it's a solution for safebrowsing, but we have limits with applications that the end users  use. 

We ask to my colleagues monday and I keep in touch.

Thanks for your quickly answer! Have a nice weekend!!

El divendres, 29 març de 2019 16:51:59 UTC+1, Alex Wozniak va escriure:

Hi Jordi,

Your best option is to update to FF 56, which is when API v4 support first landed. Is that feasible?

[Jordi Ribé]

Hi Alex!

you tell me that FF 56 is my best option but the application needs some applets and FF 26 is the last version that supported this.

We have another options? :-)

El divendres, 29 març de 2019 16:51:59 UTC+1, Alex Wozniak va escriure:

Hi Jordi,

Your best option is to update to FF 56, which is when API v4 support first landed. Is that feasible?

--
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.