On Wed, 2021-09-15 at 15:38 -0700, vince wrote: > On Wednesday, September 15, 2021 at 3:31:01 PM UTC-7 > jonatha...@gmail.com wrote: > > I presume that if weewx creates new files under .../weewx/ then > > they will inherit correct permissions (or possibly weewx won't > > create any such files after its initialization). Also it doesn't > > look like there's any worry about security. > > > It's not weewx, it's selinux, and you can't presume anything about > selinux. It has 'its' ideas about where things are located and how > they got there, so if you do anything other than that selinux will > block you when in enforcement mode, since it thinks you're actively > trying to get around the security setup on the system. It's actually > a feature. > > The better way to work around things is to put things where selinux > expects it, or just run the chcon command in the linked article to > set the security context of the files weewx writes to.
I did in fact run: # chcon -R -t httpd_sys_content_t weewx but didn't make clear that I had done so. The question was to make sure that the chcon would fix things permanently, or is there any chance that weewx will create future files with a wrong security context. -- Thanks very much for your help - Jonathan Ryshpan <jonr...@pacbell.net> And God fulfills himself in many ways Lest one good custom should corrupt the world. -- Tennyson -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e436b33a5e46c25fb53766957b42ba3e459e1900.camel%40pacbell.net.
