octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #56633] Know how protection: Running encrypted


From: Georg Wiora
Subject: [Octave-bug-tracker] [bug #56633] Know how protection: Running encrypted program files
Date: Mon, 15 Jul 2019 10:15:53 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0

URL:
  <https://savannah.gnu.org/bugs/?56633>

                 Summary: Know how protection: Running encrypted program files
                 Project: GNU Octave
            Submitted by: gwiora
            Submitted on: Mon 15 Jul 2019 04:15:52 PM CEST
                Category: Interpreter
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Feature Request
                  Status: None
             Assigned to: None
         Originator Name: gwiora
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: other
        Operating System: Any

    _______________________________________________________

Details:

= Situation =

We (and probably others) are using octave from time to time to deploy
applications to customers. We are looking for an appropriate method to protect
our know how in the deployed scripts and functions. Unlike Matlab, Octave does
not provide p-code files yet. Pcode is _not encrypted_, but just obsfuscated.


= Request =

I would like to request a new feature in octave (e.g. a special startup option
) that allows reading of encrypted source code files. Encryption method(s)
should be state of the art (e.g. BlowFish could be ok).

I think we need to discuss what is the best way to achieve this goal and how
this could be implemented. Therefore I would like to start a list of features
that should be included and I would be happy about any contribution to it.


= Features = 

* Octave should decrypt one or more source code files or source code
directories or ziped/tared source code files with at least one cryptographic
method and at least one key on the fly while interpreting/parsing it.

* Choose cryptographic method and provide cryptographic key as command line
arguments

* Providing an external program / method to decrypt input files. It is
important to have a secure pipeline for transporting decrypted files to octave
interpreter. E.g. storing decrypted contents in temporary files would be NOT
acceptable.


= Contribution =

For your contribution a suggest citing the feature list in your comment and
modifying/extending it as you think.






    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?56633>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]