-
Notifications
You must be signed in to change notification settings - Fork 58
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
Configure firewall on host to open https port after installing CE #275
Comments
our pkgs disable IPTABLES in the host and also there is no iptables inside of the chroot |
I'm not sure that we can just disable all rules silently. For CE we only need to disable https |
disable? |
This will send entirely wrong signal to individual testers who just want to see the interface after installation. It'll send signals of not-working rather than a little security concern. So, at least 443 should be open. |
It is ridiculous to disable iptables on the host. I would say that host firewall config is up to the system admin. We should not mess with the host firewall--just document the required ports for our application. |
your call guys i think only happens on RPM for centos7 and rhel7 because of the manner that we handle the systemd unit file |
We should not disable iptables of host. We simply should add our one rule to allow port 443. |
ganesh-at-wiw commented 5 days ago
|
Thanks :) |
add a rule how? if you dont have any way to know how the customer firewall is i think we can just disable adn add notes in our doc not inside of the pkg, we cannot know every customer firewall way |
I agree. Per my previous comment, I don't think we should change the host firewall. Just make recommendations in the docs. |
also ONLY centos7 and rhel7 packages are disabling the firewall, because systemd hack that we have there but i will remove that in our next build |
@adrian-gluu Can you update our admin docs. We need to explain that admin should open 443 port after installing CE |
Honestly speaking it's not our responsibility to change firewall rules on host. I think we should check if port is closed and show admin warning about this. |
I'm closing this because this can cause more questions than expected result. It's admin responsibility to enable firewall on host if needed. |
Signed-off-by: Yuriy Movchan <Yuriy.Movchan@gmail.com>
Signed-off-by: Yuriy Movchan <Yuriy.Movchan@gmail.com>
Signed-off-by: Yuriy Movchan <Yuriy.Movchan@gmail.com>
Signed-off-by: Yuriy Movchan <Yuriy.Movchan@gmail.com>
Yuriy: is it secure to open 443 port without admin approval?
Ganesh Dutt Sharma: yes, because anyway, external firewall still needs an open port at 443.
Most of our clients are doing it.
Yuriy: I think we can do this in postinstall script. We need to give Adrian commands for each platform.
Also to inform admin we can print message to console:
"Checking if https port is open and configuring firewall rules.."
Example for Ubuntu:
sudo ufw allow https
The text was updated successfully, but these errors were encountered: