[GH-ISSUE #198] Completely remove an account #749

Closed
opened 2026-03-14 10:28:54 +03:00 by kerem · 1 comment
Owner

Originally created by @rc042 on GitHub (Sep 16, 2021).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/198

Hi,

I test AnonAddy and if an account has been deleted, we can't create a new one with the same name. An error message said: "The username has already been taken."

Following my understanding, there is no admin dashboard, and I wonder know how I can definitely delete an account.

There is a table named deleted_usernames with an uniq column named username, however, the cell is encrypted (difficult to delete the good one if I have many account :p ):

CleanShot 2021-09-16 at 12 11 40@2x

Is there a particular reason to have this table? (I think about a security issue: If someone get the alias, he should receive emails from the previous user, right?)

Can I delete this entry without any side effect (except the security issue)? And, is there a cron job witch do that?

Thanks!

Originally created by @rc042 on GitHub (Sep 16, 2021). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/198 Hi, I test AnonAddy and if an account has been deleted, we can't create a new one with the same name. An error message said: _"The username has already been taken."_ Following my understanding, there is no admin dashboard, and I wonder know how I can definitely delete an account. There is a table named `deleted_usernames` with an uniq column named `username`, however, the cell is encrypted (difficult to delete the good one if I have many account :p ): ![CleanShot 2021-09-16 at 12 11 40@2x](https://user-images.githubusercontent.com/22028430/133594436-f0d80261-e8bc-4017-9061-c81d633dd282.png) Is there a particular reason to have this table? (I think about a security issue: If someone get the alias, he should receive emails from the previous user, right?) Can I delete this entry without any side effect (except the security issue)? And, is there a cron job witch do that? Thanks!
kerem closed this issue 2026-03-14 10:28:59 +03:00
Author
Owner

@willbrowningme commented on GitHub (Sep 16, 2021):

Yes, that's correct. The default behaviour is that once a username has been deleted it cannot be used by anyone else again. Yes, it's to prevent the risk of someone else gaining access to a previous user's aliases.

That is what the deleted_usernames table is for, it's encrypted for another layer of security. You can delete any rows from that table if you wish, and then that username will be free to use again.

I'll add an .env option to let you choose whether usernames that are deleted should be added to the deleted_usernames table or not.

<!-- gh-comment-id:920800748 --> @willbrowningme commented on GitHub (Sep 16, 2021): Yes, that's correct. The default behaviour is that once a username has been deleted it cannot be used by anyone else again. Yes, it's to prevent the risk of someone else gaining access to a previous user's aliases. That is what the `deleted_usernames` table is for, it's encrypted for another layer of security. You can delete any rows from that table if you wish, and then that username will be free to use again. I'll add an `.env` option to let you choose whether usernames that are deleted should be added to the `deleted_usernames` table or not.
Sign in to join this conversation.
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/anonaddy#749
No description provided.