Expand my Community achievements bar.

SOLVED

Sending encrypted xml by email submit button?

Avatar

Former Community Member

Hi,

Is it possible to encrypt the xml sent by the "email submit button"? Anyone have any ideas how to protect data from unwanted reading when several users use the same mailbox?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

There are several options.

1) If you have access to a digital signature, even a self-signed digital certificate, you can digitally sign the data. On the email submit button, click Sign Submission and select Sign Data Only on the Sign Data tab.

2) If you have access to a digital signature, use the JavaScript crypto library. See https://developer.mozilla.org/en/JavaScript_crypto.

3) Use a JavaScript implementation of a hash-based message authentication code such as MD5 or SHA-1. For example, see http://jssha.sourceforge.net/.

Steve

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

There are several options.

1) If you have access to a digital signature, even a self-signed digital certificate, you can digitally sign the data. On the email submit button, click Sign Submission and select Sign Data Only on the Sign Data tab.

2) If you have access to a digital signature, use the JavaScript crypto library. See https://developer.mozilla.org/en/JavaScript_crypto.

3) Use a JavaScript implementation of a hash-based message authentication code such as MD5 or SHA-1. For example, see http://jssha.sourceforge.net/.

Steve

Avatar

Level 10

This maybe interesting for you too.

This sample shows how to encrypt form data with RC4 through passwords (hash keys).

http://thelivecycle.blogspot.com/2010/04/xfa-form-data-encryption-rc4.html

http://2.bp.blogspot.com/_-Erl4iHa3eo/S59xqkAONWI/AAAAAAAAACs/mmfInPLq9hs/s400/RC4_1.jpg

http://3.bp.blogspot.com/_-Erl4iHa3eo/S59xvFU9KZI/AAAAAAAAAC0/0jZID1iTKVg/s400/RC4_2.jpg

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----