[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Octave m-file encryption
From: |
Jordi Gutiérrez Hermoso |
Subject: |
Re: Octave m-file encryption |
Date: |
Wed, 29 Oct 2014 13:25:47 -0400 |
On Wed, 2014-10-29 at 15:04 +0800, address@hidden wrote:
> It seems to be a gap of communication. You've clarified what you want -
> not obfuscating the code but encrypting your (sensitive) data.
This is fundamentally impossible with free software if you only resort
to technical means. You cannot give your users the encrypted data, the
decryption algorithm, and the decryption key, and then forbid them
from decrypting the data. This is why every DRM scheme is
fundamentally broken at a technical level.
The only way to do this is to not give your users either the encrypted
data or the decryption key. One way to do this is keeping the
encrypted data and/or decryption key in a server and making this
server do the decryption, communicating the plaintext results back to
the client using standard public-key communication schemes.
Nothing about this is about hiding *code*, though. Nor should there be
any attempt to have security by obscurity; that's fundamentally a
broken idea.
- Jordi G. H.