Open Bug 1470288 Opened 6 years ago Updated 2 years ago

Enable SANDBOX_FAILED_LAUNCH_KEYED out on release population

Categories

(Core :: Security: Process Sandboxing, defect, P2)

defect

Tracking

()

People

(Reporter: jimm, Unassigned)

References

(Blocks 1 open bug, )

Details

Attachments

(1 file)

I'm seeing hex values here that are beyond the range of Chromium's ResultCode enum. Wondering what's going on. For example - 

https://searchfox.org/mozilla-central/source/security/sandbox/chromium/sandbox/win/src/sandbox_types.h#26

tab	20	32
tab	2e4	740
tab	b7	183
tab	12b	299
tab	80	128
tab	1f	31
tab	57	87
tab	5aa	1450
tab	8	8
tab	1e7	487
tab	5af	1455
tab	40	64
tab	2	2
tab	5	5
tab	0	0
tab	3e6	998
		0
plugin	2	2
plugin	2e4	740
plugin	7e	126
plugin	570	1392
plugin	1f	31
		0
geckomediaplugin	5	5
geckomediaplugin	4ec	1260
geckomediaplugin	15a	346
Blocks: 1395952
Flags: needinfo?(bobowencode)
That looks like the last windows error code to me.

I think the counts on the right should be able to be broken down by the chromium sandbox error code as well.
Flags: needinfo?(bobowencode)
Oh they're not counts are they, they're the decimal form of those hex values. :-)
Priority: -- → P2
Summary: Out of bounds values found in SANDBOX_FAILED_LAUNCH_KEYED → Enable SANDBOX_FAILED_LAUNCH_KEYED out on release population
Blocks: 1476811
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: