Bug 38496 - tp-qt always uses an IPv4 socket with Localhost access control for file transfers
Summary: tp-qt always uses an IPv4 socket with Localhost access control for file trans...
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-qt (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
: 24110 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-06-20 06:35 UTC by David Edmundson
Modified: 2019-12-03 20:28 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description David Edmundson 2011-06-20 06:35:48 UTC 
Even though the specification states that IPV4 socket types should be available on every CM. This isn't the case. 

Butterfly and Salut do not support this.

TpQt4 should probably also check, and use unix sockets if they're what's
available, to work around broken CMs.
Comment 1 Olli Salli 2011-12-29 07:55:33 UTC 
tp-qt should use the fastest but simultaneously most secure socket type reported as supported by the CM. But as pointed out, currently it just always uses IPv4, even if not supported. And only uses Localhost AC, which is not secure in a multiple user context.
Comment 2 Olli Salli 2011-12-29 07:56:08 UTC 
*** Bug 24110 has been marked as a duplicate of this bug. ***
Comment 3 GitLab Migration User 2019-12-03 20:28:26 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-qt/issues/23.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.