Re: newbie Q: "Stacked" public key algorithm
- From: Steffen Köhler <steffen@xxxxxxxxxxx>
- Date: Thu, 14 May 2009 07:12:57 +0200
I've also thought about something like a watermark, but the problem is that
the original message would be send only once to the company itself and then
distributed internally, so the sender himself can't neither add a personal
watermark nor use e.g. the public keys of the employees itself for
encryption, as he just don't know them at that moment.
But as more I'm thniking about, I feel there's really no other way as to set
up a central encryption authority in the company who does personal
encryption for the different employees with their personal keys...
Skybuck Flying wrote:
Won't work.
Alice can simply decrypt the company secret, and then give it to somebody
else.
Any company employee could have done that.
If you want to know who leaked information than normally some secret
information is added which uniquely identifies each copy that was given
out.
For example a watermark in a picture or so... each copy of the picture
will have a secret code in it... like a bar code ! ;)
Bye,
Skybuck.
.
- Follow-Ups:
- Re: newbie Q: "Stacked" public key algorithm
- From: Skybuck Flying
- Re: newbie Q: "Stacked" public key algorithm
- References:
- newbie Q: "Stacked" public key algorithm
- From: Steffen Köhler
- Re: newbie Q: "Stacked" public key algorithm
- From: Skybuck Flying
- newbie Q: "Stacked" public key algorithm
- Prev by Date: Re: newbie Q: "Stacked" public key algorithm
- Next by Date: Re: newbie Q: "Stacked" public key algorithm
- Previous by thread: Re: newbie Q: "Stacked" public key algorithm
- Next by thread: Re: newbie Q: "Stacked" public key algorithm
- Index(es):
Relevant Pages
|