[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#950248: krdc: fails to connect to computers from history due to domain format of username



Package: krdc
Version: 4:18.04.1-1
Severity: normal

Dear Maintainer,

when one clicks on a computer from history, that has a username filled
in in a domain format user@domain, the krdc will not connect. This has
been introduced when debian stretch was upgraded to buster.

The computers in history which contain the domain are displayed as:
user%40domain@fqdn

When i click on this entry, it is filled into the connect to line, when
i then click on the right arrow  at right side to connect, I am provided
with the host configuration dialogue and the krdc main screen is in the
background greyd out. However, in the krdc main screen, one can observe
that the string in the connect to box changed to:
user%2540domain@fqdn
and upon clicking ok in the host configuration dialogue and filling the
password upon being prompt, the connection is refused despite the
correct password. The problem is very likely in the above string,
because, if before clicking the arrow to connect in the krdc main
window, i manually change the string to
user@domain@fqdn
the connection works perfectly. This all is caused most likely by wrong
double encoding of special characters, first '@' is encoded as %40 and
saved to history. Afterwards, when retrieved from history, the string is
again encoded since '%'=%25, %40 becomes %2540 and a nonsense string is
thus generated.

Can this be easily corrected, it is a very annoying problem introduced
in buster.

-- System Information:
Debian Release: 10.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages krdc depends on:
ii  libc6                 2.28-10
ii  libkf5bookmarks5      5.54.0-1
ii  libkf5completion5     5.54.0-1
ii  libkf5configcore5     5.54.0-1+deb10u1
ii  libkf5configgui5      5.54.0-1+deb10u1
ii  libkf5configwidgets5  5.54.0-1
ii  libkf5coreaddons5     5.54.0-1
ii  libkf5dnssd5          5.54.0-1
ii  libkf5i18n5           5.54.0-1
ii  libkf5kcmutils5       5.54.0-1
ii  libkf5notifications5  5.54.0-1
ii  libkf5notifyconfig5   5.54.0-1
ii  libkf5service-bin     5.54.0-1
ii  libkf5service5        5.54.0-1
ii  libkf5wallet-bin      5.54.0-1
ii  libkf5wallet5         5.54.0-1
ii  libkf5widgetsaddons5  5.54.0-1
ii  libkf5xmlgui5         5.54.0-1
ii  libqt5core5a          5.11.3+dfsg1-1+deb10u1
ii  libqt5gui5            5.11.3+dfsg1-1+deb10u1
ii  libqt5widgets5        5.11.3+dfsg1-1+deb10u1
ii  libqt5xml5            5.11.3+dfsg1-1+deb10u1
ii  libstdc++6            8.3.0-6
ii  libvncclient1         0.9.11+dfsg-1.3

Versions of packages krdc recommends:
ii  freerdp2-x11  2.0.0~git20190204.1.2693389a+dfsg1-1

Versions of packages krdc suggests:
ii  khelpcenter  4:18.04.0-1
pn  krfb         <none>

-- no debconf information


Reply to: