xpra icon
Bug tracker and wiki

Opened 4 weeks ago

Last modified 4 days ago

#2989 new enhancement

Running xpra in a pod/container

Reported by: louis-mulder Owned by: louis-mulder
Priority: major Milestone: 4.2
Component: android Version: 3.0.x
Keywords: Cc:

Description

referencing to r28061
I am not a experienced Python programmer so I attach my pamexec_auth.py module in Python version 2. This module works with the help of some bash scripts to startup a pod with a xpra-session. The Xpra proxy.... runs as an ingress-server in a K8 cluster. I have seen the new interface however after creating the pod it must update the capability display so the proxy knows where it must connect.
How difficult is it to convert this module to Python3 and using the new interface ?

Many thanks on the forehand.....
Louis

Attachments (4)

pamexec_auth.py (8.4 KB) - added by louis-mulder 4 weeks ago.
Python version of pamexec_auth.py
start_pod.sh (2.8 KB) - added by louis-mulder 4 weeks ago.
Bash script to startup a pod or get the ip-info
startup_proxy.sh (11.1 KB) - added by louis-mulder 4 weeks ago.
bash startup script xpra proxyand freeipa client
xpra-proxy-443.sh (30.2 KB) - added by louis-mulder 4 weeks ago.
deploying a Xpra ingress-server, shared storage is based on NFS

Download all attachments as: .zip

Change History (6)

Changed 4 weeks ago by louis-mulder

Attachment: pamexec_auth.py added

Python version of pamexec_auth.py

Changed 4 weeks ago by louis-mulder

Attachment: start_pod.sh added

Bash script to startup a pod or get the ip-info

Changed 4 weeks ago by louis-mulder

Attachment: startup_proxy.sh added

bash startup script xpra proxyand freeipa client

Changed 4 weeks ago by louis-mulder

Attachment: xpra-proxy-443.sh added

deploying a Xpra ingress-server, shared storage is based on NFS

comment:1 Changed 2 weeks ago by Antoine Martin

Milestone: 4.14.2
Owner: changed from Antoine Martin to louis-mulder

So this is a follow up to #2933, right? Or a duplicate?
The ticket title is exactly the same.

I seem to remember saying this before but I can't locate the ticket comment: you should split your pamexec module: there is no need to duplicate so much code.
(and even if there was, you should import most of it from the other modules, not duplicate it)
Just configure your socket with two authentication modules (see wiki/Authentication), the first one is pam and the second one can do what you want.

See also ticket:2933#comment:2 wrt capabilities. Don't use a global.

The command should be configurable.

Don't do this:

argv = c.strget("argv")

Just do: argv = c.strtupleget("argv") then you don't have to parse strings.

display = my_argv.split(u"/")[-1]

If you want to know the display specified by the user, there is a much easier way IIRC.

Last edited 2 weeks ago by Antoine Martin (previous) (diff)

comment:2 Changed 4 days ago by migration script

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2989

Note: See TracTickets for help on using tickets.