Hi.

1) securitypes=none should be set as without this Xvnc will ask password set in 
Xvnc global password file.
We don't want this to happen, as lightdm authenticates user, not Xvnc. 

2) current setting works as intended - you can check it yourself.

So, I'd close this bug as invalid. 

С уважением,
Александр Пыхалов,
программист отдела телекоммуникационной инфраструктуры
управления информационно-коммуникационной инфраструктуры ЮФУ


________________________________________
От: Tim Mooney <[email protected]>
Отправлено: 10 апреля 2019 г. 0:13:48
Кому: [email protected]
Тема: [oi-dev] Xvnc securitytypes=none and issue #10584


All-

I've been looking at some of the issues in the issue tracker that are
categorized as "bite-size", to see if I could help resolve some of the
easy ones.

In looking at

        https://www.illumos.org/issues/10584

Which suggests we should drop the "securitytypes=none" from the commented
Xvnc line in our lightdm.conf, I see that one of our patches specifically
adds that, and also patches the source to include it.

I can provide a patch that alters the existing patch, but I don't
understand the reason for the change in the first place.

It looks like alp and Michal are the only two to have been involved with
that patch (lightdm/patches/17-customize-config.patch).

Can anyone comment on why securitytypes=none is being added?

Tim
--
Tim Mooney                                             [email protected]
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, Quentin Burdick Building                  701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev

_______________________________________________
oi-dev mailing list
[email protected]
https://openindiana.org/mailman/listinfo/oi-dev

Reply via email to