QUESTION: accessing pcscd from muvm / fex

[Rad0van]

I don't know if this is question for muvm or fex. I am running Ubuntu Asahi and need to run software for x86-64 that accesses pcscd servive (reading smart cards). The program runs but complains pcscd service is not running / available. Not sure what mechanism is used on x86-64 for the programs to communicate with the daemon and whether it is somehow possible to bridge these in muvm / fex scenario. Any help is appreciated. Thank you.

[slp]

IIRC, pcscd listens for clients on a socket. You would need to expose that socket to the guest. While muvm already exposes some sockets to the guest, it doesn't support having the user to specify additional sockets to be exposed, so you would need to extend it to be able to do that. Should be relatively simple using the existing implementation for pulseaudio as a reference.

[Rad0van]

IIRC, pcscd listens for clients on a socket. You would need to expose that socket to the guest. While muvm already exposes some sockets to the guest, it doesn't support having the user to specify additional sockets to be exposed, so you would need to extend it to be able to do that. Should be relatively simple using the existing implementation for pulseaudio as a reference.

Hi Sergio,

thank you for answer - this is exactly what I have been looking for. I would probably be able to do some simple copy-paste with changing few constants but I am not familiar with either Rust neither muvm internals. Can you point me a little closer as to where to look for this? Thank you.

[slp]

This is what we do in the host:

muvm/crates/muvm/src/bin/muvm.rs

Line 294 in f00a4ee

if let Ok(run_path) = env::var("XDG_RUNTIME_DIR") {

And this is what we do in the guest:

muvm/crates/muvm/src/guest/bin/muvm-guest.rs

Line 128 in f00a4ee

setup_socket_proxy(pulse_path, PULSE_SOCKET)?;

[Rad0van]

Guest seems easy ;-) Host not so much but I'll give it a try... Thanks a lot.