Xinput and clipboard isolation

diff --git a/README.md b/README.md
index fa64c86fba051a8216b97696b1de87dbae28de2d..f022c50b93e354d3cc6f1ee03897af0e22289591 100644 (file)
--- a/README.md
+++ b/README.md
@@ -1,4 +1,25 @@
-Scripts: vbox
-=============
+VirtualBox Wrapper
+==================
 
-This is the vbox repository.
+Wrapper to provide easy to use GUI isolation.
+
+Xinput and clipboard isolation
+------------------------------
+
+VirtualBox offers some protections agains inherent insecurities on X server
+architecture[1] but not as tough as [Qubes](https://qubes-os.org) or maybe
+how [Subgraph](https://subgraph.com/sgos/index.en.html) is planning.
+
+It's still possible to sandbox applications using VirtualBox and have some level
+of protection while having a slightly simple setup if you can't migrate to Qubes:
+
+  1. Clipboard sharing: you can entirelly disable this feature or have just
+     the hability to copy content from the VM to the host X session.
+
+  2. Xinput isolation: by my early testings, VirtualBox provides xinput isolation
+     as the guest can just capture events when the guest window is focused. But this
+     needs further research.
+
+References:
+
+* [1](http://theinvisiblethings.blogspot.com.br/2011/04/linux-security-circus-on-gui-isolation.html).