Re: decoder memory-management question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Richard Levitte <levitte@xxxxxxxxxxx> writes:

> For all I know, a provider could just as well choose to place the key in
> an internal cache and pass the cache index in an "data" OSSL_PARAM
> (OSSL_OBJECT_PARAM_DATA), and have the keymgmt "load" function pick up
> that cache index through the reference argument.

Small detail, a cache index like that would still passed with
OSSL_OBJECT_PARAM_REFERENCE, as it's still, well, a reference, just not
a direct address to the key data.

Cheers,
Richard

-- 
Richard Levitte         levitte@xxxxxxxxxxx
OpenSSL Project         http://www.openssl.org/~levitte/



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux