New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vFeed has gone commercial... #127
Comments
@toolswatch What would be the preferred approach for CVE-Search? |
Hi, |
Decompressing is not an issue. It's more the question of, "does every user of CVE-Search need an account, or do we make one generic account?" |
Every user must open an account. Every usage of the database is tied to an account. This model will be enhanced later to become API Key. |
@adulau I assume we should change vFeed to a plug-in as well then, so that users that don't want to create an account, don't have to? |
Hello,
It seems that vFeed has gone commercial: http://www.vfeed.io. There's still a community feed, but you have to register.
I now get the following error when updating cve-search:
The text was updated successfully, but these errors were encountered: