Description
In the jigasi README file, in the Transcription options section, there are two places where a variable to hold a sha256 private key is described but it's not clear how to convert a private ssh key file into a single line variable.
Current behavior
Currently, there are two variables: org.jitsi.jigasi.transcription.remoteTranscriptionConfigUrl.key and org.jitsi.jigasi.transcription.whisper.private_key. Both contain the description "Base64 RSA256 private key to sign an ASAP JWT with ..."
Expected Behavior
It would be helpful if the description could be changed to:
Base64 RSA256 private key to sign an ASAP JWT with [....] Generate a key with ssh-keygen -m PKCS8 -b 2048 -t rsa, then remove the "--- BEGIN ..." and "---- END ..." lines as well as all line breaks and spaces from the private key that is generated.
Description
In the jigasi README file, in the Transcription options section, there are two places where a variable to hold a sha256 private key is described but it's not clear how to convert a private ssh key file into a single line variable.
Current behavior
Currently, there are two variables:
org.jitsi.jigasi.transcription.remoteTranscriptionConfigUrl.keyandorg.jitsi.jigasi.transcription.whisper.private_key. Both contain the description "Base64 RSA256 private key to sign an ASAP JWT with ..."Expected Behavior
It would be helpful if the description could be changed to:
Base64 RSA256 private key to sign an ASAP JWT with [....] Generate a key with
ssh-keygen -m PKCS8 -b 2048 -t rsa, then remove the "--- BEGIN ..." and "---- END ..." lines as well as all line breaks and spaces from the private key that is generated.