Sorry for the late response, and putting on my VIA hat for a second:
On Sat, Aug 30, 2008 at 09:55:00PM +1200, Michal Ludvig wrote:
> > Can you remind me the reason why our PadLock SHA implementation
> > copies things into a page before hashing it?
> >
> > According to the programming manual, i
Hi again,
On Mon, Sep 01, 2008 at 01:44:13PM +1000, Herbert Xu wrote:
> On Mon, Sep 01, 2008 at 01:32:48PM +1200, Michal Ludvig wrote:
> >
> > That's right, I confused SHA with AES in PadLock, sorry. With AES the
> > first versions required 16-byte alignment on input and output data as
> > well
On Mon, Sep 01, 2008 at 01:32:48PM +1200, Michal Ludvig wrote:
>
> That's right, I confused SHA with AES in PadLock, sorry. With AES the
> first versions required 16-byte alignment on input and output data as
> well as on the control word and there's a flag in newer PadLocks that
> allow doing A
Herbert Xu wrote:
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.
Hm
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?
