Closed sn-mm closed 4 months ago
Well ... that's new.
The last time I asked, GB would not sell a license separate from their commercial products. ( VMs and hardware)
I've never been able to even try.
So ... how did you manage to obtain a key?
Thanks, Scott
I simply asked here: https://www.greenbone.net/en/testnow/ It's a Trial, i could use it in their VM. I'm not even sure if I can buy their commercial products and use anyway a simple container for doing my activities, in different networks. If you need for the license, I can share it with you. Thanks for the help. Marco
When I get a few spare cycles, I'm going to give this a try.
Thanks, Scott
Did you decode the file you received from base64 ?
-Scott
I'm not sure since a bit of time has passed, but I remember that I created a file exactly where it was expected, and pasted it without any modification, as you would do with any other license. It worked smoothly. Marco
On Wed, Feb 14, 2024 at 9:48 AM GE Scott Knauss @.***> wrote:
Did you decode the file you received from base64 ?
-Scott
— Reply to this email directly, view it on GitHub https://github.com/immauss/openvas/issues/189#issuecomment-1943313926, or unsubscribe https://github.com/notifications/unsubscribe-auth/BAHWOXH2EJWGGXQXP4AUSVDYTR24FAVCNFSM6AAAAAAYWZCCPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBTGMYTGOJSGY . You are receiving this because you authored the thread.Message ID: @.***>
Probabaly my wonky mail client . . . . But yes. I did get it work, and it showed the full Enterprise feeds.
Might need to give it some time.
Oh! And make sure you are not starting the container with "SKIPSYNC=true" and you will either need to restart the container to kick off the sync script or run:
docker exec -it <container name> /scripts/sync.sh
-Scott
Hi Scott, this is really exciting news! I found this command really useful:
docker exec -it
Previously I had to launch each sync job manually. (I don't know if you added it recently to the docs) Thank you! Marco
On Thu, Feb 22, 2024 at 2:57 PM GE Scott Knauss @.***> wrote:
Probabaly my wonky mail client . . . . But yes. I did get it work and it showed the full Enterprise feeds.
Might need to give it some time.
Oh! and make sure you are not starting the container with "SKIPSYNC=true" and if you will either need to restart the container to kick off the synch script or run:
docker exec -it
/scripts/synch.sh -Scott
— Reply to this email directly, view it on GitHub https://github.com/immauss/openvas/issues/189#issuecomment-1959503970, or unsubscribe https://github.com/notifications/unsubscribe-auth/BAHWOXHLJC65X4EFWPT6TSTYU5FFJAVCNFSM6AAAAAAYWZCCPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJZGUYDGOJXGA . You are receiving this because you authored the thread.Message ID: @.***>
Glad that helped.
Just double checked .... It's in the docs. :)
-Scott
Hey, just for your information, distributing a trial key and sharing it on several machines at the same time is not allowed. Also distributing the content of the enterprise feed is considered a license violation.
@bjoernricks
Of course.
To be clear, I have never, nor would I ever, violate or condone the violation of Greenbone's or anyone else's license agreements through the distribution of this container or any other means. I have in fact, quite recently, had my operations here reviewed by a lawyer to ensure I was not violating any published licenses involved in the creation of this container image. This thread, as can be clearly seen, is about the feasibility of using the trial enterprise key or any key from Greenbone in this container distribution. My testing was conducted in an isolated environment, and the enterprise feed data pulled during testing have not, nor will they ever, be included in the distribution of this container or any other product from Immauss Cybersecurity.
-Scott
I didn't assume you were violating our licenses. It just wanted to be clear about our enterprise feed usage.
@bjoernricks all good. I realized the title of this particular thread could be misleading, and I just wanted to make sure anyone reading this in future understood our position on such things.
-Scott
For anyone interested, this does work with the container. However, as of 9 May 2024, it is not cost-effective unless you are scanning thousands of machines, to purchase access to the Enterprise Feeds.
Docker-compose with latest version (22.4.16) I tried putting the enterprise key in /etc/gvm/ and it was recogized.
Found Greenbone Enterprise Feed access key, trying to synchronize with Greenbone CERT data Repository ...
But seems to remain with community feeds.
Can the container work with enterprise feeds?