-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Enhancement suggestion: TLS support and authenticated mail #1564
Comments
Awesome, @rseichter . I think a lot of people would be happy for the feature. |
@ddpbsd : Sorry to curb your enthusiasm, but I filed this issue as an enhancement suggestion only. I have only recently started looking into OSSEC, and currently have no plans to implement TLS support myself. I'd regret if I inadvertently fooled people. As for using a local smtpd: I maintain machines that don't have an MTA for policy reasons. In other cases, I'd like to use the |
Weird, I thought all unixy systems came with an smtpd, and have for a while. |
I wrote "don't have an MTA for policy reasons". 😉 A dedicated database server, to name just one example, does not need to send or receive mail, so not installing an MTA (or any other software not required for the server's purpose) is a common security measure. |
We can agree to disagree. I won't muddle this issue anymore. |
@ddpbsd - Are you able to give me more information on your statement that "using a sendmail binary is supposed to work, but it seems to be undocumented"? I'm not familiar enough with C to be able to go into the source and figure out how to get this to work. My servers are configured with nullmailer and mailx which forwards email to a SaaS-based email provider. So if OSSEC supported Username/Password for SMTP, I'd be good. Or, if it supported injection directly to /usr/bin/mail (which I am using nullmailer to proxy to the SaaS provider) then I would also be good. You seem to suggest that the second option might actually work but there are some hidden, undocumented config settings I'd need? |
@DrLongGhost https://github.com/ossec/ossec-hids/blob/master/src/os_maild/sendmail.c#L59 |
@ddpbsd - Thanks for the info. I'd thought that might be how it works. I tried it and when I change On the plus side, I did realize that I can relatively easily push the alert logs to CloudWatch on AWS and generate alerts there, so that's likely my path forward. I would prefer if the more robust email options described in this feature request existed, but at least I can get OSSEC working for me in the meantime. Thanks for your help! |
@DrLongGhost There is more information in pull request #689 |
@ddpbsd - Thanks for that link. I actually got email injection working! I ended up having to fix several issues:
This let me inject into the nullmailer queue and nullmailer then takes the email and forwards it on to my email SaaS provider (via, I believe, authenticated, secure SMTP). Thanks again for the links! |
Back to the original topic, I'd like to stress that I'd really appreciate that feature! I think, running a local mail server (or something similar) as a relay or whatever is somewhat annoying and maybe could be considered as outdated. It is so much more convenient to configure one "real" mail server with everything you need, set-up an internal account on that mail server for sending out notification emails, and then from every machine which needs to send emails, authenticate on your remote server and you are done. Way better than fiddling around on every machine with postfix, sendmail, ssmtp, several layers of relays, mailutils, and whatnot. For many ecosystems, there are ready to use libraries/tools out there. For example, for Node.js there is emailjs and there is also the nice python command line tool smtp-cli |
@cschwaderer It's on my list (despite the fact that using ansible to install opensmtpd seems like the better solution), but the list is long. What can I do to help you get started on adding these features? |
@ddpbsd Given that "Copyright (C) 2019 Trend Micro Inc." is shown in the first line of the README, would it be possible to secure financial sponsorship for adding this feature (as in some commercial entity providing me with an incentive to spend my time developing it)? |
@rseichter You'd have to talk to Trend. They basically have nothing to do with the project AFAIK. |
Superseding issue #453, which surprisingly has been open for four years:
In many environments it is a requirement these days to send email using TLS, often using port 587 (submission) instead of 25.
Once implemented, new settings should be introduced so as not to break existing configurations:
The text was updated successfully, but these errors were encountered: