feat: ensure tracing is possible and lock down ssl ciphers #14
Merged
jon_nfc
merged 20 commits from 2022-02-19 05:25:24 +00:00
1-tracing-features
into development
Labels
Clear labels
Bug
Used in discussion about a bug in comments or commits
CVE-2023-5764
Denotes items related to the CVE
CodeReview
Used in comments (issues/MR/commits) to denote code review related items
Documentation
Documentation items
Feature
Used in discussion about a Feature in comments or commits
Lint
Used in comments (issues/MR/commits) to denote lint tasks todo, done, fixed
Privacy
Used in comments (issues/MR/commits) to denote privacy related items
Security
Used in comments (issues/MR/commits) to denote Security related items
breaking-change
label used to denote that the issue/Merge Request does/will introduce a breaking change
bug::reproducable
Given to an issue when the bug has been confirmed as re-producable. Can also be used in comments and commits.
bug::unable to reproduce
Given to an issue when the bug that is not able to be reproduced. Can also be used in comments and commits.
code review::complete
code review::not started
code review::rejected
code review::underway
difficulty::Full Development
Level 3. Difficulty representing that the task to complete must be planned and created.
difficulty::Good First Issue
Level 1. Difficulty representing that the task is very simple and with limited knowledge can be completed.
difficulty::Prior Knowledge
Level 2. Difficulty representing that the task requires some prior knowledge of either the technology or the project for task completion.
documentation::complete
Issues, Merge Requests
documentation::no change required
Issues, Merge Requests and used to denote no documentation changes required
documentation::not started
Issues, Merge Requests
documentation::stalled
Issues, Merge Requests
documentation::underway
Issues, Merge Requests
impact::0
impact::1
impact::2
impact::3
impact::4
impact::5
ops::ansible-roles
OPS project tag
ops::automation
ops::gitlab-ci
OPS project tag
ops::marcas
OPS project tag
ops::python-gitlab-management
OPS project tag
ops::website
priority::0
priority::1
priority::2
priority::3
priority::4
priority::5
stage::Ready for Development
stage::develop
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::feedback required
stage::planning
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::test
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stale
Label given to issues/merge requests that are considered stale due to no collaboration and is a mark for closure.
triage
Tag given to issues/merge requests requiring triaging by the team.
triage::not_confidential
This tag is given by the triage bot so that URLs can be added to an issue/comment. A triage policy for NFC wide should remove this label.
type::CI / CD
type::automation
This type is used to denote an automation job
type::bug
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::compliance
type::discussion
Type for Issues. Can also be used in discussion in comments.
type::documentation
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::feature
type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::invalid
label given to tickets that require no action or are deem as invalid.
type::quality assurance
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::question
Type for Issues. Can also be used in discussion in comments.
type::security
Type for Issues and Merge Requests.
type::specification
Design specification
workflow::complete
Issues, Merge Requests
workflow::not ready
workflow::not ready::blocked
workflow::not started
Issues, Merge Requests
workflow::ready to commence
Issues, Merge Requests
workflow::stalled
Label given to issues/merge requests where no work has occured in x days iaw triage policy.
workflow::underway
Issues, Merge Requests
workflow::underway::develop
Milestone
No items
No Milestone
docker-mail - v0.1.0
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: docker/docker-mail#14
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
No description provided.
Delete Branch "1-tracing-features"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
intent is to enable integration with fail2ban and to ensure the flow of email can be traced.
🔗 References
Mozilla SSL/TLS Config for software
🚧 Tasks
postfix
smtpd_sasl_security_options = noanonymous
amavis to add received header to messages comment out config line 33
dovecot logs auth success
dovecot logs auth failure
auth_verbose=yes
sieve logs auth success
sieve logs auth failure
postfix logs auth failure
postfix logs auth success
~Bug when a tag is created on dev branch, don't tag docker image as latest. tag it dev.
dovecot
verbose_ssl
dovecot has suitable and secure ssl ciphers enabled
dovecot ssl_cipher_list
dovecot ssl_cipher_suites
dovecot ssl_min_protocol
dovecot
ssl_prefer_server_ciphers=yes
changed the description
changed the description
changed the description
changed the description
changed the description
changed the description
changed the description
assigned to @jon_nfc
changed the description
added 1h 10m of time spent
changed title from feat: ensure tracing is possible {-with container service-}s to feat: ensure tracing is possible {+and lock down ssl cipher+}s
changed the description
changed the description
added 35m of time spent
added 2 commits
478336ca
- feat(dovecot): log failed authentication attempts274ade2d
- feat(dovecot): log SSL/TLS porotocol errorsCompare with previous version
marked the checklist item dovecot logs auth failure
auth_verbose=yes
as completedmarked the checklist item dovecot
verbose_ssl
as completedadded 5 commits
24f10af6
- feat(postfix): prevent anonymous users on submission7f7a259a
- fix(local_group): amavis and opendkim added to vmailfbdf6efa
- fix(file_permission): set spamd to own spamassassin folder967fd04f
- fix(bayes_learn): ensure journal is synced after scane9718c97
- fix(cron): sa-learn must run as spamd userCompare with previous version
marked the checklist item postfix
smtpd_sasl_security_options = noanonymous
as completedmarked the checklist item postfix logs auth success as completed
marked the checklist item postfix logs auth failure as completed
postfix log failure doesn't include the username. however looking at dovecot logs, you can view the username.
this should be enough to use fail2ban on the postfix logs to ban a user.
marked the checklist item dovecot logs auth success as completed
dovecot logging auth success only works on imap login. if the user logs in using postfix smtp with dovecot sasl auth, there is no success logging.
WHY?
added 2 commits
396cb15a
- feat(dovecot): Disable SSL/TLS protocol logging3741b926
- ci(docker_hub): fix rc release must be tagged 'dev'Compare with previous version
marked the checklist item ~Bug when a tag is created on dev branch, don't tag docker image as latest. tag it dev. as completed
marked the checklist item dovecot
ssl_prefer_server_ciphers=yes
as completedtask was completed some time ago
added 1 commit
2a222df7
- feat(ssl_tls): updated dovecot and postfix accepted ciphersCompare with previous version
marked the checklist item dovecot ssl_min_protocol as completed
marked the checklist item dovecot ssl_cipher_list as completed
marked the checklist item dovecot ssl_cipher_suites as completed
task marked as complete as cipher suites is not required when cipher lis is used to set min.
marked the checklist item sieve logs auth success as completed
added 1 commit
e9fb4123
- fix(dovecot): sieve extensions debug error.Compare with previous version
added 1 commit
43f6a356
- fix(sa-learn): amavis can't do bayes check if not mask 777Compare with previous version
investigate
when
autolearn=unavailable
there is a file permission error on/var/spool/spamassassin
syslog error
even when ensuring that amavis is part of
vmail
group and a file mask of770
amavis still produces the above syslog error.added 1 commit
93378dee
- fix(backup): /var/spool/postfix needs to be backed upCompare with previous version
mentioned in issue #1
added 5 commits
7ec97502
- feat(amavis): Add received header to messagef6b7bae3
- feat(amavis): move policy bank to own config filec3739c4f
- feat(amavis): Don't allow user to send spam/virus9f7ccabf
- feat(amavis): don't allow user to send banned emailCompare with previous version
added 1 commit
22a987a5
- feat(docker_container): Ensure amavis data is a volumeCompare with previous version
added 2 commits
acccf247
- fix(backup): ssl dir renamed to certse8eb6f90
- fix(backup.sh): exclude unix sockets from backupCompare with previous version
message headers now
marked the checklist item amavis to add received header to messages comment out config line 33 as completed
mentioned in issue #3
moved to issue #3
added 6h 15m of time spent
as dovecot sasl auth has been setup as a unix socket for postfix and postfix does log auth attempts. This should not present as an issue.
resolved all threads
approved this merge request
mentioned in commit
2fdd4a8411
added 44m of time spent
mentioned in commit
93378dee86
mentioned in commit
c3739c4f19
mentioned in commit
acccf24774
mentioned in commit
9f7ccabfa5
mentioned in commit
7ec9750216
mentioned in commit
e8eb6f906f
mentioned in commit
f6b7bae3eb
mentioned in commit
22a987a513