Re: Modem authentication via the NM d-bus API - how to handle PUK?

2020-10-17 Thread Aleksander Morgado
Hey, > On Fri, Oct 16, 2020 at 06:01:49PM +0200, Aleksander Morgado wrote: > > > What I could see so far is that the only thing one can provide to the > > > modem > > > via NM is the PIN, that's it. PUK, PIN2, PUK2 are not known to > > > NetworkManager > > > and remain completely unhandled. > >

Re: Modem authentication via the NM d-bus API - how to handle PUK?

2020-10-16 Thread Sergey 'Jin' Bostandzhyan
Hi, On Fri, Oct 16, 2020 at 06:01:49PM +0200, Aleksander Morgado wrote: > > What I could see so far is that the only thing one can provide to the modem > > via NM is the PIN, that's it. PUK, PIN2, PUK2 are not known to > > NetworkManager > > and remain completely unhandled. > > > > My opinion

Re: Modem authentication via the NM d-bus API - how to handle PUK?

2020-10-16 Thread Aleksander Morgado
Hey, > > What I could see so far is that the only thing one can provide to the modem > via NM is the PIN, that's it. PUK, PIN2, PUK2 are not known to NetworkManager > and remain completely unhandled. > My opinion is that PIN is the only thing that NetworkManager should attempt to unlock, and

Modem authentication via the NM d-bus API - how to handle PUK?

2020-10-16 Thread Sergey 'Jin' Bostandzhyan
Hi everyone, I'd like to start a discussion about NetworkManagers SecretAgent D-Bus API in relation to modem authentication. What I could see so far is that the only thing one can provide to the modem via NM is the PIN, that's it. PUK, PIN2, PUK2 are not known to NetworkManager and remain