Re: Octave m-file encryption

[lukshuntim]

On Wednesday, October 29, 2014 10:50 AM, maber wrote:
> I supposed I should not have mentioned the word encryption in such kind of
> forum
>
> Jordi, I disagree with you. First. The m-file is not unique to octave. its a
> Matlab file right and generated in Matlab!... as long as one plays under the
> the rules of GNU.
>
> Secondly what interest would the opensource community have in a m-file
> filled with instrument-specific numbers and confidential patient data? only
> reverse engineers would have interest in that. Im new to Octave and from
> outside view, it appears that if Octave had a little more flexibility it
> would become larger player on the scene!
>
> MN

Hi,

It seems to be a gap of communication. You've clarified what you want - 
not obfuscating the code but encrypting your (sensitive) data.

I don't recall seeing any crypto module/package in octave. Maybe no such 
need has arisen before. From a design point of view, it's not a good 
idea to put code and data together (in an m-file), and doing crypto 
correctly is hard.

Regards,
ST
--