-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 13.12.2014 um 17:43 schrieb Bernhard Mayr:
Client side printing does not work on my x2goserver.
When looking at the file /etc/cups/cups-x2go.conf I am wondering whether I need the ssh keys only if the cupsserver resides on a different server as the x2go server?
As there currently seems to be something wrong with X2GoClient's built-in printing feature, I would like to point to an older posting of mine where I described a workaround for Windows Clients: http://lists.x2go.org/pipermail/x2go-dev/2011-December/003137.html
We'be been using this approach with our X2Go-based security solution ever since, and even wrote a (commercial) installer to automate all these steps. Our customers seem to be quite happy with it. ;-)
Have a look at http://www.baur-itcs.de (in German) or contact me off-list if you need commercial assistance.
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUkExXAAoJEG7d9BjNvlEZPncIAJimiskI7Hfd016QmXY8V1JY Mdq9Pkci5abszIdW72fyB111HLC2cvunUxygZfLzQG/t2QIN4V7TMb71bk/48QuS 8kaM1BXeBpDpC39TRg2eLyRbekxp/3MZJuy/n6i7FeHyQz5PHj9LiOe+/xYUu6Q5 o1FoaI9ZSSxkzXEo86p6//VXWjBSbaPMSWg/qUBo7GiSCEa+Yxs/O1Gd08qanQ1S SToFBbL9x7+5VWYSTt+p2Jvst6qxjb0P4o0bpILFALHduiec8hZhUf0DTHmSXpQ0 R/ObHoayrTU22LF8bEBaKXxm2KVNn+IKdNvwh6bQOuKtGQpdugHnyAI0aMRcDgM= =5h6f -----END PGP SIGNATURE-----