Unfortunately that's not an option for our use case On Thu, Oct 29, 2015 at 4:00 AM <stunnel-users-request@stunnel.org> wrote:

Send stunnel-users mailing list submissions to stunnel-users@stunnel.org

To subscribe or unsubscribe via the World Wide Web, visit https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users or, via email, send a message with subject or body 'help' to stunnel-users-request@stunnel.org

You can reach the person managing the list at stunnel-users-owner@stunnel.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of stunnel-users digest..."

Today's Topics:

1. hex key support for psk (Reese Wilson) 2. Re: hex key support for psk (Michal Trojnara)

----------------------------------------------------------------------

Message: 1 Date: Wed, 28 Oct 2015 23:12:01 +0000 From: Reese Wilson <reesew@tzmedical.com> To: stunnel-users@stunnel.org Subject: [stunnel-users] hex key support for psk Message-ID: < CAJU_q421ksnS8mCtkc6tApdTwUXJrNBZ+69Zt_HxJMpJLGBoiA@mail.gmail.com> Content-Type: text/plain; charset="utf-8"

I ran into an issue with PSK reading the key as ascii instead of hex. I had a gnutls-serv and gnutls-cli set up with a hex key, and I switched the server for one wrapped using stunnel, but using the same key in psk.txt was failing. I eventually got it working by converting the hex characters to binary and placing that in the contents of the file specified by PSKsecrets (psk.txt), but this won't work for certain scenarios. For example, what if the key contains ascii newline characters?