After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 785769 - Connection description files have incorect access rights
Connection description files have incorect access rights
Status: RESOLVED DUPLICATE of bug 769702
Product: NetworkManager
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-08-03 10:26 UTC by Mirek
Modified: 2017-08-04 04:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Mirek 2017-08-03 10:26:52 UTC 
When I create new connection using NewtorkManager, then the file 
will be created with 644 access rights.
But as opposite, after new start NetowrkManager ignore such connection description files, and consider only the files with 600 access rights.

So it seems, that there is somewhere inconsistency between function creating, and reading the keyfiles.
Comment 1 Beniamino Galvani 2017-08-03 15:12:37 UTC 
This sounds like bug 769702, which was fixed in NM 1.6.

Which NM version and distro do you have?

What's the output of 'getfacl /etc/NetworkManager/system-connections'?
Comment 2 Mirek 2017-08-03 16:59:34 UTC 
Distribution is gentoo, and version 1.4.4

the output of getfacl:

# owner: root
# group: root
user::rwx
group::r-x 
other::r-x 
default:user::rwx
default:group::r-x
default:other::r-x
Comment 3 Beniamino Galvani 2017-08-03 18:30:35 UTC 
(In reply to Mirek from comment #2)
> Distribution is gentoo, and version 1.4.4
> 
> the output of getfacl:
> 
> # owner: root
> # group: root
> user::rwx
> group::r-x 
> other::r-x 
> default:user::rwx
> default:group::r-x
> default:other::r-x

Then this is a duplicate of bug 769702, which is fixed since NM 1.6.

Please update to a more recent version, or, as a workaround, remove ACLs from /etc/NetworkManager/system-connections (which probably shouldn't be there in the first place).

*** This bug has been marked as a duplicate of bug 769702 ***
Comment 4 Mirek 2017-08-04 04:14:00 UTC 
Thank you.