How would user passwords work if not stored in the core?
When someone logs in currently I just ask the core if the password is valid and off we go.
as
On 23 Mar 2015, at 8:19 am, Barry Warsaw <barry@list.org> wrote:
On Mar 22, 2015, at 09:55 PM, Florian Fuchs wrote:
As for the
passwordkey: It's recognized by mailman.client and exposed within the mlist instance'srequestsproperty. But it's used nowhere in postorius and I would be surprised if it's used anywhere in hyperkitty (Aurélien...?). I guess it can go away.
TBH, I desperately want to purge user passwords from core too! I think they're almost completely unused; the only reason to keep them would be to help Postorious or other REST clients.
As for the email/address keys: We can also just keep the
addresskey in mailman.client and let it use the same value as
Cool.
Can you notify me when your API changes are pushed to LP, so I can update mailman.client accordingly? Just to keep the window as small as possible where we have non-compatible states in the mailman/mailman.client trunks. Especially during GSoC application week...
Will do. I'm working on the subscription policy branch again, and this is a useful refactoring I'm committing before other work. I'm trying to decide whether to commit this to trunk now or when subpolicy lands. Stay tuned!
Cheers, -Barry
Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/andrew.stuart%40s...
Security Policy: http://wiki.list.org/x/QIA9