Commit 6301d32
authored
fix: NanoTDF secure key from debug logging and iv conflict risk (#208)
This change is motivated from the CodeQL result:
https://github.com/opentdf/java-sdk/security/code-scanning/1
Although that use of a static IV is deliberate, it helped highlight that
we should ensure that there is no reuse of the IV when encrypting the
data.
In addition it was found that there were two places the key was logged,
due to the sensitivity of the key this has been removed.1 parent b4f95e6 commit 6301d32
1 file changed
+5
-5
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
88 | 88 | | |
89 | 89 | | |
90 | 90 | | |
91 | | - | |
92 | 91 | | |
93 | 92 | | |
94 | 93 | | |
| |||
135 | 134 | | |
136 | 135 | | |
137 | 136 | | |
138 | | - | |
139 | | - | |
140 | | - | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
| 140 | + | |
| 141 | + | |
141 | 142 | | |
142 | 143 | | |
143 | 144 | | |
| |||
173 | 174 | | |
174 | 175 | | |
175 | 176 | | |
176 | | - | |
177 | 177 | | |
178 | 178 | | |
179 | 179 | | |
| |||
0 commit comments