Skip to content

Conversation

@oleschwen
Copy link
Collaborator

@oleschwen oleschwen commented Sep 30, 2025

Test setup for connecting to VPN from inside the MediSwarm containers rather than on the host, including a setup for locally running an openvpn server. Postponed, as we do not need this for now.
The branch contains credentials used for the test setup, warnings about this can be ignored.

…tainer) and pulling it from there.

This required additional changes:
* changed name of Docker image for testing to localhost:5000/…, which should also prevent accidental push
* parse name of Docker image from swarm project description yml rather than use hard-coded name
* extended "delete old image versions" script accordingly
…PN from within the container.

Currently requires manual steps (at least building the VPN container) for the test to succeed and will need to be adapted for productive VPN use.

* install packages for OpenVPN and debugging in ODELIA container
* changed docker run arguments for swarm nodes to be able to open VPN connection from within (currently as root, to be reconsidered)
* setup for building and VPN container, creating OpenVPN certificates (one fixed set committed), running VPN container
* swarm server now named testserver.local, but this name only needs to be reachable in the containers
* VPN container is assumed to be reachable on host at 172.17.0.1 from other containers
* changed ports for nvflare server to avoid interference with productive servers
* noted TODOs
* added integration test checking that and documenting how this works
@oleschwen oleschwen linked an issue Sep 30, 2025 that may be closed by this pull request
@gitguardian
Copy link

gitguardian bot commented Sep 30, 2025

⚠️ GitGuardian has uncovered 5 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
21197632 Triggered Generic Private Key 25e7322 tests/local_vpn/client_configs/admin@test.odelia_client.ovpn View secret
21197633 Triggered Generic Private Key 25e7322 tests/local_vpn/client_configs/client_B_client.ovpn View secret
21197634 Triggered Generic Private Key 25e7322 tests/local_vpn/client_configs/client_A_client.ovpn View secret
21197635 Triggered Generic Private Key 25e7322 tests/local_vpn/client_configs/testserver.local_client.ovpn View secret
21197636 Triggered Generic Private Key 25e7322 tests/local_vpn/server_config/server.key View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@oleschwen oleschwen force-pushed the dev-122-vpn-from-within-container branch from 255ad91 to 0d1f098 Compare September 30, 2025 12:46
@oleschwen oleschwen changed the title WIP VPN from within container POSTPONED: VPN from within container Oct 13, 2025
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

Successfully merging this pull request may close these issues.

Test VPN connection from within container

2 participants