You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an issue when a key file was generated by some tools or scripts, and some non-visible characters were inserted. This can be New line or Carriage return symbols, for example. It will be useful to filter such things since even not all text-editors can show that. I had an issue, when echo command inserted 0A byte at the end of the line.
To fix it, something like like this $string = preg_replace('/[\x00-\x1F\x7F]/u', '', $string);
But in this case, how I should setup pipeline to deploy new version of my app, but use the key that was generated previously? Right now I store generated key in secrets storage, and put it in place right before application start. An at his moment I faced with this issue. What recommendations how to manage key in CICD processes?
On 26 Mar 2021, 13:05 +0200, Sebastiaan Stok ***@***.***>, wrote:
You shouldn't use anything else but the provided KeyFactory to generate a key file, this ensures the key-file Hex encoded.
Using anything else doesn't guarantee that Halite is able to process the key-file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
There is an issue when a key file was generated by some tools or scripts, and some non-visible characters were inserted. This can be New line or Carriage return symbols, for example. It will be useful to filter such things since even not all text-editors can show that. I had an issue, when
echo
command inserted0A
byte at the end of the line.To fix it, something like like this
$string = preg_replace('/[\x00-\x1F\x7F]/u', '', $string);
should be inserted here
https://github.com/paragonie/halite/blob/master/src/KeyFactory.php#L819
The text was updated successfully, but these errors were encountered: