Bug 26961 - WockyPorter should know its own JID.
Summary: WockyPorter should know its own JID.
Status: RESOLVED FIXED
Alias: None
Product: Wocky
Classification: Unclassified
Component: General (show other bugs)
Version: 0.0.1
Hardware: Other All
: medium normal
Assignee: Sjoerd Simons
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 28647
  Show dependency tree / graph
 
Reported: 2010-03-08 08:45 UTC by Will Thompson
Modified: 2010-06-22 11:10 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Will Thompson 2010-03-08 08:45:13 UTC 
The connector returns a connection and the client's JID, but nothing inside Wocky hangs onto that JID. So in Gabble, the GabbleConnection remembers the JID, but WockyPubsubNode (for example) doesn't know its own JID, and hence can't provide useful helpers for subscribing to a node using your full JID or bare JID: the API user has to remember their own JID and pass it in.

Down with that sort of thing.
Comment 1 Simon McVittie 2010-06-22 04:49:03 UTC 
To correct the spoofing-detection in Bug #28647, WockyPorter needs to know its own JID; WockySession wouldn't be enough.
Comment 2 Simon McVittie 2010-06-22 11:10:25 UTC 
Fixed in git, and in the snapshot in Gabble 0.9.14.
Comment 3 Simon McVittie 2010-06-22 11:10:38 UTC 
Fixed in git, and in the snapshot in Gabble 0.9.14.

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.