evilsocket / evilsocket/opensnitch
[Bug Report] Rule expiry is not honored after suspend and resume
- 主要言語
- Python
- スター
- 14.1k
- フォーク
- 665
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
### 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:
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- linux, python
- 領域
- networking, security
- issue の種類
- バグ
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 活発さ
- 活発
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 68/100