mcphail/mythicbeastsddns
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Compare commits

base: mcphail:4774c70c25805ff0e939793a621499e497d803a8
Branches Tags
mcphail:master
mcphail:v0.3
mcphail:v0.2
mcphail:v0.1
..
compare: mcphail:b84283d7b28eaf895802289f51e5ad717eca7b21
Branches Tags
mcphail:master
mcphail:v0.3
mcphail:v0.2
mcphail:v0.1

No commits in common. "4774c70c25805ff0e939793a621499e497d803a8" and "b84283d7b28eaf895802289f51e5ad717eca7b21" have entirely different histories.
4774c70c25 ... b84283d7b2

2 changed files with 6 additions and 1 deletions
Show Stats Expand all files Collapse all files

4
snap/hooks/install
View File

@ -3,4 +3,6 @@
set -e set -e
cp $SNAP/default.conf $SNAP_DATA/config cp $SNAP/default.conf $SNAP_DATA/config
chmod 600 $SNAP_DATA/config # The config file should not be world readable, but the snap user can't read it
# either if it is chmodded. How to solve this?
#chmod 600 $SNAP_DATA/config

3
snap/snapcraft.yaml
View File

@ -8,6 +8,9 @@ description: |
ipv4hostname and ipv6hostname using the `snap set` command as detailed at ipv4hostname and ipv6hostname using the `snap set` command as detailed at
https://docs.snapcraft.io/reference/snap-command#set . Activate the updater by https://docs.snapcraft.io/reference/snap-command#set . Activate the updater by
setting the updateipv4 and/or updateipv6 keys to "yes". setting the updateipv4 and/or updateipv6 keys to "yes".
.
BEWARE - passwords are stored in world-readable plain text. Until I can find a
way around this problem do not use this snap in production.
grade: stable grade: stable
confinement: strict confinement: strict
architectures: architectures: