Introduce mutt policy
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest posting 2/23 patches 0 repliesNew
- v3 posting 1/23 patches 0 repliesSuperseded
- v23 patches 0 repliesSuperseded
Earlier versions · 1
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v1 | 3 patches | 0 replies | Superseded |
Patches in v3 posting 2/2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | Initial policy for the mutt e-mail clientmutt.fc mutt.if mutt.te | +169 | 0 replies | |
| 2/3 | Allow gpg to read/write mutt e-mail files (for signing)gpg.te | +4 | 0 replies | |
| 3/3 | Allow users and staff to use muttpolicy/ policy/ | +8 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [refpolicy] [PATCH v3 0/3] Introduce mutt policy
Please find in the following e-mails an initial policy for the mutt application (terminal e-mail client). The set of mails contains:
- the mutt definition (.te, .if, .fc)
- adding mutt_role to unprivuser and staff
- update gpg.te to grant it rw access to mutt's tmp files
With respect to the previous (v2) patchset, this has coding style fixes, using userdom_user_tmp_file and removes a test rule that was forgotten earlier.
Wkr,
Sven Vermeulen