Hi,
On Fr 25 Jan 2019 14:42:27 CET, Stefan Baur wrote:
Am 25.01.19 um 11:19 schrieb rubens.zanatta@grad.ufsc.br:
I think it might be the client version that's causing the problem. 4.1.1.0 introduced a fix for Bug 592 [0], but, in doing so, broke other things related to Kerberos, as reported in Bug 1258 [1] and (hopefully) fixed in 4.1.2.0.
Yes, updating to 4.1.2.1 through the PPA fixed it. Working perfectly with Kerberos now.
Yay! :-)
@Mike#1: Do you think you can get X2GoClient 4.1.2.1 pushed into Ubuntu (at least 18.04, possibly 16.04 as well), so people don't need to add the PPA? "Un-breaks Kerberos support" sounds like a valid reason to get it updated.
Nope. I am not a Ubuntu MOTU Developer. Neither would they (Ubuntu
MOTU team) accept new upstream releases for such a minor reason
(sorry, but Krb5 Login support is still a rare case scenario).
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de