Re: I need a encryption utility that will...
From: Scott W (CantGiveMyAddressBecauseIm@work.com)
Date: 02/12/03
- Next message: Rob Slade, doting grandpa of Ryan and Trevor: "REVIEW: "The CISSP Prep Guide Gold Edition", Ronald L. Krutz/Russell Dean Vines"
- Previous message: sapurnicus: "Re: liability for unsecured systems"
- In reply to: Juha Laiho: "Re: I need a encryption utility that will..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Scott W" <CantGiveMyAddressBecauseIm@work.com> Date: Wed, 12 Feb 2003 07:15:24 -0600
Thanks, I will look into PGP.
Scot
"Juha Laiho" <Juha.Laiho@iki.fi> wrote in message
news:b2bcq6$qt0$2@ichaos.ichaos-int...
> "Scott W" <CantGiveMyAddressBecauseIm@work.com> said:
> >Let me describe what I am seeking... if anyone here knows of such a
thing,
> >please let me know. I realize I could write this app myself, but would
> >rather not if there something out there that already suits the purpose.
> ...
> >Here is what makes my requirements unique:
> >I want to be able to specify the password in advance, embedded in the
> >utility, so when they specify one or more files for inclusion, they just
> >click "Generate" and it creates a file for them to send to me. They don't
> >have to know or care about the password. I need to be able to
periodically
> >change the embedded password, which would then necessitate me resending
the
> >utility out, or maybe just a small file with a key - not sure how this
would
> >work.
>
> Everything seems to fit the definition of "public-key encryption".
> Just a fancy shell on top of any public-key crypto system, such as
> PGP.
>
> Without considering the user-interface issues you presented:
> - the sender will need to have your "public key"
> - with that the sender can encrypt information so that only the
> holder of the matching private key (i.e. you) can open the content
> - you will periodically provide new copies of your public key
> - you keep copies of all the previous private keys, so you can still
> decrypt all content signed by "obsoleted" public keys, too
> - it's also possible for the senders to create their own private keys,
> providing you with a stronger way of authenticating the senders
>
> >Since the people I distribute this to could not use it for any other
> >purpose than to send files to me, [...]
>
> Here is where a "commodity" public key system doesn't match your
> specification. And still I think it might be cheaper for you to
> use such a commodity system than to have your private implementation
> custom-built for you.
> --
> Wolf a.k.a. Juha Laiho Espoo, Finland
> (GC 3.0) GIT d- s+: a C++ ULSH++++$ P++@ L+++ E- W+$@ N++ !K w !O !M V
> PS(+) PE Y+ PGP(+) t- 5 !X R !tv b+ !DI D G e+ h---- r+++ y++++
> "...cancel my subscription to the resurrection!" (Jim Morrison)
- Next message: Rob Slade, doting grandpa of Ryan and Trevor: "REVIEW: "The CISSP Prep Guide Gold Edition", Ronald L. Krutz/Russell Dean Vines"
- Previous message: sapurnicus: "Re: liability for unsecured systems"
- In reply to: Juha Laiho: "Re: I need a encryption utility that will..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
