2023-04-01 08:05:31 |
Atlas Yu |
bug |
|
|
added bug |
2023-04-01 08:06:00 |
Atlas Yu |
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. |
[ 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. |
|
2023-04-01 08:06:45 |
Atlas Yu |
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. |
[ 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. |
|
2023-04-01 08:12:22 |
Atlas Yu |
bug |
|
|
added subscriber OEM Solutions Group: Engineers |
2023-04-01 08:12:26 |
Atlas Yu |
tags |
|
oem-priority originate-from-1956804 sutton |
|
2023-04-01 08:12:31 |
Atlas Yu |
tags |
oem-priority originate-from-1956804 sutton |
oem-priority originate-from-1956804 originate-from-2007061 sutton |
|
2023-04-01 08:12:58 |
Atlas Yu |
oem-priority: assignee |
|
Atlas Yu (pseudoc) |
|
2023-04-01 08:13:28 |
Atlas Yu |
oem-priority: status |
New |
Confirmed |
|
2023-04-01 08:13:36 |
Atlas Yu |
oem-priority: importance |
Undecided |
High |
|
2023-04-01 08:19:23 |
Atlas Yu |
attachment added |
|
libmbim_1.28.0-1~ubuntu20.04.2.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5659790/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff |
|
2023-04-01 08:26:20 |
Ubuntu Foundations Team Bug Bot |
tags |
oem-priority originate-from-1956804 originate-from-2007061 sutton |
oem-priority originate-from-1956804 originate-from-2007061 patch sutton |
|
2023-04-01 08:26:29 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
2023-05-31 10:07:51 |
Atlas Yu |
attachment removed |
libmbim_1.28.0-1~ubuntu20.04.2.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5659790/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff |
|
|
2023-05-31 10:08:21 |
Atlas Yu |
attachment added |
|
libmbim_1.28.0-1~ubuntu20.04.2.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5676943/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff |
|
2023-06-06 13:37:45 |
Sebastien Bacher |
libmbim (Ubuntu): importance |
Undecided |
High |
|
2023-06-06 13:38:29 |
Sebastien Bacher |
libmbim (Ubuntu): status |
New |
Fix Released |
|
2023-06-06 13:38:42 |
Sebastien Bacher |
libmbim (Ubuntu): assignee |
|
Atlas Yu (pseudoc) |
|
2023-06-13 03:43:40 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Sebastien Bacher |
2023-06-14 04:22:47 |
Atlas Yu |
libmbim (Ubuntu): status |
Fix Released |
New |
|
2023-06-14 04:22:51 |
Atlas Yu |
libmbim (Ubuntu): assignee |
Atlas Yu (pseudoc) |
|
|
2023-06-14 07:45:09 |
Sebastien Bacher |
libmbim (Ubuntu): status |
New |
Fix Released |
|
2023-06-14 07:52:38 |
Sebastien Bacher |
libmbim (Ubuntu): status |
Fix Released |
In Progress |
|
2023-06-15 19:21:38 |
Lucas Kanashiro |
nominated for series |
|
Ubuntu Jammy |
|
2023-06-15 19:21:38 |
Lucas Kanashiro |
bug task added |
|
libmbim (Ubuntu Jammy) |
|
2023-06-15 19:21:38 |
Lucas Kanashiro |
nominated for series |
|
Ubuntu Lunar |
|
2023-06-15 19:21:38 |
Lucas Kanashiro |
bug task added |
|
libmbim (Ubuntu Lunar) |
|
2023-06-16 03:06:55 |
Atlas Yu |
attachment added |
|
libmbim_1.28.2-1ubuntu1.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680077/+files/libmbim_1.28.2-1ubuntu1.debdiff |
|
2023-06-16 03:07:21 |
Atlas Yu |
attachment added |
|
libmbim_1.28.4-2ubuntu1.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680078/+files/libmbim_1.28.4-2ubuntu1.debdiff |
|
2023-06-16 03:07:48 |
Atlas Yu |
attachment added |
|
libmbim_1.28.0-1~ubuntu20.04.2.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680079/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff |
|
2023-06-20 02:59:04 |
Atlas Yu |
attachment added |
|
libmbim_1.28.4-2ubuntu1.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680883/+files/libmbim_1.28.4-2ubuntu1.debdiff |
|
2023-06-20 02:59:37 |
Atlas Yu |
attachment added |
|
libmbim_1.28.2-1ubuntu1.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680884/+files/libmbim_1.28.2-1ubuntu1.debdiff |
|
2023-06-20 02:59:55 |
Atlas Yu |
attachment added |
|
libmbim_1.28.0-1~ubuntu20.04.2.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680885/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff |
|
2023-06-20 03:00:25 |
Atlas Yu |
attachment removed |
libmbim_1.28.0-1~ubuntu20.04.2.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5676943/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff |
|
|
2023-06-20 03:01:05 |
Atlas Yu |
attachment removed |
libmbim_1.28.2-1ubuntu1.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680077/+files/libmbim_1.28.2-1ubuntu1.debdiff |
|
|
2023-06-20 03:01:19 |
Atlas Yu |
attachment removed |
libmbim_1.28.4-2ubuntu1.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680078/+files/libmbim_1.28.4-2ubuntu1.debdiff |
|
|
2023-06-20 03:01:38 |
Atlas Yu |
attachment removed |
libmbim_1.28.0-1~ubuntu20.04.2.debdiff https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/2014954/+attachment/5680079/+files/libmbim_1.28.0-1~ubuntu20.04.2.debdiff |
|
|
2023-06-26 04:39:42 |
Atlas Yu |
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. |
[ 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 Fibocom WWAN cards (Intel XMM 7560), and Lenovo are struggling to give a decent way to run the FCC unlock service without this.
Until the device is unlocked, the end users are not able to use the SIM cards, and some of the affected devices have already been shipped. The end users now have to go to the Lenovo support website and download a few scripts and binaries to unlock the device to make their SIM cards work.
The Lenovo wants this patch to be included in jammy, then they can provide the FCC unlock service and manage it in OEM-archive, so the end users can use SIM cards as soon as they receive the laptop.
[ 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. |
|
2023-06-26 14:25:33 |
Dave Jones |
removed subscriber Ubuntu Sponsors |
|
|
|