I am using the newLisp (encrypt) function to encrypt something and need to decrypt it somewhere else, in JavaScript. Then, I have to send back a response from JavaScript and decrypt it in newLisp.
My JavaScript is weak-sauce, but here's the gist (cobbled together from the Internets): https://gist.github.com/a110621fe731facb40ff
The newLisp encrypt response looks like this:
"+ 22O 12 00 31 03O 06 17A7 07 29 03L"))
Whereas the JavaScript output looks like this:
043022079012000031003079006017065055007029003076
I can make a few changes, like:
(43 22 79 12 0 31 3 79 6 17 65 55 7 29 3 76)
But, I still end up with something that's not properly JavaScript-y.
If I force everything to be properly formatted for JavaScript, it all works out...
> "043022079012000031003079006017065055007029003076"
Until I try to go back to the format (encrypt) expects, then I'm at a loss. Because I can't just say...
"Ѐ?0? 00 16 0@P`p???"
I've tried (pack "n" x) and several other options. Nothing seems to get me where I need to be.
Anyone?
P.S. Why doesn't newLisp have SHA256 or AES again? :(
Perhaps Base64 encode/code it while its' travelling ?
Quote from: "cormullion"
Doesn't solve the problem that JavaScript only wants it as a string of integers.
Figured it out -- I think.
(edit: spoke too soon... a text_enc of " 90 60 00 09" maps to (90 60) and the 9 gets removed. So I have to use the original, very long:
I return the JavaScript happy version this way:
And, transform the JavaScript version to newLisp this way:
Which I then pass to (encrypt enc_str my_pvt_password).
Keep in mind, that explode works on byte boundaries only in the utf8 version of newLISP. To make it work on both, utf8 and non-utf8, use:
(65 66 67)
> (unpack (dup "b" (length str)) str) ; unsigned 0 to 255
(65 66 67)
> (unpack (dup "s" (length str)) str) ; displayable character or " 00" decimal notation
("A" "B" "C")
>
So, the question is...
(setf enc_str "067020093000014001022091071092094008065017083090010089067030020084002084018094006091029018016000092085067042093051080017023064052051093080")
(setf enc_str (join (map char (map (fn (x) (int x 0 10)) (explode enc_str 3)))))
How do I turn this into something that works with (encrypt) non UTF-8 systems?
I can't seem to get (pack) to work the way I want.
Also, I can't compile newlisp on Android with UTF-8 support, because when I add UTF-8, I get hundreds of compile and link errors, starting with "newlisp.c:3524: undefined reference to `wchar_utf8"
We posted the last at the same second, see the difference of "b" and "c" in pack/unpack.
Quote from: "Lutz"
Right, but I'm still asking: What the best way to pack enc_str back into 00 format for (encrypt).
I'm using this function, which gets an enc_str like "001003024" but it doesn't work on non UTF-8 systems, sadly.
Not sure what problem you are having. Following works for me on both: utf8 and non-utf8 versions:
(encrypt (join (map char (map (fn (x) (int x 0 10)) (explode js 3)))) "foobar")
;=> "My name is Earl."
but the following is about double as fast:
;=> "My name is Earl."
; or using non-escaping {,} as string delimiters
(encrypt (read-expr (append {"} (join (explode js 3) {}) {"})) "foobar")
;=> "My name is Earl."
... and also works on utf8 and non-utf8.
Also when you produce the JavaScript formatted encrypted string use (unpack (dup "b" ...)) not (unpack (dup "c" ...)), which would produce negative integers for numbers > 127.