No padlock for Dataset with inherited encryption

HolyK

Ninja Turtle
Moderator
Joined
May 26, 2011
Messages
654
Heya!

Is it only me going into panic mode for a split of a second every time i see no padlocks near my encrypted datasets? My brain quickly realizes that it is because encryption is inherited (after my eyes are forced to check the parent/root Dataset).

The concept with the icons is just weird ...

If root dataset IS encrypted, then:
- "No icon" = Encryption inherited
- "Padlock with "X" " = Encryption explicitly disabled

If root dataset is NOT encrypted then:
- "No icon" = Dataset is NOT encrypted
- "Padlock" = Dataset is encrypted

And the most weirdo is when you combine inherited encryption with not-encrypted datasets ...
- RootDataset - Not encrypted, no padlock
-- Encrypted dataset - padlock, encrypted
---- Encrypted dataset - no padlock, encrypted (inherited)
---- Not Encrypted dataset - padlock with "X", not encrypted (inheritance explicitly disabled)
-- Not Encrypted dataset - no padlock, NOT encrypted

Uhm ... what?

I've raised NAS-115096 with suggestion to add some sort of Padlock sign for inherited encryption. In my eyes the "No icon" should be left for "undefined / not-encrypted" only.

1646215236181.png

Original screen from here. Sadly i don't have not-encrypted root-datasets to add the "no padlock" for not-encrypted datasets.
 

SMnasMAN

Contributor
Joined
Dec 2, 2018
Messages
177
i agree with your concept, and have voted for your IX bug tracker ticket. (i have read that IXsys does not even read improvement tickets until they 10x or more votes)
 
Joined
Oct 22, 2019
Messages
3,641
i agree with your concept, and have voted for your IX bug tracker ticket.
Looks like the votes got reset from the recent Jira migration? :frown:

I voted for it... again.
 
Top