FFe request: Provide remote login options

I filed a separate FFe for the NetworkManager part of this, in hopes to get that in before Beta1 freeze (since that is on for everyone all the time, and the rest of this is opt-in). Bug 1042757.

Once the MIRs are resolved, when are the components targetted to land?

Which ones will make it by beta1 (before we freeze tomorrow), and which are likely to be after and how far after?

The components are in distro today. There needs to be a unity-greeter release with the components in them, but the unity-greeter team would like to know this FFe is going to be accepted before doing that release.

This is of course assuming the security doesn't come back with issues that require fixing.

Will the unity-greeter team only put out a release with just this change, or will they be looking at including other features in it?

On Wed, 2012-08-29 at 17:28 +0000, Kate Stewart wrote:
> Will the unity-greeter team only put out a release with just this
> change, or will they be looking at including other features in it?

This would be the largest part of the change, but also the nm-applet
inclusion that is in bug 1042757.

Also, I forgot, there'll need to be a lightdm release that hasn't been
made as well. It has been tested in a PPA and was waiting on an ACK for
the full stack working (which it does in a PPA currently). It's
expected to move forward as Australia wakes up.

MIRs for two of the required packages are pending:
https://bugs.launchpad.net/ubuntu/+source/libpam-freerdp/+bug/1039634
https://bugs.launchpad.net/ubuntu/+source/lightdm-remote-session-freerdp/+bug/1039636

Besides that, we're ready to push now.

The two main features are NetworkManager support and Remote Login support. Everything else is UI changes or bug fixes.

If this doesn't happen in time for Beta1 Freeze, I'll push tomorrow with the two features disabled to get the rest of the changes in under the UIF wire. But I'd really like to get at least the NM change in before Beta1.

LightDM 1.3.3 is ready and waiting in lp:~ubuntu-desktop/lightdm/ubuntu for release. It contains the new feature required for remote login and three normal bug fixes.

Fixed in unity-greeter 12.10.1 and waiting in lp:~ubuntu-desktop/unity-greeter/ubuntu

Thanks Robert!

lightdm 1.3.3 and unity-greeter 12.10.2-0ubuntu1 uploaded to quantal. Both have this feature disabled for now via distro patches. But the code is there.

MIRs are almost done. Kate, once Beta1 comes out, I believe we'll be ready to upload the feature, barring this FFe.

OK, MIRs are all approved and the code is in quantal, just waiting to be turned on, pending FFe approval.

If all the MIRs are approved, FFE is approved (subject to landing by 9/10) Please make sure to send email to ubuntu-docs and ubuntu-translators since this will be affecting the user interface portions, detailing what will be visibly affected.

This bug was fixed in the package unity-greeter - 12.10.2-0ubuntu3

---------------
unity-greeter (12.10.2-0ubuntu3) quantal; urgency=low

  * Enable Remote Login support (LP: #1040221)
  * Add proper remote login help icon from trunk
 -- Michael Terry <email address hidden> Fri, 07 Sep 2012 11:26:21 -0400

This bug was fixed in the package lightdm - 1.3.3-0ubuntu3

---------------
lightdm (1.3.3-0ubuntu3) quantal; urgency=low

  * debian/patches/06_disable_remote_login.patch:
    - Drop patch, thereby enabling Remote Login support (LP: #1040221)
 -- Michael Terry <email address hidden> Fri, 07 Sep 2012 11:40:01 -0400

Just cleaning up this bug to note everything is approved and in quantal now.

Oh, and emails sent to ubuntu-doc and ubuntu-translators.

As a member of the security team, I've been asked to comment on enabling by default. When performing our reviews (which due to the time of the review, were limited to code-only reviews) , we did not realize that this would be enabled by default-- the code is brand new and it seems (tm me anyway) a strange default to have in the default install since it is presumed only a very small fraction of users will use the service (eg, they need an rdp or citrix server to user it). While our preference would be to not enable by default and let the bugs shake out, we will not block on it being turned on by default. We plan to poke at this more as all the pieces land and we gain a better overall picture, but if serious issues are found, we may revisit enabling it by default.