snappy install --allow-unauthenticated changes ownership of snap
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Snappy |
High
|
Unassigned | ||
Bug Description
snappy install --allow-
Eg:
$ ls -l /tmp
total 12240
-rwxr-xr-x 1 ubuntu ubuntu 12498600 Mar 30 20:04 snappy
-rw-rw-r-- 1 ubuntu ubuntu 31422 Mar 30 20:04 test-snap.
$ sudo snappy install --allow-
Installing /tmp/test-
2015/03/30 20:05:15 Signature check failed, but installing anyway as requested
snappy package not found ########### what is this?
$ ls -l /tmp
total 12240
-rwxr-xr-x 1 ubuntu ubuntu 12498600 Mar 30 20:04 snappy
-rw-rw-r-- 1 clickpkg clickpkg 31422 Mar 30 20:04 test-snap.
Note that test-snap.
Related branches
- Michael Vogt: Approve on 2015-04-14
-
Diff: 264 lines (+74/-38)6 files modifiedclickdeb/deb.go (+35/-17)
clickdeb/deb_test.go (+15/-10)
cmd/snappy/cmd_internal_unpack.go (+8/-6)
snappy/build.go (+6/-1)
snappy/click.go (+7/-3)
snappy/click_test.go (+3/-1)
| Changed in snappy-ubuntu: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| James Hunt (jamesodhunt) wrote : | #1 |
| James Hunt (jamesodhunt) wrote : | #2 |
The attached is sufficient to fix the problem. However, I'd like to know the original reason for chowning the snap. Is it simply an oversight, or maybe it was added to ensure that local .snap's that are root:root 0640 install successfully? If the latter, the attached patch is insufficient.
| John Lenton (chipaca) wrote : Re: [Bug 1438420] Re: snappy install --allow-unauthenticated changes ownership of snap | #3 |
why keep the loop at all?
On 9 April 2015 at 14:48, James Hunt <email address hidden> wrote:
> The attached is sufficient to fix the problem. However, I'd like to know
> the original reason for chowning the snap. Is it simply an oversight, or
> maybe it was added to ensure that local .snap's that are root:root 0640
> install successfully? If the latter, the attached patch is insufficient.
>
> ** Patch added: "bug-1438420.patch"
> https:/
>
> --
> You received this bug notification because you are a member of Snappy
> Developers, which is subscribed to snappy-ubuntu.
> https:/
>
> Title:
> snappy install --allow-
>
> To manage notifications about this bug go to:
> https:/
| James Hunt (jamesodhunt) wrote : | #4 |
Sure - this isn't a MP, just a "proof-of-concept" until we understand how the bug was introduced :-)
| John Lenton (chipaca) wrote : | #5 |
While we figure out how it was introduced (hint: there are no tests for this), I've pushed an MP to fix it.
| Changed in snappy-ubuntu: | |
| status: | Triaged → Fix Released |
| affects: | snappy-ubuntu → snappy |


Note that --allow- unauthenticated is not required to see this behaviour.