From: Mads Martin Joergensen <mmj@mmj.dk>
To: mlmmj@mlmmj.org
Subject: Security audit
Date: Sun, 01 May 2005 10:54:41 +0000 [thread overview]
Message-ID: <20050501105441.GI38323@mmj.dk> (raw)
Hey list,
Sebastian Krahmer (http://www.novell.com/linux/security/team.html)
recently did a security audit of mlmmj, and didn't find any issues.
That doesn't necessarily mean that there isn't any, but at least the
code have been looked by different eyes with security in mind.
--
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?"
-- A. P. J.
next reply other threads:[~2005-05-01 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-01 10:54 Mads Martin Joergensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-22 18:01 Security Audit Taylor Hornby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050501105441.GI38323@mmj.dk \
--to=mmj@mmj.dk \
--cc=mlmmj@mlmmj.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.