Bug 390153 - spamming proxy
Summary: spamming proxy
Status: RESOLVED FIXED
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: 1.0
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-09 14:04 UTC by Sylvain Paré
Modified: 2020-11-22 02:14 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sylvain Paré 2018-02-09 14:04:41 UTC
Installed two laptops with kubuntu lastly in our enterprise.
Then our admin team brought us bask this issue : our proxy wrote 5Go of acces.log in a week because kdeconnect tried to connect between the two laptops.
We had to uninstall kdeconnect.
I let you imagine how easy it was to evangelize kde to our admin team then.
Comment 1 Nicolas Fella 2018-02-13 16:14:20 UTC
Well, you can't blame KDE Connect for trying to do what it is supposed to do (connect devices).

What kind of solution are you looking for?
Comment 2 Sylvain Paré 2018-02-13 22:06:27 UTC
Thanks for your reply.
Well why 5 Go in a week ?! It is a bit two much.
Perhaps It could try to detect and stop trying to connect.
Comment 3 Matthijs Tijink 2018-02-25 11:36:26 UTC
KDE Connect shouldn't actually send much traffic; it only tries to connect when the network connection status changes (so not very often).

Can you provide more details of the network setup?
Comment 4 Justin Zobel 2020-11-20 05:29:49 UTC
If this is still an issue can you please provide the information requested in Comment 3.

I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 5 Sylvain Paré 2020-11-21 10:19:35 UTC
So i dont work anymore in this enterprise
Comment 6 Justin Zobel 2020-11-22 02:14:49 UTC
As no others have commented saying they also experiencing this bug and we cannot test it I am marking it as resolved. If this issue can be confirmed happening in the future please reopen this bug.