"'DRC' via TurboVNC User Discussion/Support"
<[email protected]> writes:

> Can you confirm whether my recommendation below fixes the issue on
> your machine?

I tried it just now, and it seems to work nicely, thanks!

/Joakim

>
> DRC
>
> On 2/28/22 3:14 PM, DRC wrote:
>> This is apparently necessary on RHEL/CentOS 7 and 8 as well.  Under
>> prior RHEL/CentOS releases, the initrc_t context was unconfined, but
>> apparently that changed.  On my Fedora 34 installation, it is also
>> necessary, so I'm not sure how you were able to make the TurboVNC
>> Server init.d script work on Fedora 34.  I'm investigating whether
>> it makes sense to relabel /etc/rc.d/init.d/tvncserver automatically
>> in the official RPM. Everything I've read so far suggests that
>> unconfined_service_t is the appropriate context, since that context
>> was designed for running non-SELinux-aware services.
>>
>> DRC
>>
>> On 2/28/22 12:07 PM, DRC wrote:
>>> Try
>>>
>>>    sudo semanage fcontext -a -t bin_t /etc/rc.d/init.d/tvncserver
>>>    sudo restorecon -R -v /etc/rc.d/init.d/tvncserver
>>>
>>> and then reboot the system.  That seems to work for me.  Those
>>> commands have the effect of making the TurboVNC Server init.d
>>> script run under the system_u:system_r:unconfined_service_t:s0
>>> context instead of the system_u:object_r:initrc_exec_t:s0 context,
>>> which more closely simulates the SELinux context that you get when
>>> you start the TurboVNC Server manually
>>> (unconfined_u:unconfined_r:unconfined_t:s0).
>>>
>>> DRC
>>>
>>> On 2/26/22 5:56 PM, [email protected] wrote:
>>>> Hello,
>>>>
>>>> I upgraded a machine from fedora 34 to 35. After that, I got a black
>>>> screen in the turbovnc client.
>>>>
>>>> If I start turbovnc server manually in a shell, the vnc server starts
>>>> fine, and I can connect.
>>>>
>>>> Then I tried "setenforce 0", and started the turbovnc service, and then
>>>> xfce starts fine, and I can connect the client. I can then turn on
>>>> selinux again, and it seems to continue to work.
>>>>
>>>> I also upgraded turbovnc turbovnc-2.2.91-20220224.x86_64
>>>> but that didnt seem to make a difference.
>>>>
>>>> Any hints how to fix this?
>>>>
-- 
Joakim Verona
[email protected]

-- 
You received this message because you are subscribed to the Google Groups 
"TurboVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/turbovnc-users/87v8woq1at.fsf%40tanaka.verona.se.

Reply via email to