From: Milan Broz <mbroz@redhat.com>
To: Aaron Lewis <aaron.lewis1989@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] OT: Just for fun , outputing a sound as access granted or denied
Date: Mon, 30 Aug 2010 09:52:42 +0200 [thread overview]
Message-ID: <4C7B634A.60302@redhat.com> (raw)
In-Reply-To: <4C7B091A.3060906@gmail.com>
On 08/30/2010 03:27 AM, Aaron Lewis wrote:
> I did a small modification , make cryptsetup funny , these code is not
> secure as i didn't verify changes on ogg123 & sound files.
This is some kind of "find 5 security problems" cartoon? :-)
Seriously, please do not post such things here, cryptsetup runs with
root privileges and you introduced nice "backdoor" here...
(This reminds me http://xkcd.com/327/ :-)
Anyway, there are also exit codes, so you can do this using simple shell
script so it is also completely wrong approach, sorry.
Milan
next prev parent reply other threads:[~2010-08-30 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 1:27 [dm-crypt] OT: Just for fun , outputing a sound as access granted or denied Aaron Lewis
2010-08-30 6:55 ` Heinz Diehl
2010-08-30 10:20 ` Aaron Lewis
2010-08-30 7:52 ` Milan Broz [this message]
2010-08-30 10:18 ` Aaron Lewis
2010-08-30 10:33 ` Milan Broz
2010-09-01 6:14 ` [dm-crypt] [SOLVE] " Aaron Lewis
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=4C7B634A.60302@redhat.com \
--to=mbroz@redhat.com \
--cc=aaron.lewis1989@gmail.com \
--cc=dm-crypt@saout.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox