P1315 secure_clear / memset_explicit

[jensmaurer]

P1315R1 secure_val: a secure-clear-on-move type (Miguel Ojeda)

Other papers related to abstract machine semantics:

• N4534 Data-Invariant Functions (revision 3)
• P0928 Mitigating Spectre v1 Attacks in C++ P0928 Mitigating Spectre v1 Attacks in C++ #725
• P1382 volatile_load<T> and volatile_store<T> P1382 volatile_load<T> and volatile_store<T> #167

[jensmaurer]

Ville in http://lists.isocpp.org/lib-ext/2019/02/10157.php: Optimization barriers of any sort are EWG territory.

[jfbastien]

Ryan McDougall volunteered to present in Kona, the author will be present at one of the upcoming European meetings.

[jensmaurer]

Discussion on lib-ext: http://lists.isocpp.org/lib-ext/2019/01/10033.php

[brycelelbach]

@jfbastien Please send this back to LEWGI when you are done with it.

[jfbastien]

Remove all cache related things from the proposal.
SF F N A SA
3 1 3 0 0
Remove encrypting at rest from the proposal.
SF F N A SA
4 1 1 1 0
(A vote: encryption is a novel thing about the proposal)
Want secure_clear to write indeterminate values (as opposed to memset_s).
SF F N A SA
4 1 2 0 0
Want to work with WG14 on secure_clear (e.g. salvage memset_s from Annex K).
SF F N A SA
2 3 2 0 0
We want something along the lines of secure_val (with compiler support).
SF F N A SA
0 0 2 2 3