open All Channels
seplocked EVE Information Portal
blankseplocked New Dev Blog: API Security
 
This thread is older than 90 days and has been locked due to inactivity.


 
Pages: 1 [2]

Author Topic

Ishina Fel
Caldari
Terra Incognita
Intrepid Crossing
Posted - 2010.10.25 14:45:00 - [31]
 

Edited by: Ishina Fel on 25/10/2010 14:51:09

What you guys need, is the following:

1.) A list of checkboxes for every major thing you can query via the API. One checkbox for your wallet history, one for your assets, one for your mail, one for your skillqueue, etc.

2.) A button "Generate API Key", which will produce a key that *only* grants the privileges you marked using the above checkboxes.

3.) A list of API keys you already generated, which privileges are associated with them, and when they were last used for a query.

4.) An individual "Invalidate API Key" button next to every single entry in that list.

5.) The whole thing being made part of the EVE Gate website.

And that is all you will ever need. Regardless of what capabilities you add to the API - all you need to do is provide additional checkboxes. You will never have to warn users like this that their existing full access key will suddenly grant additional privileges, because the concept of a "full" key no longer exists and even if you created a key with all boxes checked, no new features will automatically be added to it.

Users can have any number of API keys, with completely custom privileges, specifically tailored to the needs of each application and/or service you use. They can share specific info on request without compromising privacy and security. And they can render invalid a compromised key without affecting more than a single application and/or service.

I admit that such an approach is a lot more involved than what you do right now, both on the implementation side as well as on the hardware side. But once it is implemented, it will be incredibly powerful and modular; and for starters, you could have already saved the time you spent writing this blog, and used it to implement yet more new spiffy features! ugh

SGT FUNYOUN
Gallente
Posted - 2010.10.29 03:44:00 - [32]
 

Ok so if I write up a web site that people can visit and do stuff like lotteries and such, would I be able to link my wallet directly through my full API Key? That way the ISK they are transfering to me is being directly deposited into my wallet?

Xander Hunt
Minmatar
Dead Rats Tell No Tales
Posted - 2010.10.29 10:13:00 - [33]
 

Originally by: Ishina Fel
Edited by: Ishina Fel on 25/10/2010 14:51:09

What you guys need, is the following:

1.) A list of checkboxes for every major thing you can query via the API. One checkbox for your wallet history, one for your assets, one for your mail, one for your skillqueue, etc.

2.) A button "Generate API Key", which will produce a key that *only* grants the privileges you marked using the above checkboxes.

3.) A list of API keys you already generated, which privileges are associated with them, and when they were last used for a query.

4.) An individual "Invalidate API Key" button next to every single entry in that list.

5.) The whole thing being made part of the EVE Gate website.

And that is all you will ever need. Regardless of what capabilities you add to the API - all you need to do is provide additional checkboxes. You will never have to warn users like this that their existing full access key will suddenly grant additional privileges, because the concept of a "full" key no longer exists and even if you created a key with all boxes checked, no new features will automatically be added to it.

Users can have any number of API keys, with completely custom privileges, specifically tailored to the needs of each application and/or service you use. They can share specific info on request without compromising privacy and security. And they can render invalid a compromised key without affecting more than a single application and/or service.

I admit that such an approach is a lot more involved than what you do right now, both on the implementation side as well as on the hardware side. But once it is implemented, it will be incredibly powerful and modular; and for starters, you could have already saved the time you spent writing this blog, and used it to implement yet more new spiffy features! ugh


+1 (if applicable) for this suggestion. There is going to be a bit more of a drag on the DB side of things as far as the DB validating what access is supposed to go with what key, but with proper indexes or cached data, having the XML output give what we WANT to give would be great. I would guess that the creation of two new tables would come to existence. One holding the list of "Types of Information" that is to be considered (IE: Corp data, Kill Mail, Personal Asset List, Mail, etc), and what each of these groups allow access to, and another table containing the API key itself, the relationship to the users account, and the group.

A TTL (Time To Live) on each key would also be nice, that way I can give the information I want to give for only a period of time, and not permanently.

Vaerah Vahrokha
Minmatar
Vahrokh Consulting
Posted - 2010.10.31 11:58:00 - [34]
 

I cannot believe to what I see done.

1) Privacy is paramount for many people
2) Privacy is protected by laws
3) EvE is a game where privacy matters, and a lot.


1) First you made EvE Gate information public by default and that was a nasty decision exclusively done to push EvE Gate usage up by brute force.

2) You implemented an in game mail system which is quite cool but people tend to send private information in there. Making it available with API exposes people to share whatever confidential and RL information to complete unknowns.
All it takes is for someone who is not a geek to be kindly asked for his full API by someone else (i.e. corp officer) and then everything private could be posted on Google.com home page for what it matters.

I don't recall to have seen a clearly visible and advertised warning to players with API keys "out" to stop using the in game mail to protect their confidential data.

3) Eve is the game where just hinting at casual information will cause alts to be wardecced, POSes to be found and so on.

So why didn't CCP implement features to exclude unwanted information from being divulged FIRST, instead of letting everyone with an API key to know mails of everyone but no ways to fine tune the amount of information out?


How can I audit corporations any more, now that people will downright refuse because they would be STUPID to hand a third party the key to their emails?

RockofLife
Posted - 2010.11.02 14:05:00 - [35]
 

i thank there should be 3 api keys per player
frist one just like lemited
2 one be for killmails corp data dumps
3 one be full api

Myrhial Arkenath
Ghost Festival
Naraka.
Posted - 2010.11.02 14:52:00 - [36]
 

I've written a post on my blog in response to this dev blog. The solution I propose is paragraph three and four, the rest is some analysis of the side-effects of this change. While the post focuses on the more negative side of things, I'd like to add however that I can see the good things of this change, and do like the possibilities for community developed tools this brings.

True Sight
Deep Freeze Industries
Posted - 2010.11.14 22:16:00 - [37]
 

You're making a horrible horrible mistake. Director of alliance corporations must hand over their API for important tasks like tracking huge POS networks, and for accurate killboard stats. With that same handover, you are now forcing them to give out the contents of all their mails, regardless of how private something may be.

PLEASE take this into consideration and add a new corp API, third type or SOMETHING, don't just leave it like this, its horrible.

Cory Sopapilla
Minmatar
Kiroshi Group
Posted - 2010.11.16 19:29:00 - [38]
 

I agree with the comments on a more granular security setting for the API keys rather than all or nothing.

That being said, I generated a new API key and it seems I either won the statistical lottery or the generator does only capital letters now.


Pages: 1 [2]

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only