Skip to content
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

Open
lvets opened this issue Aug 31, 2016 · 5 comments
Open

vFeed has gone commercial... #127

lvets opened this issue Aug 31, 2016 · 5 comments

Comments

@lvets
Copy link

lvets commented Aug 31, 2016

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:

...
Starting vfeed
Cannot open url http://www.toolswatch.org/vfeed/vfeed.db.tgz. Bad URL or not connected to the internet?
vfeed has 79987 elements (0 update)
...
@PidgeyL
Copy link
Owner

PidgeyL commented Aug 31, 2016

@toolswatch What would be the preferred approach for CVE-Search?

@toolswatch
Copy link

Hi,
In fact, there are 3 different plans. Since CVE-search is not commercial and public, it falls under the Community Plan (see here http://www.vfeed.io/pricing/) . So, you can still register and download it. Once there is a new available db release, you will get notified via email with a direct link to the download. The only hassle (as for now) is that you have to decompress the DB yourself.

@PidgeyL
Copy link
Owner

PidgeyL commented Aug 31, 2016

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?"

@toolswatch
Copy link

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.
I need as well to control those who are using and embedding the database within their commercial software (and i got tons of them. Making money on my back !!).

@PidgeyL
Copy link
Owner

PidgeyL commented Aug 31, 2016

@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?

PidgeyL pushed a commit that referenced this issue Apr 16, 2017
Python requirements >= 3.3
PidgeyL pushed a commit that referenced this issue Apr 16, 2017
Plug-in manager fixes, updates etc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants