Error when missing a seccomp entry is confusing
Bug #1468446 reported by
Sergio Schvezov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Snappy | Status tracked in Trunk | |||||
| 15.04 |
Fix Released
|
Undecided
|
Sergio Schvezov | |||
| Trunk |
Fix Released
|
Undecided
|
Sergio Schvezov | |||
Bug Description
The error reported when package.yaml misses a seccomp entry when doing a security definition override is confusing,
The cause for this is that the policy override is checked for existence but then there is no check to see if seccomp is different than an empty string causing an open to fail against a directory.
Related branches
lp:~sergiusens/snappy/seccomp
- John Lenton (community): Approve
-
Diff: 46 lines (+14/-0)3 files modifiedsnappy/errors.go (+2/-0)
snappy/security.go (+5/-0)
snappy/security_test.go (+7/-0)
lp:~sergiusens/snappy/seccompError
- Ricardo Salveti (community): Approve
-
Diff: 46 lines (+14/-0)3 files modifiedsnappy/errors.go (+3/-0)
snappy/security.go (+4/-0)
snappy/security_test.go (+7/-0)
- Snappy Developers: Pending requested
-
Diff: 1765 lines (+1354/-8) (has conflicts)20 files modifiedcmd/snappy/cmd_internal_unpack.go (+4/-0)
cmd/snappy/cmd_internal_unpack_test.go (+20/-0)
cmd/snappy/cmd_rollback.go (+9/-0)
cmd/snappy/cmd_set.go (+14/-0)
cmd/snappy/main.go (+4/-0)
etc/grub.d/09_snappy.OTHER (+441/-0)
helpers/helpers.go (+170/-8)
helpers/helpers_test.go (+104/-0)
oauth/oauth_test.go (+72/-0)
partition/bootloader_uboot.go (+104/-0)
partition/bootloader_uboot_test.go (+37/-0)
partition/partition.go (+20/-0)
snappy/click.go (+258/-0)
snappy/errors.go (+23/-0)
snappy/security.go (+7/-0)
snappy/snapp.go (+21/-0)
snappy/snapp_test.go (+19/-0)
snappy/systemimage.go (+7/-0)
systemd/systemd.go (+14/-0)
systemd/systemd_test.go (+6/-0)
To post a comment you must log in.
