)]}'
{"specs/2023.1/approved/ephemeral-storage-encryption.rst":[{"author":{"_account_id":7166,"name":"Sylvain Bauza","email":"sbauza@redhat.com","username":"sbauza"},"change_message_id":"8cb513ec416a84501532aa0ed6fb2dacdaf0dad5","unresolved":true,"context_lines":[{"line_number":151,"context_line":"    to the virt driver implementation, underlying hypervisor and format being"},{"line_number":152,"context_line":"    used."},{"line_number":153,"context_line":""},{"line_number":154,"context_line":".. note::"},{"line_number":155,"context_line":""},{"line_number":156,"context_line":"    The ``encryption_options`` field will be unused and not exposed to end"},{"line_number":157,"context_line":"    users initially because of the security and upgrade implications around it."},{"line_number":158,"context_line":"    For the first pass, sensible defaults for the cipher algorithm, cipher"},{"line_number":159,"context_line":"    mode, and initialization vector generator algorithm will be hard-coded"},{"line_number":160,"context_line":"    instead."},{"line_number":161,"context_line":""},{"line_number":162,"context_line":"    Encryption options could be exposed to end users in the future when a"},{"line_number":163,"context_line":"    proper design which addresses security and handles all upgrade scenarios is"},{"line_number":164,"context_line":"    developed."},{"line_number":165,"context_line":""},{"line_number":166,"context_line":"Populate ephemeral encryption BlockDeviceMapping attributes during build"},{"line_number":167,"context_line":"------------------------------------------------------------------------"}],"source_content_type":"text/x-rst","patch_set":1,"id":"f8929cd9_1a418844","line":164,"range":{"start_line":154,"start_character":0,"end_line":164,"end_character":14},"updated":"2022-11-15 17:38:32.000000000","message":"fwiw, this is the only paragraph that was added for this revision on Antelope :\n[sbauza@sbauza nova-specs]$ diff specs/2023.1/approved/ephemeral-storage-encryption.rst specs/zed/approved/ephemeral-storage-encryption.rst \n154,165d153\n\u003c .. note::\n\u003c \n\u003c     The ``encryption_options`` field will be unused and not exposed to end\n\u003c     users initially because of the security and upgrade implications around it.\n\u003c     For the first pass, sensible defaults for the cipher algorithm, cipher\n\u003c     mode, and initialization vector generator algorithm will be hard-coded\n\u003c     instead.\n\u003c \n\u003c     Encryption options could be exposed to end users in the future when a\n\u003c     proper design which addresses security and handles all upgrade scenarios is\n\u003c     developed.\n\u003c \n167c155\n\u003c ------------------------------------------------------------------------\n---\n\u003e -------------------------------------------------------------------------\n183c171\n\u003c A ``COMPUTE_EPHEMERAL_ENCRYPTION`` compute compatibility trait was introduced\n---\n\u003e A ``COMPUTE_EPHEMERAL_ENCRYPTION`` compute compatibility traits was introduced\n452c440\n\u003c     melwitt\n---\n\u003e     lyarwood\n455c443\n\u003c     lyarwood\n---\n\u003e     melwitt\n542,543d529\n\u003c      - Reproposed\n\u003c    * - 2023.1 Antelope\n\n\nFWIW, I\u0027m fine with the note.","commit_id":"62d6b6280645cbddc3178b6c6904abafe2beda22"}]}