User contributions for EnigmaticC
Results for EnigmaticC talk block log uploads logs abuse log global account global block log
A user with 8 edits. Account created on 10 January 2023.
17 January 2023
- 15:0515:05, 17 January 2023 diff hist +510 m Talk:Protecting Memory Secrets →pithier, maybe: nice current
15 January 2023
- 23:3223:32, 15 January 2023 diff hist +2,372 m Talk:Protecting Memory Secrets →Disagree, Task is valid: rebuttal
- 02:3202:32, 15 January 2023 diff hist +116 m Talk:Protecting Memory Secrets →Disagree, Task is valid: adjust points
- 02:1902:19, 15 January 2023 diff hist +157 m Talk:Protecting Memory Secrets →Disagree, Task is valid: another couple of points
- 02:1602:16, 15 January 2023 diff hist −1 m Talk:Protecting Memory Secrets →Transient =: fix unequal heading markup
- 01:4401:44, 15 January 2023 diff hist +770 m Talk:Protecting Memory Secrets →Perhaps missing the point
13 January 2023
- 03:0903:09, 13 January 2023 diff hist +3,243 N Talk:Protecting Memory Secrets Created page with "== Draft Status == Despite the wording in some of the standards which may sound overly prescriptive, I expect the intent is not to ban the use of popular languages from use. As such I expect that the requirements will evolve. This is an attempt to step back from some of the wording to look at the risks and a broader set of options to meet the objective. This task should evoke a healthy constructive discussion. As such, I don't see this as cast in stone. == Motivation..."
- 02:1902:19, 13 January 2023 diff hist +5,708 N Protecting Memory Secrets How can your language protect in-memory secrets from eavesdropping