This in your changelog is a Debian keyword
  Closes: #2014954
To work on launchpad that needs to be
  LP: #2014954

I hope that helps and gives you a few minor things to fix.

I feel too much out of my comfort zone to fully sponsor this anyway :-/
But I wondered about one more thing to ask you, given that you say this is "the 
feature itself might have bugs and glitches since it is a brand new one and is 
not widely tested by the laptop vendors" wouldn't you think it might be better 
to wait until upstream 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/tags tags 1.30 - then 
at least we'd have the testing of the developers there and all the code they 
tested it with.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmbim in Ubuntu.
https://bugs.launchpad.net/bugs/2014954

Title:
  Backport Intel Mutual Authentications - FCC Lock

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  In Progress
Status in libmbim source package in Jammy:
  New
Status in libmbim source package in Lunar:
  New

Bug description:
  [ Impact ]

  There exist no formal API to do the FCC unlock procedure[1] in the
  latest version of the modemmanger.

  But there is a merged commit[2] that provide this functionality for
  intel WWAN cards in the upstream project.

  Lenovo have several laptops using the Intel WWAN cards, and Lenovo are
  struggling to give a decent way to run the FCC unlock service without
  this.

  [ Test Plan ]

  OEM enablement engineers and Lenovo engineers will help to test if the
  FCC unlock would work on certain laptops with the help of a custom
  package[1] provided by Lenovo which contains the FCC unlock script.

  [ Where problems could occur ]

  This is a completely new feature to support Intel WWAN cards mutal
  authentication, which does not affect other existing features.

  But the feature itself might have bugs and glitches since it is a
  brand new one and is not widely tested by the laptop vendors, still it
  is better than nothing.

  [ Other Info ]

  [1] FCC unlock procedure: 
https://modemmanager.org/docs/modemmanager/fcc-unlock/
  [2] intel-mutual-authentication: new service, fcc-lock: 
https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/157
    - when the device is first shipped or comes out of the factory,
      it should be protected with a lock till the device reaches
      the end user. This FCC lock feature will ensure the device
      is secured till its unlocked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2014954/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to