Unsubscribing since I'm not working on that issue
** Changed in: freerdp2 (Ubuntu)
Assignee: Sebastien Bacher (seb128) => (unassigned)
** Changed in: freerdp2 (Ubuntu Jammy)
Assignee: Sebastien Bacher (seb128) => (unassigned)
--
You received this bug notification because you are a
I don't think remmina will be updated to 1.27 (1.26 would be enough).
Usually the version of the package remain the same, only some patches
get applied when needed. Browsers are exempt from that rule.
Ubuntu maintainers might cherry pick this:
runnuni as suggested didnt help:
$ remmina --set-option tls-seclevel=0
Any time frame when 1.27 will be available in Ubuntu's repo?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
I can confirm that the remmina-next PPA (currently offering version
1.4.27) provides a TLS Security Level drop down in the Advanced tab and
that by choosing the option "0 - Windows 7 compatible" works to connect
to a Windows Server 2008 R2 (which does not have ssl3 enabled) from an
Ubuntu 22.04.1
@t2t-exe some questions:
is the error message exactly the one mentioned here?
what version is the target rdp server (Windows7, Windows 10, Windows Server
2019, ..)?
since you use a new remmina version, what is the tls security level set to?
--
You received this bug notification because you are
Using Remmina 1.4.27 (git n/a)
LSB Version:
core-11.1.0ubuntu4-noarch:printing-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename: jammy
Not Working cannot connect to RDP
--
You received this bug
We had several fixes landing in freerdp since that issue was report.
Dmitry could you try if you still see the problem in the current
version?
** Changed in: freerdp2 (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: freerdp2 (Ubuntu Jammy)
Status: Confirmed => Incomplete
--
> A bit disconcerting that Remmina seems to be the only GUI option for
this task.
KRDC works for this as you can add xfreerdp flags in the "Extra Options"
box for each host or add it to the default Extra Options.
--
You received this bug notification because you are a member of Desktop
The 2.6.1+dfsg1-3ubuntu2 libfreerdp2-2 found on jammy-updates fixes the RD
gateway access issue for me too. Thanks, I can use Remmina again. A bit
disconcerting that Remmina seems to be the only GUI option for this task. Much
depends on it working. Shocking that the bug made it all the way to
Thanks msaxl!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1954970
Title:
remmina "Cannot connect to the RDP server ... via TLS. Check that the
client and server support a
I can confirm that 1.6.1+dfsg1-3ubuntu2 fixes the gateway issue
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1954970
Title:
remmina "Cannot connect to the RDP server ... via TLS.
There is a fix for the gateway issue in jammy-proposed now,
https://launchpad.net/ubuntu/+source/freerdp2/2.6.1+dfsg1-3ubuntu2/+build/23606934,
if someone wants to try it
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in
Backporting that UI seems indeed a better solution than lowering the
default value
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1954970
Title:
remmina "Cannot connect to the RDP
remmina will probably have a tls security level switch in the future.
https://gitlab.com/Remmina/Remmina/-/commit/cf4d8f99ac258248b8e3f3a5314ae047a210a3e9
imo it would be cleaner to backport this instead of lowering the default
security for everyone.
In the next ubuntu version I think the will
@omriasta are you sure you did not use /sec:rdp? 2.6.1+dfsg1-3ubuntu1 does not
contain the upstream patch and will 100% work over gateway if linked to
openssl3 and using a tls based transport over rdp gateway (nla/ext/tls), but as
said /sec:rdp always worked if the remote end allowed it
The
The issue with connecting with gateway has been fixed for me with the
release of freerdp2-wayland and freerdp2-x11 version
2.6.1+dfsg1-3ubuntu1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
I have built a version that includes my mentioned security level
workaround.
It's in ppa:saxl/freerdp2
With that this bug report should be addressed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
@blaze status 403 is quite strange, but afaik openssl1.1 is not in
jammy. If you still have it this is because it probably does not get
removed when updating.
I will try to make a package that fixes both rdp gateway and windows < 8.
It would be very useful if you (and probably others) would be
Well. What do I have
1) I have no control over the gateway software.
2) xfreerdp is blocked here. No matter what I do I'm always getting 403 status
code.
3) There's no way to try the security level workaround in Remmina.
So I guess that is it for now. The only way around is to rebuild
freerdp2
ok, I created a bug report dedicated for the rdp gateway issue
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1970655
regarding the windows 6.1 tls issue (Windows 7 and Windows Server 2008
R2, probably also Vista and Server 2008) there is now an upstream report
here
yes, it would be better, thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1954970
Title:
remmina "Cannot connect to the RDP server ... via TLS. Check that the
client and
reading the first message actually it would be better splitting out the
gateway fix since this bug really talks about windows 2008r2. If you
agree I will make a new report about the backport of the gateway fix
--
You received this bug notification because you are a member of Desktop
Packages,
Thanks for the details shared here. We should start by SRUing the
gateway fix mentioned, then it sounds like there are other issues being
discussed that would be better to be split in a new report?
--
You received this bug notification because you are a member of Desktop
Packages, which is
The relevant change is SHA1 in openssl3
https://github.com/openssl/openssl/commit/aba03ae571ea677fc484daef00a21ca8f7e82708
SHA1 is, contrary to what someone would expect given that the documentation
says:
Level 4
Security level set to 192 bits of security. As a result RSA, DSA and
DH keys
I just discovered that a direct tls connection to a windows 7 (=2008r2) rdp
server indeed fails with
ERRCONNECT_TLS_CONNECT_FAILED
the error is that there is no cipher match (this probably happens also
with a 2008r2 based rdp gateway server, but that someone would need to
check)
this however
again: a debug log output would be very useful.
With a gateway there are actually two TLS handshakes. It would be useful what
handshake fails.
What version of RD Gateway are you using? If it is a 2008/2008R2 based
one, is that even openssl3 compatible? (I checked that TLS1.0 is enabled
on the
I do use a gateway actually
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1954970
Title:
remmina "Cannot connect to the RDP server ... via TLS. Check that the
client and server
> I've been testing this patch and it didn't help in my case
what would probably be useful in this thread if someone would post the
output of ex.
xfreerdp /v: /log-level:debug
I know we are talk about remmina here, but it would be very strange if
xfreerdp works and remmina doesn't.
For me
https://github.com/FreeRDP/FreeRDP/pull/7822 addresses a gateway issue
only, so if you don't use a gateway this will not fix anything for you.
I just compiled the latest ubuntu 2.6.1 version with this patch applied
and for me now gateway connections work
--
You received this bug notification
>https://github.com/FreeRDP/FreeRDP/pull/7822
I've been testing this patch and it didn't help in my case
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1954970
Title:
remmina
it is now fixed upstream and in stable-2.0
https://github.com/FreeRDP/FreeRDP/pull/7823
https://github.com/FreeRDP/FreeRDP/pull/7822
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
This is happening to me as well, see the bug report here:
https://github.com/FreeRDP/FreeRDP/issues/7449
It appears to be an issue with any RD Gateway and related to OpenSSL 3
I tried the Flatpak method suggested and that works for me using the command
line but would really like to be able
I believe that distro version of OpenSSLv3 is missing some neccessary
extension
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1954970
Title:
remmina "Cannot connect to the RDP
Btw snap version:
$ ldd /snap/remmina/5237/usr/lib/libfreerdp2.so.2.6.1
...
libssl.so.1.1 => /lib/x86_64-linux-gnu/libssl.so.1.1
(0x7fe684581000)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
I have a similar issue. With libfreerdp2 being built against libssl.so.3
it doesn't work at all
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1954970
Title:
remmina "Cannot connect
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: freerdp2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
** Changed in: freerdp2 (Ubuntu)
Assignee: (unassigned) => Sebastien Bacher (seb128)
** Also affects: freerdp2 (Ubuntu Jammy)
Importance: High
Assignee: Sebastien Bacher (seb128)
Status: New
** Tags removed: rls-jj-incoming
--
You received this bug notification because you
Is there anything specific to the setup you are using? There is a report
upstream about gateway issue with openssl3,
https://github.com/FreeRDP/FreeRDP/issues/7449
I don't have a win8 to test but connecting to a standard win10 pro
desktop works without issue using the current freerdp package
I tried, and it not fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1954970
Title:
remmina "Cannot connect to the RDP server ... via TLS. Check that the
client and server
Thank you for your bug report, could you try the update on
https://bugs.launchpad.net/ubuntu/+source/freerdp2/2.4.1+dfsg1-1ubuntu1
and tell us if it fixes your issue?
** Changed in: freerdp2 (Ubuntu)
Importance: Undecided => High
** Changed in: freerdp2 (Ubuntu)
Status: New =>
** Tags removed: rls-ii-incoming
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1954970
Title:
remmina "Cannot connect to the RDP server ... via TLS.
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1954970
Title:
remmina "Cannot connect to the RDP server ... via TLS. Check that the
client and
42 matches
Mail list logo
