On Sat, Aug 09, 2008 at 01:20:13PM +0200, Sebastian Siewior wrote:
>
> Well, the spec says the key reload takes a lot of time so it should give
> a big boost to everything what isn't supported directly in HW.
> The padlock supports a few other modes like OFB but I doubt they are
> required since th
On Sat, Aug 30, 2008 at 09:55:00PM +1200, Michal Ludvig wrote:
>
> IIRC The first versions of VIA PadLock required the input data to be
> aligned on 16-bytes boundaries and more importantly they always
> finalised the hash. Therefore we had to collect all data before hashing
> them.
Hmm, the curr
On Sat, Aug 30, 2008 at 09:55:00PM +1200, Michal Ludvig wrote:
>
> IIRC The first versions of VIA PadLock required the input data to be
> aligned on 16-bytes boundaries and more importantly they always
> finalised the hash. Therefore we had to collect all data before hashing
> them.
Ah yes, the f
Hi Herbert,
> Can you remind me the reason why our PadLock SHA implementation
> copies things into a page before hashing it?
>
> According to the programming manual, it would seem that the state
> should be recorded in EDI after each 64-byte block so we should
> be able to use the init/update/fin
Hi Michal:
Can you remind me the reason why our PadLock SHA implementation
copies things into a page before hashing it?
According to the programming manual, it would seem that the state
should be recorded in EDI after each 64-byte block so we should
be able to use the init/update/final model, no?
