To answer to some posts (thanks for them), the goal is quite basic :
- I've a single external scilab function (.sci) that is called in scilab routine
- this file has been placed in a specific directory, but under windows, I 
cannot allow execution and deny reading
 
I do not really want to encrypt the file, just to deny the reading and to 
transform it into "black" box ... it's not a commercial issue ... I just want 
to protect my work from some years 
 
Paul

________________________________

De : [email protected] [mailto:[email protected]] De 
la part de Antoine Monmayrant
Envoyé : jeudi 11 avril 2013 16:45
À : International users mailing list for Scilab.
Objet : Re: [Scilab-users] non access to sci files


On 11/04/2013 16:23, Adrien Vogt-Schilb wrote:


        On 11/04/2013 11:15, Carrico, Paul wrote:
        

                Dear All,
                 
                I know it's not possible to encrypt a Scilab .sci file so far ; 
I want to deny reading but I want to allow execution ...
                 
                Does somebody has a trick ? 
                 
                (creating a binary file, include it in a C file, etc. ...I've 
don't know)
                 
                Paul

        Dear Paul, 
        
        No trick will be never possible. The user can always use fun2string to 
display the source code of any function that Scilab can execute after reading 
it from a .sci file. You cannot prevent Scilab for doing so.
        Scilab can be executed in a mode where it displays each line of code 
before executing it.
        The user can also modify Scilab source code to get Scilab display 
whatever Scilab is allow to read. If Scilab can execute it, Scilab can display 
it. This is completely unavoidable. 
        
        

Well, it's not completely true: what you say applies to macros, not to C (or 
Fortran) native functions (that is, compiled and linked).
You can translate all your code to C and write the proper wrapper to use it 
like a native scilab function and compile it and then remove the sources.
I think this should work but I don't know if it worths the effort.

Antoine
(and if you distribute it, are you still in agreement with scilab open licence 
your binary blob with no source?)


        -- 
        Adrien Vogt-Schilb (Cired)
        +33 (0) 1 43 94 73 83

         
        
        _______________________________________________
        users mailing list
        [email protected]
        http://lists.scilab.org/mailman/listinfo/users



--------------------------------------------------------------------------------


Le présent mail et ses pièces jointes sont confidentiels et destinés à la 
personne ou aux personnes visée(s) ci-dessus. Si vous avez reçu cet e-mail par 
erreur, veuillez contacter immédiatement l'expéditeur et effacer le message de 
votre système. Toute divulgation, copie ou distribution de cet e-mail est 
strictement interdite.

This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error, please contact the sender and delete the 
email from your system. If you are not the named addressee you should not 
disseminate, distribute or copy this email.

_______________________________________________
users mailing list
[email protected]
http://lists.scilab.org/mailman/listinfo/users

Reply via email to