Hey Ralph and everyone who will read this (now and in the future)…
We FINNALLY got this solved! So, as you know, Google changed PEPK and they no
longer supply the Signing Key. Using their new method with PEPK, we got error
after error after error! What finally worked was installing version 1
i finally have a use-case for the signature widget.
* has anyone used it?
* does anyone have experiencing transporting the signature data, then
recreating it, say, by adding it to a document, or generating an svg
file?
___
use-livecode mailing list
use-l
I'm sorry, I don't exactly remember. I think that came from the developer
console when I selected the pepk option when signing. You can always
"Request upload key reset" on the developer console in Setup==>App Integrity
in the "App signing" tab.
Ralph DiMola
IT Director
Evergreen Information Servi
Ralph,
Thank you for the reply. I have an old version of the pepk.jar from about a
year ago… didn’t even try it as I figured it could not be used. I’ll give it a
try… but, where did you/I get the encryptionkey? SomeVeryLongHexString?
-Dan
From: use-livecode on behalf of Ralph
DiMola via
Dan,
This is how I did it. NOTE: pepk-v1.jar is just my name for the version that
worked. I can post this version if you would like to try it?
Actual output from win 10 command line: (names changed to protect the
innocent)
---
java -jar pepk-v1.jar --keystore=MyKeyStore.keystore
--ali
Dan,
Now this is starting to be familiar. As I remember it I got an error with
the tool. After many searches I found out there was some problem with the
most recent version of the PEPK tool. I had to download an older version. It
then worked as expected.
Ralph DiMola
IT Director
Evergreen Informa
