>> ah, not totally dropped, but dropped for bcrypt; see this and a couple >> of subsequent commits: >> >> https://github.com/Kozea/Radicale/commit/438d5f1735e84210ea85e603632e5b84929b7307 > > hmm. but then there's > https://github.com/Kozea/Radicale/issues/1896#event-20157710330 > so radicale _isn't_ handling this. That's... odd, like sure the bug was introduced indirectly, but they should at least handle it imho Related PR, based on this in fact it might be better to wait for this to settle down before updating the passlib port, and depending on how that pans out, maybe reintroduce bcrypt through passlib in Radicale? https://github.com/notypecheck/passlib/pull/25
- radicale broken in 7.8 due to py3-bcrypt changes Vincent Lee
- Re: radicale broken in 7.8 due to py3-bcrypt changes Stuart Henderson
- Re: radicale broken in 7.8 due to py3-bcrypt cha... Lydia Sobot
- Re: radicale broken in 7.8 due to py3-bcrypt cha... Vincent Lee
- Re: radicale broken in 7.8 due to py3-bcrypt cha... Lydia Sobot
- Re: radicale broken in 7.8 due to py3-bcrypt... Stuart Henderson
- Re: radicale broken in 7.8 due to py3-bc... Stuart Henderson
- Re: radicale broken in 7.8 due to p... Lydia Sobot
- Re: radicale broken in 7.8 due to py3-bcrypt changes Lydia Sobot
- Re: radicale broken in 7.8 due to py3-bcrypt cha... Stuart Henderson
- Re: radicale broken in 7.8 due to py3-bcrypt changes Aric Gregson
