Skip to content

fix: Replace MD5 with sha256 (trimmed to 48 characters)#69

Open
skalar-bcawkwell wants to merge 1 commit intoSkalar:masterfrom
skalar-bcawkwell:fix-no-md5
Open

fix: Replace MD5 with sha256 (trimmed to 48 characters)#69
skalar-bcawkwell wants to merge 1 commit intoSkalar:masterfrom
skalar-bcawkwell:fix-no-md5

Conversation

@skalar-bcawkwell
Copy link

Many postgresql deployments are now using FIPS mode, which means MD5() is no
longer generally available. Although channel names can be plain strings I guess
there was some concern that potentially the channel name will end up more than
63 characters long, so I switched it to use sha256 instead but trim the output
to 48 characters.

Many postgresql deployments are now using FIPS mode, which means `MD5()` is no
longer generally available. Although channel names can be plain strings I guess
there was some concern that potentially the channel name will end up more than
63 characters long, so I switched it to use sha256 instead but trim the output
to 48 characters.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant