Re: Encrypted configuration file?
- From: "Ed Weir \(ComCast\)" <Anon@xxxxxxxx>
- Date: Fri, 28 Apr 2006 13:28:54 -0700
"Mike Amling" <nospam@xxxxxxxxxx> wrote in message
news:QUs4g.757$E84.394@xxxxxxxxxxxxxxxxxxxx
| Kristian Gjøsteen wrote:
| > mike3 <mike4ty4@xxxxxxxxx> wrote:
| >
| >>1. For authentication, upon saving out the config, we attach an MAC
| >>generated with a user-supplied password, which also locks the
| >>configuration program. [...]
| >>
| >>2. For obscurity, we encrypt the config with a key stored in another
| >>file somewhere else on the drive, [...]
| >>
| >>How good is this system, given the purpose of it?
| >
| >
| > The obvious objection is that if someone can tamper with the
configuration
| > file, why can't they tamper with the program? If they can tamper with
| > the program, then everything is trivially lost.
| >
| > However, if you have an obscure sitation where the adversary cannot
| > tamper with the program, but can tamper with the configuration file,
| > the MAC trick will work. (Passwords are a problem, it would be better
| > to use something else, but it has to be stored securely. That may or
| > may not be difficult.)
|
| When you say the MAC trick will work, I wonder how the attacker is
| detected if she surreptitiously installs a previously valid
| configuration file? Is the user-supplied password changed with each
| change to the file?
|
| --Mike Amling
If you couldn't install a previously valid file, then how could you manage
fault-tolerance? Here's an idea:
1.) Arrange the layout of the file to start with am IV (could be the CRC32
of the entire (compressed data section) package)
2.) Compress the data
3.) Add a MAC followed by the compressed data image (IV+MAC+CDATA)
4.) Encrypt the file with a key internally derived at runtime from the
machine, user, disk ID, etc. via one-way hash
5.) Store the file in more than one place
6.) Code sign the application
There's no such thing as a perfect security scheme, but this would increase
the difficulty a bit for an attacker.
- Ed.
.
- References:
- Encrypted configuration file?
- From: mike3
- Re: Encrypted configuration file?
- From: Kristian Gjøsteen
- Re: Encrypted configuration file?
- From: Mike Amling
- Encrypted configuration file?
- Prev by Date: Re: Looking for EXPTIME-algorithm
- Next by Date: Semi-OT: "The Smithy Code"
- Previous by thread: Re: Encrypted configuration file?
- Next by thread: Re: Encrypted configuration file?
- Index(es):
Relevant Pages
|
|