Colin Holgate wrote:
> I may have missed a reply too. Which one covered the question of the PDF
> remaining encrypted after the user has downloaded it?
You added the following 5 requirements after my response containing the
suggested implementation:
1. The PDF file itself is also to be encryp
On 03/05/2016 01:46 PM, Colin Holgate wrote:
I may have missed a reply too. Which one covered the question of the PDF
remaining encrypted after the user has downloaded it?
Sorry, I cleaned out my mailboxes earlier. Look for Lyn's longer reply
about three levels back in this discussion.
--
I may have missed a reply too. Which one covered the question of the PDF
remaining encrypted after the user has downloaded it?
> On Mar 5, 2016, at 4:26 PM, Mark Wieder wrote:
>
> On 03/04/2016 10:43 PM, Lyn Teyla wrote:
>> The whole point of HTTPS is _not_ just to authenticate the website, bu
On 03/04/2016 10:43 PM, Lyn Teyla wrote:
The whole point of HTTPS is _not_ just to authenticate the website, but also to
encrypt the data in transit:
Yes, but only in transit.
The latter question had already been addressed in my earlier reply...
Yes, I missed the earlier reply. Just didn't
Mark Wieder wrote:
> On 03/04/2016 06:38 PM, Lyn Teyla wrote:
>
>> Using a HTTPS connection ensures that the PDF file is transmitted securely.
>
> Uh, sorry, no.
> HTTPS by itself will (mostly) guarantee that you are connected to the server
> you think you're connecting to. There's no encryptio
Just as an idea:
A few times I used this one (it's basically AES-128).
There are also examples that basically worked for me.
So: Not really an experience but the few times it worked.
https://github.com/defuse/php-encryption
___
use-livecode mailing list
I think we weren’t planning on using Acrobat at all. It would be an unencrypted
PDF that is encrypted on a server, saved locally with the same encryption, and
only viewable by the logged in user as a local file,
> On Mar 4, 2016, at 10:55 PM, stephen barncard
> wrote:
>
> On Fri, Mar 4, 2016
On 03/04/2016 06:38 PM, Lyn Teyla wrote:
Using a HTTPS connection ensures that the PDF file is transmitted securely.
Uh, sorry, no.
HTTPS by itself will (mostly) guarantee that you are connected to the
server you think you're connecting to. There's no encryption unless you
enforce it yoursel
On Fri, Mar 4, 2016 at 7:23 PM, Colin Holgate
wrote:
> I found out more info, the local copy of the PDF needs to be encrypted
> too. This isn’t what it is, but imagine it’s top-secret, that even other
> users of your computer shouldn’t see, I need to download the file and just
> let you see it, w
I found out more info, the local copy of the PDF needs to be encrypted too.
This isn’t what it is, but imagine it’s top-secret, that even other users of
your computer shouldn’t see, I need to download the file and just let you see
it, with some sort of password entry to unlock it.
> On Mar 4,
> Colin H. wrote:
> A PDF is online somewhere...
Of course, if you don't insist on HTML5 (despite the subject)
you could also think about simpler solutions available in php
which is much faster than LC server.
Others here (Peter H.?) will have several ready made solutions
for that.
__
Colin Holgate wrote:
> Is LiveCode required in what you say?
You can use LiveCode Server (or any other server-side language) to perform
those tasks.
> Does the PDF travel securely?
Using a HTTPS connection ensures that the PDF file is transmitted securely.
Lyn
_
Thanks for the detailed explanation.
Is LiveCode required in what you say?
Does the PDF travel securely?
> On Mar 4, 2016, at 7:57 PM, Lyn Teyla wrote:
>
> Colin Holgate wrote:
>
>> A PDF is online somewhere. A logged in user asks for it, and the server
>> encrypts it before sending over, u
Colin Holgate wrote:
> A PDF is online somewhere. A logged in user asks for it, and the server
> encrypts it before sending over, using some sort of key that was in the
> query. On receiving the data, the client side would have to unencrypted it,
> and show it as the original PDF in a browser.
Forgot to add the link where you can try which functions work (or not) in dp-15
HTML5 standalones:
Because on-rev is moving tonight, you could use this one:
http://hyperhh.org/html5/TerminalZero-8.0.0-dp-15X.html
___
use-livecode mailing list
use-liveco
Hopefully the exception key would help. Only the user would know how to
unencrypt the image.
> On Mar 4, 2016, at 7:07 PM, [-hh] wrote:
>
> Currently the ask dialog is the **only** way to communicate
> with a HTML5 standalone.
> You simply have to manage, that your imagedata can pass the
> dia
Currently the ask dialog is the **only** way to communicate
with a HTML5 standalone.
You simply have to manage, that your imagedata can pass the
dialog (no CR). And be aware that everybody can read your
script, but that shouldn't matter. The rest works "as usual".
The copy/paste via "ask" mechanism
Yes. There are other options, but I was hoping that LiveCode could do it in an
easier way. At worse, the encryption could be as simple as Base64.
> On Mar 4, 2016, at 6:48 PM, Monte Goulding wrote:
>
> I wouldn't expect imageData to be an issue in HTML5 but encryption seems like
> a stretch a
I wouldn't expect imageData to be an issue in HTML5 but encryption seems like a
stretch at this stage. Does it need to be in a browser?
Sent from my iPhone
> On 5 Mar 2016, at 8:35 AM, Colin Holgate wrote:
>
> I’ve been tasked with a problem to solve, and I think I can use any tool to
> do it
19 matches
Mail list logo
