On 2013/12/14 18:33, S.Tindall wrote:
> On Sat, 2013-12-14 at 18:13 -0800, jdow wrote:
>> On 2013/12/14 18:05, S.Tindall wrote:
>>> On Sat, 2013-12-14 at 17:36 -0800, jdow wrote:
>>>> I kinda wondered if somebody here had an idea.
>>>>
>>>> Ah well....
>>>> {o.o}
>>>
>>> I would start with:
>>>
>>>    # restorecon -vr /etc/ddclient*
>>>    # restorecon -vr /var/cache/ddclient
>>>
>>> and then retest in permissive mode.
>>>
>>>    # setenforce 0
>>>
>>> Steve
>>>
>>
>> More or less been there done that.
>>
>> "restorecon -r /var" took a bit longer, and fixed one other unrelated
>> file. But the basic problem persisted.
>>
>> Googling indicates current Fedora "stuff" has a ddclient_t tag that does
>> not exist on my machine. So it seems the ddclient selinux policy setup
>> was skipped or missing. At least, that's my best guess.
>>
>> {^_^}
>
> For now, you could build/implement local policy for ddclient:
>
> http://wiki.centos.org/HowTos/SELinux#head-faa96b3fdd922004cdb988c1989e56191c257c01
>
> ...unless the local policy looks ridiculous. The above link also offers
> other options that you might try.
>
> Or you can hope that Daniel Walsh (Red Hat's SELinux go-to guy) reads
> this thread. :-)
>
> You can post a bug report to epel, but my experience with getting
> movement, or even acknowledgment, is poor, to be polite.
>
> Steve

I just cheated and asked him to check the bugzilla report.

Hopefully I didn't irritate him by contacting him directly about it.

{o.o}