Why TDE doc says that memory encryption is supported?

[dmagda]

Nikolay,

Do we really support encryption for pages in RAM? That's what I found in
the docs:

Ignite uses JDK-provided encryption algorithms: "AES/CBC/PKCS5Padding" for
WAL records encryption and *"AES/CBC/NoPadding" for memory page encryption.*

Shouldn't we remove the highlighted from the docs?
-
Denis

[Nikolay Izhikov-2]

Hello, Denis.

Ignite doesn't encrypt memory page as long as it retains in memory.
Page encrypted when it is written to the disk.


пт, 31 мая 2019 г. в 19:39, Denis Magda <[hidden email]>:

> Nikolay,
>
> Do we really support encryption for pages in RAM? That's what I found in
> the docs:
>
> Ignite uses JDK-provided encryption algorithms: "AES/CBC/PKCS5Padding" for
> WAL records encryption and *"AES/CBC/NoPadding" for memory page
> encryption.*
>
> Shouldn't we remove the highlighted from the docs?
> -
> Denis
>

[Artem Budnikov]

Guys,

I updated the page.

-Artem

On 02.06.2019 22:20, Nikolay Izhikov wrote:

> Hello, Denis.
>
> Ignite doesn't encrypt memory page as long as it retains in memory.
> Page encrypted when it is written to the disk.
>
>
> пт, 31 мая 2019 г. в 19:39, Denis Magda <[hidden email]>:
>
>> Nikolay,
>>
>> Do we really support encryption for pages in RAM? That's what I found in
>> the docs:
>>
>> Ignite uses JDK-provided encryption algorithms: "AES/CBC/PKCS5Padding" for
>> WAL records encryption and *"AES/CBC/NoPadding" for memory page
>> encryption.*
>>
>> Shouldn't we remove the highlighted from the docs?
>> -
>> Denis
>>