https://bugs.kde.org/show_bug.cgi?id=443155
toni_rocha changed:
What|Removed |Added
CC||antonioni.ro...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=443155
pearagon changed:
What|Removed |Added
CC||m...@kylesalter.com
--- Comment #53 from pearagon
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #52 from Lukáš Turek <8...@8an.cz> ---
(In reply to Albert Vaca from comment #43)
> I've modified GSConnect to use ECDSA and it doesn't seem to fix the issue.
> Here's my change:
>
https://bugs.kde.org/show_bug.cgi?id=443155
Ali changed:
What|Removed |Added
CC||fakham...@gmail.com
--- Comment #51 from Ali ---
I have
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #50 from FeRD (Frank Dana) ---
(In reply to FeRD (Frank Dana) from comment #49)
> The SFTP stuff, in
> particular, has next to zero logging on the Android side, AFAICT.
(That wasn't meant as any sort of slight against kdeconnect-android,
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #49 from FeRD (Frank Dana) ---
(In reply to Brian from comment #48)
> (I'm not sure if/how the decryption can be done with a tcpdump cmdline.)
> Any saved traces should now contain the decrypted traffic -- a decrypted
> packet should look
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #48 from Brian ---
"Permission denied" sounds a lot like a different issue I've had before --
https://bugs.kde.org/show_bug.cgi?id=432368
To fix it, you just need to set the Custom Destination in KDE-C Android to your
Downloads folder,
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #47 from Malte Deiseroth ---
(In reply to Brian from comment #46)
> We can probably disregard tests done with the stable version in the Store.
> For now, we're focused on the latest builds, containing tentative fixes in
> both
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #46 from Brian ---
We can probably disregard tests done with the stable version in the Store. For
now, we're focused on the latest builds, containing tentative fixes in both
KDEConnect-Android and GSConnect.
@Albert, do you have any logs
https://bugs.kde.org/show_bug.cgi?id=443155
Barnabás Pőcze changed:
What|Removed |Added
CC||po...@protonmail.com
--- Comment #45 from
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #44 from Andy Holmes ---
(In reply to Albert Vaca from comment #43)
> I've modified GSConnect to use ECDSA and it doesn't seem to fix the issue.
> Here's my change:
>
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #43 from Albert Vaca ---
I've modified GSConnect to use ECDSA and it doesn't seem to fix the issue.
Here's my change:
https://github.com/albertvaka/gnome-shell-extension-gsconnect/compare/main...ecdsa-keys
After applying this change I
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #42 from Lukáš Turek <8...@8an.cz> ---
Unfortunately you're right, it didn't help, it really seems the RFC8308
extension is needed, which requires MINA SSHD version 2.3.0 or later.
Do we really need to use RSA for client authentication? Or
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #41 from Albert Vaca ---
I'm out of ideas, the only alternative is to upgrade the version of mina-sshd
that we use (which doesn't seem easy).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #40 from Albert Vaca ---
I added rsa-sha2-256 but I think it still didn't fix the issue:
https://invent.kde.org/network/kdeconnect-android/-/merge_requests/401
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #39 from Lukáš Turek <8...@8an.cz> ---
I tried that, but it made no difference. It seems that key exchange algorithms
are something different, what's missing is signature algorithm "rsa-sha2-256"
and some protocol extension. These additional
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #38 from Albert Vaca ---
Thanks for the insight, Lukáš!
This change might do the trick:
https://invent.kde.org/network/kdeconnect-android/-/commit/4f44aef5f8bee8603d08cab18decae70f618faa4
Can you please give it a test? You should be able
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #37 from Lukáš Turek <8...@8an.cz> ---
I cleared KDE Connect settings on my phone, and it generated an ECDSA key
instead of RSA, so option HostKeyAlgorithms=+ssh-dss,ssh-rsa is no longer
needed, but that was bug #351725. This one is about
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #36 from Malte Deiseroth ---
(In reply to Albert Vaca from comment #35)
> If I'm not mistaken this should be fixed in the Android app version 1.29.0.
> However, the fix only applies to new installs, so if you have an existing
> version of
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #35 from Albert Vaca ---
If I'm not mistaken this should be fixed in the Android app version 1.29.0.
However, the fix only applies to new installs, so if you have an existing
version of the Android app installed you will have to use "Clear
https://bugs.kde.org/show_bug.cgi?id=443155
Carlo changed:
What|Removed |Added
CC||cirlo...@msn.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=443155
FeRD (Frank Dana) changed:
What|Removed |Added
CC||ferd...@gmail.com
--- Comment #34 from
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #33 from QwertyChouskie ---
Any progress towards a proper fix for this? This completely breaks file
transfers when using GSConnect on any somewhat-modern distro. IMHO it's time
to drop Android <=7 support if no easy workaround to keep it
https://bugs.kde.org/show_bug.cgi?id=443155
QwertyChouskie changed:
What|Removed |Added
Component|common |android-application
CC|
https://bugs.kde.org/show_bug.cgi?id=443155
Hans Deragon changed:
What|Removed |Added
CC||h...@deragon.biz
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #32 from Aleksandar Kostadinov ---
The security concern should not be lesser IMO. The protocol was disabled for a
reason. I just wanted clarification. Enabling the protocol was a good quick-fix
measure. But it is unacceptable in the long
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #31 from Brian ---
SSH-RSA was enabled here in the KDE-Connect desktop app, as a work-around for
this issue:
https://invent.kde.org/network/kdeconnect-kde/-/commit/204207f2e66e87e7696ff1c98d70ce41b3e2d396
I'm using GSConnect on GNOME,
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #30 from Aleksandar Kostadinov ---
Is the KDE connect widget failing for you? I don't see in my ssh configuration
`ssh-rsa` enabled, yet kde connect is working. Maybe it enables it under the
hood and it is much better not to.
I'm just
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #29 from Brian ---
No, as far as I can tell, the situation is still unchanged -- sshd-core is
still stuck at the obsolete version 0.14.0, carrying only "ssh-rsa" support:
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #28 from Aleksandar Kostadinov ---
works for me now. I assume android app and kde got updated several times
already
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443155
micet2004-git...@yahoo.de changed:
What|Removed |Added
CC||micet2004-git...@yahoo.de
---
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #26 from Brian ---
Following that -- Why does KDEConnect Android still bundle an obsolete
sshd-core (0.14.0)?
The reason given so far has been backward-compatibility with older Android
versions, specifically Android 7 and below. This is a
https://bugs.kde.org/show_bug.cgi?id=443155
Brian changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=443155
Simon Redman changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw
https://bugs.kde.org/show_bug.cgi?id=443155
Simon Redman changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw
https://bugs.kde.org/show_bug.cgi?id=443155
Colin J Thomson changed:
What|Removed |Added
CC|colin.thom...@g6avk.co.uk |
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=443155
Albert Vaca changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=443155
Peter Oliver changed:
What|Removed |Added
CC||bugs.kde@mavit.org.uk
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=443155
Lukáš Turek <8...@8an.cz> changed:
What|Removed |Added
CC||8...@8an.cz
--- Comment #21 from
https://bugs.kde.org/show_bug.cgi?id=443155
pixelplanetdev changed:
What|Removed |Added
CC||pixelplanet...@gmail.com
--- Comment #20 from
https://bugs.kde.org/show_bug.cgi?id=443155
Russell Haley changed:
What|Removed |Added
CC||yumpusamongus+...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=443155
Rex Dieter changed:
What|Removed |Added
CC||rdie...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=443155
Colin J Thomson changed:
What|Removed |Added
CC||colin.thom...@g6avk.co.uk
--
You are
https://bugs.kde.org/show_bug.cgi?id=443155
Laurent RINEAU changed:
What|Removed |Added
CC||Laurent.Rineau__kde@normale
https://bugs.kde.org/show_bug.cgi?id=443155
Antonio Rojas changed:
What|Removed |Added
CC|aro...@archlinux.org|
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=443155
Justin Jacobs changed:
What|Removed |Added
CC|jajdorks...@gmail.com |
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=443155
Justin Jacobs changed:
What|Removed |Added
CC||jajdorks...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #19 from Pastafarianist ---
(In reply to Malte Deiseroth from comment #18)
> Looking at the lines you send, can it just be the version?
> implementation 'org.apache.sshd:sshd-core:0.14.0'.
>
> This version of sshd-core is from 2015
https://bugs.kde.org/show_bug.cgi?id=443155
juanmah changed:
What|Removed |Added
CC|juan...@gmail.com |
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=443155
Malte Deiseroth changed:
What|Removed |Added
CC||msdeiser...@gmx.net
--- Comment #18 from
https://bugs.kde.org/show_bug.cgi?id=443155
Pastafarianist changed:
What|Removed |Added
CC||dfa...@gmail.com
--- Comment #17 from
https://bugs.kde.org/show_bug.cgi?id=443155
Michael Olbrich changed:
What|Removed |Added
CC||michael.olbr...@gmx.net
--
You are
https://bugs.kde.org/show_bug.cgi?id=443155
leodream2...@gmail.com changed:
What|Removed |Added
CC||leodream2...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=443155
Ken Rice changed:
What|Removed |Added
CC||krinp...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=443155
Aleksandar Kostadinov changed:
What|Removed |Added
CC||akostadi...@gmail.com
--- Comment #16
https://bugs.kde.org/show_bug.cgi?id=443155
Dimitri Scheftelowitsch changed:
What|Removed |Added
CC||d.scheftelowit...@gmail.com
--
You
https://bugs.kde.org/show_bug.cgi?id=443155
Fabian Vogt changed:
What|Removed |Added
CC||fab...@ritter-vogt.de
--- Comment #15 from
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #14 from MikeC ---
Fixing the android app for kdeconnect seems the most straightforward way to get
this resolved. Hopefully the developers will get that implemented soon. Moving
to more modern and secure key algorithm would make sense, even
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #13 from Antonio Rojas ---
(In reply to MikeC from comment #12)
> OK - I had assumed this came from upstream - presumably the work-around in
> the arch packages provides the basis for the upstream source to be fixed if
> the kde developers
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #12 from MikeC ---
OK - I had assumed this came from upstream - presumably the work-around in the
arch packages provides the basis for the upstream source to be fixed if the kde
developers make the same changes to the source files?
--
You
https://bugs.kde.org/show_bug.cgi?id=443155
Antonio Rojas changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://bugs.kde.org/show_bug.cgi?id=443155
MikeC changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=443155
Dashon changed:
What|Removed |Added
CC||dashonww...@pm.me
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=443155
Oleg changed:
What|Removed |Added
CC||mehanoid...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=443155
PhobosK changed:
What|Removed |Added
CC||phob...@fastmail.fm
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #9 from MikeC ---
This bug from 2020 is not dissimilar to the current bug
https://bugs.kde.org/show_bug.cgi?id=417787
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #8 from MikeC ---
I had a look at the private key for the connection using the command:
$ openssl pkey -in .config/kdeconnect/privateKey.pem -text
and in the output there is a line:
RSA Private-Key: (2048 bit, 2 primes)
SO it is
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #7 from MikeC ---
The matter of using the RSA signatures with sha-1 looks like a possible cause
of the issue. Is there a way to get kdeconnect to use an alternative sig to
test that idea?
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #6 from Martin Droessler ---
(In reply to MikeC from comment #5)
>
> So that all works fine, and suggests the bug is in kdeconnect
Well, I guess, rather in the kdeconnect-app on the remote device/phone.
I suspect the offending change is:
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #5 from MikeC ---
Also I have tested sshfs with the newest openssh package and it works without
issue, such as making a directory mnt as a mount point and doing:
$ sshfs remotemachine:/home/mike/Documents/ mnt
then enter ssh password if
https://bugs.kde.org/show_bug.cgi?id=443155
Prajna Sariputra changed:
What|Removed |Added
CC||putr...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=443155
juanmah changed:
What|Removed |Added
CC||juan...@gmail.com
--- Comment #4 from juanmah ---
I
https://bugs.kde.org/show_bug.cgi?id=443155
--- Comment #3 from MikeC ---
Thank you for comment 1 - I have changed the title to the correct package
involved.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=443155
MikeC changed:
What|Removed |Added
Summary|kdeconnect breaks when |kdeconnect breaks when
|openssl is
74 matches
Mail list logo
