snappy config lacking appropriate input validation for systemd

Bug #1499834 reported by Jamie Strandboge
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
snapd
Confirmed
High
Unassigned

Bug Description

I set the hostname via snappy config to 'snappy-1504_edge-amd64' then rebooted. On reboot I see the errors in the attached screenshot. I'm guessing the problematic character is '_' even though http://www.freedesktop.org/software/systemd/man/hostname.html states that it should be allowed.

Note, I at first changed it to snappy-15.04.edge-amd64, verified /etc/hostname was set, rebooted, and that went fine. I then changed it from snappy-15.04.edge-amd64 to snappy-1504_edge-amd64, verified /etc/hostname was set, rebooted and it failed to boot.

Revision history for this message
Jamie Strandboge (jdstrand) wrote :
Leo Arias (elopio)
Changed in snappy:
status: New → Confirmed
Revision history for this message
Michael Vogt (mvo) wrote :

The `snap config` command is not yet available but once it will become available again we will need to sanitize this input.

Changed in snappy:
importance: Undecided → High
Michael Vogt (mvo)
affects: snappy → snapd
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.