Bug 45825 – Consider splitting up 10_univention-firewall_start.sh

Bug 45825 - Consider splitting up 10_univention-firewall_start.sh


Summary:	Consider splitting up 10_univention-firewall_start.sh

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Firewall (univention-firewall)
Version:	UCS 4.2
Hardware:	Other Windows NT

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-12-05 21:06 CET by Michael Grandjean
Modified:	2020-07-03 20:55 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

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

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

Description Michael Grandjean

2017-12-05 21:06:34 CET

Currently we initialise iptables in 10_univention-firewall_start.sh AND define the iptables rules via UCRV security/packetfilter/...

We should split this in more files, at least two:

- 10_univention-firewall_init.sh        <- initialise iptables
- 15_univention-firewall_ucr_rules.sh   <- add rules defined in UCR

This way, it would be much easier to insert certain iptables rules in a custom script right after initialising iptables (e.g. more strict filtering or logging), but before the iptables rules defined by our packages.

Comment 1 Ingo Steuwer

2020-07-03 20:55:23 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.