Openvas distributed architecture , master slave setup with common postgress database

[harshalgithub]

==========================

@immauss Sir,

If Possible, Please check below architecture diagram, Also Request you to find below kind of setup for MultiContainer ( mc ) build so it will be kind of Master-Slave ( Master will be Administrator GUI of GVM and Slave will be remote scanner only which is reachable via SSH connections) architecture,

https://securecompliance.gitbook.io/projects/gvm_image

https://github.com/Secure-Compliance-Solutions-LLC/GVM-Docker[](https://user-images.githubusercontent.com/9278569/148571575-dcf82388-886a-467a-b4e0-cc66bda883ea.png)

image

Will it be possible to make above kind of setup for your "mc" build, single Docker file/docker compose file.

==========================

[immauss]

I've looked at this before, but not gotten that far with it.
In my current implementation of the multiple container build, I'm using a shared volume for the sockets. Greenbone does not yet give an option for TCP communications from gvmd to postgres, which is why there is the ssh forwarding in the Securecompliance containers.
I've also been a bit swamped lately, so not as much time to work on this as I would like.

[harshalgithub]

Hi @immauss ,

Will it be possible for exposing these available ports [ GSA Web Interface (8080:9392) , 22/tcp for SSH, 9390/tcp GVM API Client, 5432/tcp PGSQL Client ] in your multi-container build, then this multi-container build will be more portable and scalable.

Please check feasibility in latest migration with pg13

[immauss]

So ... I was hoping that GB would get close to this with their upcoming container implementation by adding some TCP connection options for postgresl <-> gvmd ... however, they seem to have chosen the same method I'm using which is a shared volume to hold the sockets. I'm not a fan of all the extra ssh connections to get this to work. Mainly because it seems like a lot of work and I just haven't had the time to put into it. I'm also not sure there is a huge use case for it. Most everyone I know is primarily interested in the single container option.

That said ... I'm pretty sure you could still make this work using my container and some fancy docker-compose options to add anything addition and setup some things differently. I'm going to leave this open as a reminder for something I might try to do in the future, but right now, I just don't have the bandwidth.

-Scott

[immauss]

So GB has recently answered this still possible, and I have the directions on.
I'll start working on it soon, but it will likely be an option available to supporters.
I'll keep you posted.

[harshalgithub]

Hi @immauss , Is there any update on requested architecture enhancements ?

Thanks.

[immauss]

Yes I’ve managed to get it working, but have not fully tested it yet. I’m expecting to have some time in the next weeks to test and document and hope to make it available in early January.

…

-Scott G.E. Scott Knauss ***@***.***

On Dec 22, 2023 at 21:54 +0100, harshalgithub ***@***.***>, wrote: Hi @immauss , Is there any update on requested architecture enhancements ? Thanks. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[harshalgithub]

Hi Scott, I was researching over internet about UNIX SOCKET communications forwarding to TCP ports, and found "SOCAT" tool which can able to forward "UNIX Sockets" to "TCP Ports" I was trying that in multiport containers docker-compose file given by GB here https://greenbone.github.io/docs/latest/22.4/container/index.html#docker-compose-file Below services I have added extra in docker compose, to forward sockets to port, but not able to manage to get it working on TCP communication.

…

------------------------------------------------------------------------------------------ socat: image: alpine/socat command: "TCP-LISTEN:6400,fork UNIX-CONNECT:/run/gvmd" depends_on: - gvmd socat: image: alpine/socat command: "TCP-LISTEN:6401,fork UNIX-CONNECT:/run/ospd" depends_on: - gvmd - ospd-openvas ------------------------------------------------------------------------------------------ [docker-compose_yml.txt](https://github.com/immauss/openvas/files/13811197/docker-compose_yml.txt) I have added docker-compose file here for reference. You might get more idea about how to make this work, as you have more work experience on this. I am still researching, if I get any luck, I will share it here. On Sat, Dec 23, 2023 at 7:02 PM GE Scott Knauss ***@***.***> wrote:

Yes I’ve managed to get it working, but have not fully tested it yet. I’m expecting to have some time in the next weeks to test and document and hope to make it available in early January. -Scott G.E. Scott Knauss ***@***.*** On Dec 22, 2023 at 21:54 +0100, harshalgithub ***@***.***>, wrote: > Hi @immauss , Is there any update on requested architecture enhancements ? > Thanks. > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you were mentioned.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub <#109 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACGZI2PL6IHFRFGSZB2KPG3YK3MN3AVCNFSM5SN7FFNKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBWHAZDSNJWGE3A> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[immauss]

It's actually easier than that.

The container will be run as a remote.

The remote is added as a another scanner to the Master.

You can then configure scan to run from the remote scanner.

It's a documented feature .... Well, it's not documented well.

I have it working, but need to write docs and some more scripts to make setup easier.

The tricky part, which isn't that tricky ...
is getting the certs from the master to the remote.

I've also not been able to do any testing with it yet either. I got side tracked updating the base image and resolving a few bugs.

[harshalgithub]

Hi Scott, Any update on distributed setup with All open ports in TCP protocol?

…

On Wed, Jan 3, 2024 at 3:57 AM GE Scott Knauss ***@***.***> wrote: It's actually easier than that. The container will be run as a remote. The remote is added as a another scanner to the Master. You can then configure scan to run from the remote scanner. It's a documented feature .... Well, it's not documented well. I have it working, but need to write docs and some more scripts to make setup easier. The tricky part, which isn't that tricky ... is getting the certs from the master to the remote. I've also not been able to do any testing with it yet either. I got side tracked updating the base image and resolving a few bugs. — Reply to this email directly, view it on GitHub <#109 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACGZI2KPELCU4H7SPOPAM6TYMSCT3AVCNFSM5SN7FFNKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBXGQ3DGOJVHAZQ> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>