Another thing you can do is only ship compiled Python bytecode files. You
can create these files by using the -O or -OO option. In Python 2, this
creates a .pyo file, in Python 3 this creates a .pyc file with opt1 or
opt2.
On Fri, Nov 9, 2018 at 11:00 AM Dan Ritter wrote:
> Tom Luo:
> > Is
Tom Luo:
> Is there any alternative besides docker?
Yes.
You can:
- set up servers and sell the service of access to your nifty
idea rather than shipping code to the users.
- ask your users to sign a contract that says that they will
not read through the source code or re-use
Is there any alternative besides docker?
On Fri, Nov 9, 2018 at 10:24 AM Rich Pieri wrote:
> On Thu, 8 Nov 2018 23:53:52 -0500
> Tom Luo wrote:
>
> > Thanks for answers. I just feel docker should support the feature to
> > hide all details inside the container and just expose a port.
>
> We
On Thu, 8 Nov 2018 23:53:52 -0500
Tom Luo wrote:
> Thanks for answers. I just feel docker should support the feature to
> hide all details inside the container and just expose a port.
We explained why this is not possible. Your desire to be proprietary
cannot change reality.
--
Rich Pieri
Tom Luo:
> Hi, all,
>
> Thanks for answers. I just feel docker should support the feature to hide
> all details inside the container and just expose a port.
How would you do that? Encrypt the container?
See my previous discussion of how that doesn't actually work.
-dsr-
Hi, all,
Thanks for answers. I just feel docker should support the feature to hide
all details inside the container and just expose a port.
I know I can compile to python code from .py to .pyc. But the python byte
code is not that difficult to reverse engineering.
Thanks,
Tom
On Thu, Nov 8,
one other thing is if you if you are providing a container or vm you could
precompile all or some of the python.
On Thu, Nov 8, 2018 at 10:05 AM Rich Pieri wrote:
> On Thu, 8 Nov 2018 02:34:42 -0500
> Tom Luo wrote:
>
> > Basically, what I need is to provide a port for customers to access
> >
On Thu, 8 Nov 2018 02:34:42 -0500
Tom Luo wrote:
> Basically, what I need is to provide a port for customers to access
> the service. At the same time, I don't want customers to see my code.
>
> What should I do? Any ideas?
The Docker host can see everything in the container. The customer
Dan,
I fully agree, I was mostly making the point that in docker everything is
shared with the host system. its possible to obscure things, but that all
depends on how savy and motivated the users are. in the end docker is a
open system, build by people with an open source mentality. there are
Jason Normand:
> from a strictly technical perspective, in order to make something like this
> work in docker you would need to set up some kind of runtime decryption.
> basically your system would need to read encrypted files from the volume
> then decrypt them into a memory based storage
from a strictly technical perspective, in order to make something like this
work in docker you would need to set up some kind of runtime decryption.
basically your system would need to read encrypted files from the volume
then decrypt them into a memory based storage (harder thought not
impossible
Tom Luo:
> Hi, all,
>
> I developed a software which provide a web service.
> When I deploy the software in customer's machines, I don't want them to see
> the source code.
> I tried to use docker, but I found out that docker cannot provide password
> protection. The customer can still see the
If you open up the service port (let's say it's running on 8080) but
limit SSH login to a key only you have, then they should be able to use
the service without seeing in the docker image at all.
On 11/8/18 2:34 AM, Tom Luo wrote:
Hi, all,
I developed a software which provide a web service.
13 matches
Mail list logo
