Hi Marko,
Actually I have it,
However I was thinking the problem in a wrong way. In my particular case,
the fact of the private key in memory is a good reason for discard the
electronic signature, I mean, in order to have a real protection against the
data modification I need a TSA (time stamping
On 1/23/08, Luis Alberto Pérez Paz <[EMAIL PROTECTED]> wrote:
> Very interesting point of view.
> Yes, you're right about the manage key problem.
>
> The grant database access looks like a real solution.
Eh, for some reason I imagined you have have some good reason
why simple solutions are not eno
Very interesting point of view.
Yes, you're right about the manage key problem.
The grant database access looks like a real solution.
Thanks a lot for your advice.
Best Regards,
Luis Alberto Perez Paz
On Jan 23, 2008 11:20 AM, David Wall <[EMAIL PROTECTED]> wrote:
>
> > We're in a stage wher
We're in a stage where I need to implement a mechanism to prevent the
data modification.
I'm thinking on 'Digital Signatures' (maybe RSA) in each row. If
there's a modification, the signature doesn't verify.
Like all such solutions, the key (lame pun intended) is how to do you
manage the key
On 1/23/08, Luis Alberto Pérez Paz <[EMAIL PROTECTED]> wrote:
> I'm working in a project which is using postgres (great database!, I love
> it)
>
> We're in a stage where I need to implement a mechanism to prevent the data
> modification.
>
> I'm thinking on 'Digital Signatures' (maybe RSA) in each
