@kkarhan@BrodieOnLinux you could also probably use backup / recovery codes in the event that a device is lost. you can also back up the TOTP secret in something like keepassXC and generate tokens right along side your password safe. TOTP will probably outlive an iTAN list and it's a lot easier for someone to store a single secret than a whole list of them. Supporting it would mean more room for vulnerabilities to pop up too as it would have to increase complexity unless they got rid of other MFA methods.
@kkarhan@BrodieOnLinux to me TOTP seems like a perfectly reasonable solution to multi-factor auth. I agree that if you take it seriously you are generating tokens on a device that is not the one you are logging in with, but you can do that with a phone, a crappy laptop, or even some of the various usb devices. Some will even act as a keyboard.
The thing with iTAN is that you need to maintain a whole list of tokens, and I imagine a responsible implementation would only allow each token to be used once which means you have to keep track of which ones you've used. If anyone sees the list (or takes a photo) they can compromise you a lot easier than if someone sees a time based token that will only work within a small window and never again. Yes some math is involved, but in my opinion it is a better proof of authenticity than a token that was generated some ambiguous time ago. I don't want to have to go to the gun safe every time I have to do something on Github that requires a token.
@kkarhan@BrodieOnLinux so do it right and keep things separate. But I still say that a token that is only valid for a small window is definitely going to be more secure than one that is valid for potentially years, and the single secret is easier to protect.
@kkarhan@BrodieOnLinux To me it seems if the issue was really with security, I would imagine you'd already have some form of DFA enabled on your account. I have had TOTP enabled on my account for a while already. Anyway, gitlab is always a thing. Also gitea, and a few others around. I was running gitea last year but I had some hardware problems and haven't had time to fix it. Overall it's a great product IMO.
Honestly if you ask me github ruins git which is kind of designed to be more decentralized. I would rather not use github if it can be avoided, especially now that they are just another microsoft product.
@kkarhan@BrodieOnLinux > Personally, I do want my shit to be so secure that I can't backdoor it at gunpoint without the ability to commit asset denial towards the attacker...
but you have NO dfa now. Any properly implemented DFA offering is a security improvement. I would argue that TOTP is greater than iTAN as far as security goes, but it seems like a debatable topic. Really with both it comes down to secrets storage, but to me it seems storing a lot more secrets is harder to do, and having to keep track of the used ones seems even more bothersome to me.
My bank uses totp. Also by asking for more options you have to recognize it becomes much more complex and could lead to vulnerabilities that negate the benefit all together? These fuckers just published their own private keys like less than a year ago.
Just use a pencil or pen to tick out those you used. #ProblemSolved
Sarcasm aside, they also allow and encourage me to store my recovery codes seperately, thus they can also allow me to do the same with #TANs to #2FA, and with #iTAN they mitigate or at least vastly reduce the success rate of shouldersurfers gaining valid TANs...