Hi Olga, When a signature is made, a padding algorithm is used to fill out that data to match the size of the key. The padding algorithm will use random data to fill in, thus the different signature data. When the signature is verified, the padding is stripped off before verification.
Kent On Tue, Sep 14, 2010 at 9:13 AM, Olga Gelbart <[email protected]> wrote: > Hello, > I was wondering if anyone else got this result: I am creating a SHA-1 hash > of a file, then signing this hash using a key from Trousers' persistent > store (accessed by a UUID). I run the program as a "regular" user and get a > value for the signature. If I run exactly the same program as root, I get a > different value for the signature. The file is the same, the SHA-1 hash is > the same; I access the key by using the same UUID, but the resulting > signature is different. > Does anyone know the reason why this might be happening? > > sincerely, > Olga > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > TrouSerS-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/trousers-users > > ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ TrouSerS-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/trousers-users
