Desktop: Why does this app make a call to api.segment.io ?

Created on 1 Jun 2017 · 6Comments · Source: mattermost/desktop

This is new to one of the later versions - suddenly Mattermost desktop is calling api.segment.io - which is typically used for tracking data in 3rd party services.

Why is this client tracking anything? Feels less secure with this going on. Please advise.

Server Side

Source

fmp777

❤3

Most helpful comment

@jasonblais : It is optional and can be turned off on the server if preferred. No personally identifiable information is collected.

I think that kind of optional option should be set to disabled by default. In other words, it should be an opt-in option instead of an opt-out one.

dannycolin on 18 Jun 2017

👍26

All 6 comments

Thanks @fmp777

You can find out more information here: https://docs.mattermost.com/administration/telemetry.html

It is optional and can be turned off on the server if preferred. No personally identifiable information is collected.

jasonblais on 1 Jun 2017

👎11 😕7

I'll close the issue since it's related to the Mattermost server rather than the desktop app. Feel free to ask further question though.

jasonblais on 2 Jun 2017

👎1

@jasonblais : It is optional and can be turned off on the server if preferred. No personally identifiable information is collected.

I think that kind of optional option should be set to disabled by default. In other words, it should be an opt-in option instead of an opt-out one.

dannycolin on 18 Jun 2017

👍26

I think it is a big security issue to use a host, which changes every 60 seconds its IPs in an unpredictable manner. So since reports are blocked by our firewall anyway (impossible to find a static stable IP), we are forced to disable telemetry ...

jelmd on 9 Oct 2018

Hi,
I didn't want to duplicate this issue.
So I'm going to continue on this one until advised otherwise.
The pi-hole mattermost server is configured to not have telemetry activated. Their team have shown me the screenshot of the box checked to false in the settings.
Still I have plenty of api.segment.io calls on my dns filtering system which is pi-hole or latter nextdns.

Here are the screenshots that I4ve taken when I had a problem before unblocking your telemetry partners.
accept cert2020-04-26 033705
apsegment_blocked_nextdns2020-04-26 033853
certificate error2020-04-26 033534
segment_being_blocked2020-04-26 035628

boistordu on 26 Apr 2020

👍1

@boistordu FYI, I had to reload (View->Reload) my front end app (Linux v4.3.1, in my case) after disabling reporting in the System Console. Errors went away after that.

Currently the cert is bad:

$ curl https://api.segment.io/
curl: (60) SSL certificate problem: EE certificate key too weak
More details here: https://curl.haxx.se/docs/sslcerts.html