Bug 5101 - transfer tlstunnel metadata (like IP address) to the python process
Summary: transfer tlstunnel metadata (like IP address) to the python process
Status: CLOSED INVALID
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Misc (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.13.0
Assignee: Karl Mikaelsson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-16 13:18 CEST by Pierre Ossman
Modified: 2020-09-22 12:50 CEST (History)
0 users

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pierre Ossman cendio 2014-04-16 13:18:48 CEST 
Right now there are some things that only tlstunnel is aware of that we'd really like to report to the associated Python process (tlwebaccess/tlwebadm). The prime example is the IP address of the client.

The solution to this depends on if we want an ongoing side channel, or just at the start. The simpler case is just at the start and we could solve that by having the first thing transferred being some kind of structure (e.g. JSON). After that the normal data could continue.

One advantage to this is that we could get rid of the extra socket used for non-TLS traffic and just have a boolean in the metadata instead.
Comment 1 Pierre Ossman cendio 2020-09-22 12:50:00 CEST 
It's unclear what is missing here and what we need it for. The IP address was resolved when we changed the tlstunnel architecture. We don't know what is needed for anything else. So closing.
Note You need to log in before you can comment on or make changes to this bug.