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

Advanced Firewall-based blocks persist across service restarts #6

Open
EvanAnderson opened this issue Jul 13, 2012 · 10 comments
Open
Assignees
Labels
Milestone

Comments

@EvanAnderson
Copy link
Owner

This was wholly unintended functionality. I will write code to identify and remove blocks that have persisted.

It looks like an initialization routine to query the Advanced Firewall rules for rules with a known naming convention and parsing those rule names to extract the appropriate block expiration time should be sufficient.

@ghost ghost assigned EvanAnderson Jul 13, 2012
@thor795
Copy link

thor795 commented Sep 20, 2020

This was wholly unintended functionality. I will write code to identify and remove blocks that have persisted.

It looks like an initialization routine to query the Advanced Firewall rules for rules with a known naming convention and parsing those rule names to extract the appropriate block expiration time should be sufficient.

#6

@thor795
Copy link

thor795 commented Sep 20, 2020

This was wholly unintended functionality. I will write code to identify and remove blocks that have persisted.

It looks like an initialization routine to query the Advanced Firewall rules for rules with a known naming convention and parsing those rule names to extract the appropriate block expiration time should be sufficient.

@thor795
Copy link

thor795 commented Sep 20, 2020

Am trying

@thor795
Copy link

thor795 commented Sep 20, 2020

This was wholly unintended functionality. I will write code to identify and remove blocks that have persisted.

It looks like an initialization routine to query the Advanced Firewall rules for rules with a known naming convention and parsing those rule names to extract the appropriate block expiration time should be sufficient.

#6

@thor795
Copy link

thor795 commented Sep 20, 2020

This was wholly unintended functionality. I will write code to identify and remove blocks that have persisted.

It looks like an initialization routine to query the Advanced Firewall rules for rules with a known naming convention and parsing those rule names to extract the appropriate block expiration time should be sufficient.

@thor795
Copy link

thor795 commented Sep 20, 2020

This was wholly unintended functionality. I will write code to identify and remove blocks that have persisted.

It looks like an initialization routine to query the Advanced Firewall rules for rules with a known naming convention and parsing those rule names to extract the appropriate block expiration time should be sufficient.

@thor795
Copy link

thor795 commented Sep 20, 2020

Hot out side

@thor795
Copy link

thor795 commented Sep 20, 2020

This was wholly unintended functionality. I will write code to identify and remove blocks that have persisted.

It looks like an initialization routine to query the Advanced Firewall rules for rules with a known naming convention and parsing those rule names to extract the appropriate block expiration time should be sufficient.

@thor795
Copy link

thor795 commented Sep 20, 2020

Wow

@thor795
Copy link

thor795 commented Sep 20, 2020

Wow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants