evilsocket / evilsocket/opensnitch
[Bug Report] Rule expiry is not honored after suspend and resume
- Lingua principale
- Python
- Stelle
- 14.1k
- Fork
- 665
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
### Describe the bug:
After a rule is created with the duration of X number of hours, and the device goes on standby, the rule remains in effect if the device is resumed after a longer period of time than X.
Include the following information:
- OpenSnitch version: 1.8.0
- OS: Fedora
- OS version: 43
- Window Manager: MATE
- Kernel version: Linux localhost 6.19.14-200.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Apr 23 17:34:07 UTC 2026 x86_64 GNU/Linux
### To Reproduce:
Steps to reproduce the behavior:
1. Access whatever address that will throw the rule creation request.
2. Set the rule to expire after X many hours.
3. Standby the device.
4. Resume the device after longer than X many hours
5. See that the rule is still in effect
### Post error logs:
### Expected behavior (optional):
The rule expiry should be checked and applied correctly
### Screenshots:
### Additional context:
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Reproduce the issue with the listed steps, using the opensnitchd daemon and checking /var/log/opensnitchd.log for relevant behavior. Start by tracing how rule expiry is handled across standby and resume; done means a rule created for X hours is no longer effective after resuming beyond X hours.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- linux, python
- Ambito
- networking, security
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Attiva
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 68/100