Crash when key in snap/keys is not ascii armored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
Triaged
|
Medium
|
Chris Patterson |
Bug Description
If I put a key in snap/keys/ that is not ascii armored (ie. it's a binary file), snapcraft crashes with:
Sorry, an error occurred in Snapcraft:
'utf-8' codec can't decode byte 0x98 in position 0: invalid start byte
This is with --enable-
package-
- type: apt
url: file://
path: .
key-id: EE2C5601BCD6893
and a file called snap/keys/
Expected: a suitable error message. Actual: a crash.
Solution: gpg -a --export BFDF724C > snap/keys/
In other words, ensure that the file is actually ASCII. The workaround is easy, but there's an opportunity for better handling of this; hence this report.
Changed in snapcraft: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Chris Patterson (cjp256) |
installed: 4.5.4 (6120) 72MB classic