[GH-ISSUE #994] [BUG]Unique key should not use MD5. #2502

New issue

Closed

opened 2026-03-15 20:43:17 +03:00 by kerem · 1 comment

kerem commented

2026-03-15 20:43:17 +03:00

Owner

Originally created by @kexinoh on GitHub (Dec 22, 2024).
Original GitHub issue: https://github.com/hibiken/asynq/issues/994

Originally assigned to: @hibiken, @kamikazechaser on GitHub.

this function uniquekey should not use md5.because md5 is at risk of collision.
github.com/hibiken/asynq@489e21920b/internal/base/base.go (L200-L206)

Originally created by @kexinoh on GitHub (Dec 22, 2024). Original GitHub issue: https://github.com/hibiken/asynq/issues/994 Originally assigned to: @hibiken, @kamikazechaser on GitHub. this function `uniquekey` should not use md5.because md5 is at risk of collision. https://github.com/hibiken/asynq/blob/489e21920b92ae6acfc19c54de91166e56817620/internal/base/base.go#L200-L206

kerem

2026-03-15 20:43:17 +03:00

closed this issue
added the
wontfix
label

kerem commented

2026-03-15 20:43:33 +03:00

Author

Owner

@kamikazechaser commented on GitHub (Dec 23, 2024):

Not in this library. Most task results are often archived and deleted.

@kamikazechaser commented on GitHub (Dec 23, 2024): Not in this library. Most task results are often archived and deleted.

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/asynq#2502

No description provided.

Rows
Columns