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

Add packet filtering to restrict the accessibility of the web interface to certain IPs/subnets #3

Open
2 tasks done
blint opened this issue Sep 10, 2018 · 0 comments

Comments

@blint
Copy link
Owner

blint commented Sep 10, 2018

Prerequisites

  • Can you reproduce the problem?
  • Did you perform a cursory search to see if your bug or enhancement is already reported?

Description

It is not possible to apply packet filtering rules on the management interfaces (web and ssh) to restrict which subnets/IP addresses they should be accessible from.

Steps to Reproduce

  1. provision a MiCADO master
  2. reach port tcp/22 and tcp/443 (if not configured otherwise) from any IP address

Expected behavior: [What you expected to happen]
The user should be able to configure the accessibility of these interfaces through security-cred.yml by following the steps described in the documentation.

Actual behavior: [What actually happened, including error logs]
No such behaviour can be configured.

Versions

develop

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

1 participant