I notice the following things about the provided configuration: - No account or passwd stanzas are specified. This means it will use the defaults from /etc/pam.d/other; that's generally a good thing. - common-auth and common-session are not included (as commented above). This makes sense given the intent to provide freerdp authentication, but it's a very non-PAM-ish way to do it. Why, for instance, is this not done as a pam-auth-update profile for the freerdp module, which enables freerdp as one of the available methods for authenticating to a single lightdm service? Looking at the source, apparently the answer is that we want to use freerdp authentication only for a freerdp session, so it is indeed a different service from lightdm' standard usage; so that's a perfectly fine answer, and shouldn't be a blocker for main IMHO. - gnome-keyring and selinux modules, used in the standard lightdm config, aren't mentioned here. I guess gnome-keyring doesn't matter at all if the session just launches an rdp client; but shouldn't the selinux policy still be applied (if selinux is in use)?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1039636 Title: [MIR] lightdm-remote-session-freerdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-remote-session-freerdp/+bug/1039636/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
