Bug 61958 – ipchains blocking https when http allowed

Bug 61958 - ipchains blocking https when http allowed

Summary:	ipchains blocking https when http allowed

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	gnome-lokkit (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	i386 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-03-26 04:26 EST by Jukka Lehti
Modified:	2014-03-16 22:26 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:	1.3.5-1
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-03-11 00:59:32 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jukka Lehti 2002-03-26 04:26:22 EST

When installing Red Hat Linux 7.2 and selecting "Medium level" firewall +
customizing firewall to allow http connections (port 80), https connections
(port 443) are still blocked. IMHO https should be allowed for users who allow
http (or at least an option provided to allow https, too).

I fixed this manually adding line

-A input -s 0/0 -d 0/0 443 -p tcp -y -j ACCEPT

to the end of file /etc/sysconfig/ipchains but probably this should be done
automatmc.

Comment 1 Michael Fulbright 2002-03-27 01:27:10 EST

We will consider this enhancement in a future release.

There is currently a field to enter arbitrary ports in so it is still possible
to enable this port through the UI.

Comment 2 Michael Fulbright 2003-04-16 14:59:03 EDT

This is a configuration decision for the lokkit program.

Comment 3 Bill Nottingham 2004-03-11 00:59:32 EST

Fixed in system-config-securitylevel-1.3.5-1.

Note You need to log in before you can comment on or make changes to this bug.