Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Features questions #51

Closed
victorca25 opened this issue Jun 12, 2020 · 4 comments
Closed

Features questions #51

victorca25 opened this issue Jun 12, 2020 · 4 comments

Comments

@victorca25
Copy link

victorca25 commented Jun 12, 2020

I’ve been reading your roadmap of ideas and it’s really impressive, great ideas all over the place.

From reading them, I also have a couple of questions just to know if they are feasible:

  • about the portable sandboxes, would it be possible to compact (zip?) the sandboxes for easier migration? For example, like Thinstall/ThinApp does that generates a single executable (and afaik, deflates on scratch space when executed). This could also morivate a behavior similar to the distribution of Docker images in some sort of hub (like portableapps.com). I currently use sandboxie in combination with Python virtualenv to manage different environments and app versions and this sounds interesting
  • something, similar would be sandbox snapshotting, to easily revert to a prior version. A simple way could be by compacting the sandbox. The problem would be the data duplication, but I don’t know if an alternative is too complicated
  • lastly, about the networking, if not including the firewall functionality directly, did I understand correctly that your idea is to attach a virtual networking device to each sandbox? That would be very interesting
@DavidXanatos
Copy link
Member

  1. zipping would be possible but IMHO the overhead would be to large.

  2. some thign like this is on my todo, it would behave liek sandboxie behaves towards the system, when you create a snapshot you get a new root dir and all new changes go there and from the apps view point overwrite the old data.
    The sandboxed registry would however be copied enteirly

  3. Not really just in that sense as the ap would see a virtual mac but it would not be a functional device, the traffic would go through its regular route through the real device.

@victorca25
Copy link
Author

victorca25 commented Jun 19, 2020

Thanks for your reply!

  1. zipping would be possible but IMHO the overhead would be to large.

What if it's only used for portability? i.e., copy a sandbox from one computer to another. The use case is for example to share a development environment with all the required dependecies

  1. some thign like this is on my todo, it would behave liek sandboxie behaves towards the system, when you create a snapshot you get a new root dir and all new changes go there and from the apps view point overwrite the old data.
    The sandboxed registry would however be copied enteirly

Aha! I didn't know that, that's really interesting, great to know!

  1. Not really just in that sense as the ap would see a virtual mac but it would not be a functional device, the traffic would go through its regular route through the real device.

I understand. I will look for options on how to do something like that, it can be really useful for some cases.

Cheers!!

@DavidXanatos
Copy link
Member

I understand. I will look for options on how to do something like that, it can be really useful for some cases.

What use case exactly do you have in mind?

@victorca25
Copy link
Author

Initially, just to experiment, but I was thinking about port forwarding rules to, for example, host isolated API endpoints in separate sandboxes. Maybe I'm mixing it too much with containers, but TBH, containers in Windows are not extremelly efficient hehe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants