Re: KDE phoning home
On Sat, 06 Sep 2025 11:15:03 +0200, Martin Steigerwald wrote:
> Hi Rob, hi Andrey, hi.
>
> Rob Brewer - 05.09.25, 23:45:23 CEST:
>> I wasn't aware of the GUI of DrKonqi but I must have clicked on "Send a
>> crash report" at some point not realising that this would send a report
>> to the IP that was blocked by my firewall and not helped by the fact
>> that this IP doesn't have any relevant whois information or a reverse
>> DNS, so it looked rather like a bogus IP to me.
> […]
>> Thank you and Martin for your help with this. I now have a much better
>> understanding of drkonqi and the implications of sending reports.
>
> So for clarity: I gather that you actually initiated the sending of
> reports yourself?
>
I would suspect that was the case although this wasn't a conscious
decision. In trying to remember now what caused this, if I can remember
correctly I was having a problem with entering a pass phrase into
Kleopatra and DrKonqi popped up and without paying a lot of attention
probably clicked on "send Automatic report" option without understanding
the implications.
If the pop up has stated that it would send a report to 77.235.60.43 or
even crash-reports.kde.org, I would probably have given DrKonqi more
attention, but didn't realise what had happened until I was aware of the
outward going failed connections in the firewall logs a day or so later.
My problem was that I couldn't find a way of stopping the connection
attempts once they had been initiated or what information was being sent.
> Then I'd argue there is no privacy related bug to report :)
>
> Best,
Now that I have found the "Crashed Process Viewer" it all makes a lot more
sense. I didn't anticipate that this was a privacy issue, I just didn't
understand the process that had initiated the failed outgoing connections.
Regards
Rob
Reply to: