From 1cad3d0e4a67c9071619fa37c18e95b6f986dcbb Mon Sep 17 00:00:00 2001 From: andrew Date: Fri, 17 Jun 2016 05:25:09 +0000 Subject: Added a comment --- .../comment_10_7812a96a98405d924a69e998dd42f275._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/todo/bytes_in_privData__63__/comment_10_7812a96a98405d924a69e998dd42f275._comment (limited to 'doc/todo/bytes_in_privData__63__/comment_10_7812a96a98405d924a69e998dd42f275._comment') diff --git a/doc/todo/bytes_in_privData__63__/comment_10_7812a96a98405d924a69e998dd42f275._comment b/doc/todo/bytes_in_privData__63__/comment_10_7812a96a98405d924a69e998dd42f275._comment new file mode 100644 index 00000000..602f91f0 --- /dev/null +++ b/doc/todo/bytes_in_privData__63__/comment_10_7812a96a98405d924a69e998dd42f275._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="andrew" + subject="comment 10" + date="2016-06-17T05:25:08Z" + content=""" +I've recreated my propellor repository a few times and have had to write out .pfx files. Essentially a binary format of .pem and .key. I had no problem getting the pfx file into privData, but propellor bails when writing the binary data on the host. This patch tackles the writing on host bit (not the writing to privData). You've used `hPutStr` to write out data which errors on certain bytes (because `hPutStr` assumes a character encoding?). 0x00 is a likely candidate. I don't recall the exact error, but at least Haskell noticed this and gave an error rather than writing out a partial file. + +I'll see if I can get a deduping patch to tidy up fileProperty and byteProperty. +"""]] -- cgit v1.2.3