Bug#1028438: otpclient: OTP values are all 000000

2023-01-17 Thread Francisco Vilmar Cardoso Ruviaro
Hi, Thanks for the help guys! libcotp has been upgraded to 1.2.8-1 (see https://bugs.debian.org/1028305). otpclient has been upgraded to 3.1.3-1, we will use libbaseencode version 1.0.15-1 with libcotp 1.2.8-1 while the transition from libcotp 1.2.8-1 to 2.0.0-1 doesn't happen (see

Bug#1028438: otpclient: OTP values are all 000000

2023-01-13 Thread eng . stk
Hi! The problem is not otpclient 3.1.1, but with libcotp12 1.2.7 which is broken (upstream released 1.2.8 with bugfix). Meanwhile upstream released otpclient 3.1.2 and libcotp12 2.0.0, those should be merged instead. Also libbaseencode1 has been deprecated. Thanks.

Bug#1028438: otpclient: OTP values are all 000000

2023-01-13 Thread eng . stk
Hi! The problem is not otpclient 3.1.1, but with libcotp12 1.2.7 which is broken (upstream released 1.2.8 with bugfix). Meanwhile upstream released otpclient 3.1.2 and libcotp12 2.0.0, those shold be merged. Also libbaseencode1 has been deprecated. Thanks. On Thu, 12 Jan 2023 13:26:12

Bug#1028438: closed by Francisco Vilmar Cardoso Ruviaro (Re: Bug#1028438: otpclient: OTP values are all 000000)

2023-01-12 Thread Gunnar Hallgren
Thank you for looking into this. The problem occurs on my original database, as well as in any new database i create. both the new and old databases were created by exporting unencrypted JSONs from Aegis (android). creating a completely new db and adding entries manually also result in 00. i

Bug#1028438: otpclient: OTP values are all 000000

2023-01-10 Thread Buster Keaton
Package: otpclient Version: 3.1.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? the update from 2.6.3-2 to 3.1.1-1 seems to be when the issue