Documentation v4 - not asking for 2FA code

[darkghosthunter]

Documentation v4 - not asking for 2FA code

[DarkGhostHunter]

Came here to say v4 from v2 is not supported.

[dragonfly4]

Digging deeper I saw I would have to rewrite a lot and modify my login process.
So I have swapped Laravel/UI for Laravel/Fortify with built-in 2FA support.
Your package has more features but let's hope Fortify gets a big update with Laravel v9.x

[DarkGhostHunter]

I was pretty much forced to do this package since there was no Fortify when I need it. I’ll probably archive this package since Fortify exists with a cleaner implementation. Italo Baeza C.

…

El 29-10-2021, a la(s) 04:39, dragonfly4 ***@***.***> escribió:  Digging deeper I saw I would have to rewrite a lot and modify my login process. So I have swapped Laravel/UI for Laravel/Fortify with built-in 2FA support. Your package has more features but let's hope Fortify gets a big update with Laravel v9.x — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[dragonfly4]

Correct but Fortify has some limitations and security risks.

I also had to extend some functions and write extra validation checks. I wouldn't switch yet if I was you.

[DarkGhostHunter]

Correct but Fortify has some limitations and security risks.

Like what?

[dragonfly4]

Correct but Fortify has some limitations and security risks.

Like what?

laravel/fortify#201

laravel/fortify#322

laravel/fortify#285
This doesn't work for now, need to investigate further.

++ you can re-use a TOPT so dangerous for MITM attack.

[DarkGhostHunter]

Thanks for the heads up. Seems weird that they decided to go for their own route considering this package already works like a charm (at least for me).