3 ms·
Why is the government cargo-culting the scourge that is API keys? The goal of this should be for everyone to have access and lower barriers to entry, not put b
by AnthonyMouse 3y ago
Why is the government cargo-culting the scourge that is API keys?
The goal of this should be for everyone to have access and lower barriers to entry, not put bureaucracy in the way of access and de facto suppress use by open source projects because each user would need their own API key unless someone publishes one.
- gausswho 3y agoWhat makes API keys a scourge?
- scq 3y agoAPI keys are important for effective rate limiting/abuse prevention.
- beachy 3y agoIf the provider is bearing the costs (like here) then they always need some kind of authorization, or they have no way to shut off abusers or people with misbehaving clients. An API key is about the simplest possible way to achieve that, and appears to be perfectly adequate in this case. What do you suggest? SAML?
- AnthonyMouse 3y ago> If the provider is bearing the costs (like here) then they always need some kind of authorization, or they have no way to shut off abusers or people with misbehaving clients. HTTP is an "API" that has no API keys and all the public web servers in the world seem to manage this without any trouble. > What do you suggest? SAML? No authentication required by default -- it's public data. Just impose a reasonable rate limit by IP address and require registration only if someone has a legitimate reason to exceed that.
- mlhpdx 3y ago> HTTP is an "API" that has no API keys and all the public web servers in the world seem to manage this without any trouble. Um, no. That’s just not true.
- AnthonyMouse 3y agoWe're currently using a discussion forum that nobody signed up for an API key in order to make posts and you don't even need a user account in order to read. What allows them to sustain this without being destroyed by evil forces?
- thfuran 3y agoProbably either the lack of evil forces currently attempting to destroy it or cloudflare.
- AnthonyMouse 3y agoSo we've established that it isn't API keys.
- knodi123 3y ago> nobody signed up for an API key in order to make posts Yes you did. When you logged in, they gave you an API key in the form of a cookie that you include with every request. And it's run at a loss by Y Combinator, which is very, very wealthy. And even hackernews has to pay for cloudflare and mods, on top of hardware, hosting, and traffic.
- AnthonyMouse 3y ago> When you logged in, they gave you an API key in the form of a cookie that you include with every request. You can read this website (i.e. make queries against its database) without logging in. Moreover, the main thing the cookie does is not some kind of rate limiting or denial of service protection, it's assigning your username to your posts so that others can't impersonate your account. Various image boards exist that even allow you to post without logging in and they seem to be fine with it.
- fragmede 3y agoThere's a rate limiter that kicks in if you try to post or do other things as a logged in user too fast.
- beachy 3y ago> all the public web servers in the world seem to manage this without any trouble Incorrect. Most large web sites invest in DDOS protection e.g. Cloudflare. Cloudflare DDOS protection as an example is a lot more sophisticated than merely counting requests per source IP (https://developers.cloudflare.com/ddos-protection/about/how-ddos-protection-works https://developers.cloudflare.com/ddos-protection/about/how-...).
- AnthonyMouse 3y agoCloudflare is one of the ways they manage it. But API keys aren't any good for that anyway because if someone is just trying to overload your service by brute force, they can send requests regardless of whether the keys are valid and still use up all your bandwidth sending error responses or your CPU/memory opening new connections prior to validating the API keys, and to avoid that you'd still need some kind of DDoS protection. Where they actually do something is where you're doing accounting, because then if someone wants to send you a million requests, you don't block them, you just process them and send them a bill. Maybe you block them if they reach the point you don't expect them to be able to pay. But if it's a free service that anybody can sign up for as many times as they want then that doesn't do any good because the price is $0 and a rate limit per key is avoided by signing up for arbitrarily many more keys.
- maxerickson 3y agoPer IP limits don't do anything about the scenario where the API is integrated into a third party website that sees a sudden spike in popularity. At that point, the API is providing free capacity to the third party site. Maybe that is fine, but you seem to be ignoring the possibility.
- AnthonyMouse 3y agoBecause it's fine. That's what it's for, isn't it? The public, via some website, is requesting the government data their tax dollars have paid for. Which allows that website (or app) to operate with minimal resources, e.g. by a non-profit or open source project, instead of having to be a for-profit entity which needs some underhanded way to generate revenue in order to display the "free" data.
- AdieuToLogic 3y agoFrom the site: The NPS Data API is open and accessible to all developers who wish to use NPS data in their projects. From their "API Guides": Limits are placed on the number of API requests you may make using your API key. Rate limits may vary by service, but the defaults are: Hourly Limit: 1,000 requests per hour For each API key, these limits are applied across all developer.nps.gov API requests. Exceeding these limits will lead to your API key being temporarily blocked from making further requests. The block will automatically be lifted by waiting an hour. That, along with their ToS[0], hardly seems to qualify as a "cargo-culting scourge." 0 - https://www.nps.gov/aboutus/disclaimer.htm https://www.nps.gov/aboutus/disclaimer.htm
- AnthonyMouse 3y agoAPI keys were invented as a tracking device. You sign up and then they associate all your use with one person and can do things like revoke your keys if you e.g. try to compete with the company's own products. Neither of these should be relevant to public data on a government service. Rate limits are straight forward to implement per-IP address without having any other information about anyone. The sort of person willing to bypass them by using a thousand IP addresses is the same sort of person who would sign up for a thousand API keys using fake names. How are you supposed to rate limit by API key if "anyone" can get an API key? You'd need to use some means to rate limit how many API keys someone could request, which was the original problem.
- mlhpdx 3y agoPer IPv6 address? It’s very difficult (impossible?) to even make IPv4 based rate limiting work.
- AnthonyMouse 3y agoWith IPv6 you use address blocks instead of individual addresses. IP-based rate limiting is extremely effective because it bifurcates the internet into IP addresses controlled by the attacker and ones that aren't. The attacker can only issue requests at a rate of rate limit per IP address times number of IP addresses (or IPv6 blocks) they control. Then the IP addresses under their control get denied while the IP addresses not under their control, i.e. all of the other users, are unaffected. This only becomes a problem if they control on the order of millions of IP addresses, but then you're dealing with a sophisticated criminal organization and are probably screwed anyway.
- aspanu 3y agoI don't really understand your complaints about API keys, but if you did want to make an issue of something perhaps it should be that you get your API key sent to you by email, in plaintext. Not amazing, but I guess for their threat model it's generally ok.
- velcrovan 3y agoAPI keys provide a straightforward mechanism for limiting use, and for allowing clients that get lots of traction to pay for higher limits. That’s not a cargo cult, that’s just design.
- sixstringtheory 3y agoCould you show us an example of a service API that you maintain that doesn’t uses API keys?
- AnthonyMouse 3y agoRSS feeds.