VLC 3.2.x & 3.3.x dev issues

VLC for Android and Chrome OS specific usage questions
Jean-Baptiste Kempf
Site Administrator
Site Administrator
Posts: 37523
Joined: 22 Jul 2005 15:29
VLC version: 4.0.0-git
Operating System: Linux, Windows, Mac
Location: Cone, France
Contact:

Re: VLC 3.2.x & 3.3.x dev issues

Postby Jean-Baptiste Kempf » 15 Feb 2021 13:54

Midi merged in 3.4.0
Jean-Baptiste Kempf
http://www.jbkempf.com/ - http://www.jbkempf.com/blog/category/Videolan
VLC media player developer, VideoLAN President and Sites administrator
If you want an answer to your question, just be specific and precise. Don't use Private Messages.

Stef_An
Blank Cone
Blank Cone
Posts: 38
Joined: 13 Apr 2018 23:50

Re: VLC 3.2.1 & 3.2.2 issues

Postby Stef_An » 23 Jun 2021 00:18

And I'm not going to post reports anymore on https://code.videolan.org/videolan/vlc-android because I don't want to use Google neither my mobile phone for two-factor authentication.
I'm quite sure I'm not the only one in this case, so please find another way for 2FA :wink:
I know, that this is a workaround, but it works: I successfully used oathtool in Linux to create a 6 digit PIN from the long code on the 2FA setup page. The whole article about it is here:

https://www.cyberciti.biz/faq/use-oatht ... ation-2fa/

At the end, all you need is a command like oathtool -b --totp 'N3V3R G0nn4 G1v3 Y0u Up' and it generates your PIN. The only problem - it works just for the current session. So after logoff, on the next logon, one have to repeat the PIN generation. But on the bright side: one don't have to install some extra software on the phone or somewhere else.

On Windows, WinAuth should do the trick.

Stef_An
Blank Cone
Blank Cone
Posts: 38
Joined: 13 Apr 2018 23:50

Re: VLC 3.2.1 & 3.2.2 issues

Postby Stef_An » 06 Jul 2021 14:32

I know, that this is a workaround, but it works:
Afterwards, I found this solution on the wiki.

So now one has 3 possibilities:
  1. As in the wiki, just save the long code from the right of the QR code and use it with oathtool to manually generate the PIN every time one needs it.
  2. Use some full-GUI solution like OTPClient on Linux or WinAuth on Windows or Linux (here with wine). One can create a local saved database and let the PIN be generated every time one needs it. There is no need to install some extra software on the PC or smartphone and sign-up for another account on another service. And the data is saved locally, not in some cloud. One has to, on the other side, setup such database on every device, where one likes to log in into the GitLab of the VLC.
  3. As a deviation from the both other scenarios: one just deactivates 2FA every time before one logs off on the GitLab. This way, next time after the log-in, one would be asked to set up the 2FA again and would be once again shown the long code to create a PIN. There is no need to save any information locally. One just uses some program, GUI or not, to generate the PIN as in the set-up step. But: don't forget to deactivate the 2FA, if you don't save the code(s)!
In any scenario: save the recovery codes, for the case you lose the code or need them otherwise. And: either save the code right to the QR code in some file/program database or on the paper, or don't forget to deactivate the 2FA before logout.


Return to “VLC for Android and Chrome OS”

Who is online

Users browsing this forum: Irene86 and 21 guests