WebView::LogMessageSecurityLevel cast is broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Oxide |
Triaged
|
High
|
Unassigned |
Bug Description
The log level transmitted through Oxide isn't strongly typed, and it's cast to LogMessageSecur
The cast currently works like this:
-1 (logging:
0 (logging::LOG_INFO) -> LogSeverityInfo
1 (logging:
2 (logging:
3 (logging:
No valid logging level casts to LogSeverityFatal.
This cast is unsafe anyway - we should only ever be casting like this if we have appropriate static_asserts to catch breakage like this.
Obviously, LogSeverityErro
Changed in oxide: | |
importance: | Undecided → High |
status: | New → Triaged |