BrowserBox - remote browser isolation tool
npm install bbproBrowserBox is an embeddable, multiplayer browser that facilitates RBI (remote browser isolation) and zero trust protection. We've just integrated support for Tor.
You can now browse the web through Tor, when using BrowserBox. BrowserBox also supports running itself as a Tor hidden service](#rotating_light-latest-news-browserbox-hidden-services), so you can access your BrowserBox instances over the Tor network.
We're thrilled to announce the following major updates to BrowserBox that will enhance your user experience and streamline your workflow!
- What's New in BrowserBox
- BrowserBox on Tor
- Installable PWAs on Desktop
- Protocol Links Support
- Latest News: BrowserBox Hidden Services!
- AWS EC2 Installation
- Docker Quick Start
- Special Event: Ephemeral Web Proxy
- General README
-----
#### š Enhanced Privacy with Tor Support
We are excited to announce that BrowserBox now supports Tor, providing you with a more private and secure browsing experience. This feature is still in alpha, but we're committed to continuously improving it to match the security level of the Tor Browser over time.
Key Features:
- Onion Sites Accessibility: Browse .onion websites seamlessly.
- Privacy-First Browsing: Enhanced encryption for anonymity and security. Tor conceals the IP address of your RBI server.
- Socks5 Proxy Integration: Traffic securely routed over a Socks5 proxy.
- Simple Tor Activation: Easy activation using the --ontor flag.
- Platform Compatibility: Tested on macOS and Debian.
#### :gear: Using BrowserBox with Tor
Activate Tor in BrowserBox with this command:
``shell`
$ setup_bbpro
$ bbpro
If you want to switch it off again, shut down as normal (pm2 delete all), and re-run setup_bbpro without the --ontor flag.
Start exploring the web with Tor's added security.
#### :warning: Important Caveats and Commitment to Security
As this Tor integration is in alpha, there are several important considerations:
- Proxy and Tor Escapes: There's a potential for some requests to bypass the Socks5 Tor proxy or Tor itself, which could impact privacy. We are actively working to identify and mitigate these risks.
- Adherence to Tor Guidelines: We aspire to aligning our Tor integration as closely as possible with the best practices recommended by the Tor Project. This includes careful configuration to prevent leaks and maintaining the anonymity that Tor provides.
- Ongoing Security Enhancements: Our goal is to eventually provide a level of security comparable to the Tor Browser. We'll be regularly updating and improving the Tor functionality in BrowserBox.
- Exploring Alternatives: We are considering the integration of alternative browsers like Brave as the underlying engine for RBI, which may offer a more secure base than Chrome for Tor browsing.
#### :speech_balloon: Your Input is Valuable
Your feedback is crucial for our continuous improvement. Please report any issues or suggestions to enhance the Tor functionality on our GitHub issues page. Contributions, especially those that help achieve parity with Tor Browser's security, are highly appreciated.
Stay tuned for more updates and enhancements in BrowserBox, and as always, enjoy a secure browsing experience!
-----
You can now install BrowserBox as a Progressive Web App (PWA) on your desktop! This means smoother performance, offline capabilities, and a more integrated experience with your operating system.
Key Benefits:
- Seamless Integration: Feel the power of a native app with the flexibility of a web application.
- Offline Access: Access essential features even without an internet connection.
- Reduced Resource Usage: Enjoy a more efficient use of system resources compared to traditional web browsing.
Introducing protocol links support with web+bb://. Now, you can open links directly in BrowserBox by prefacing them with web+bb://. This feature allows for more efficient navigation and a streamlined process to access web content.
How it Works:
- Simply prefix your URL with web+bb://.https://example.com
- For example, to open , use web+bb://https://example.com.
- The link will automatically open in BrowserBox, providing a seamless browsing experience.
This update is part of our ongoing commitment to enhance BrowserBox and make your web experience as efficient and enjoyable as possible. Try out these new features and let us know what you think!
Stay tuned for more updates, and as always, happy browsing with BrowserBox!
-----
Before starting, fork or generate this repo to your account.
Then ensure that:
1. Issues are switched on, and
2. Actions are enabled.
To begin the action to create your BrowserBox Tor Hidden Service, click Submit New Issue, on this special issue template.
Alternately, use the new torbb command:
`shell`
$ git clone https://github.com/BrowserBox/BrowserBox.git
$ cd BrowserBox
$ yes | ./deploy-scripts/global_install.sh localhost
$ setup_bbpro --port
$ torbb
-----
š We're excited to announce that BrowserBox can now run as a hidden service on the Tor network! This significant update brings enhanced privacy and security, allowing you to access BrowserBox with the anonymity of Tor. Check out our Show HN post: torbb - Now with Tor, run BrowserBox as a hidden service.
-----
New Video: Installing BrowserBox on Amazon AWS EC2 Amazon Linux
General install instructions:
`shell`
git clone https://github.com/BrowserBox/BrowserBox.git
cd BrowserBox
./deploy-scripts/global_install.sh
setup_bbpro --port
bbpro
-----
November 4 2023: New version released. Docker image v6.
First ensure you have docker installed and running! :) Then run:
`console`
PORT=8080 # or your preferred port
bash <(curl -s https://raw.githubusercontent.com/BrowserBox/BrowserBox/734235d3c85ad0c48f0209fcb67474ad05bcffdb/deploy-scripts/run_docker.sh) $PORT
That's it! Follow the prompts to set up certificates and it will emit a link that you can send open in any web browser.
Update: Docker image now works on macOS!!! š
-----
HOLD UP You need to fork or generate this repo first, so you have your own copy. Then open an issue and you will be guided through the process (1 manual step, rest is automatic), while your browser VPN is created.
By default they remain open for 5 minutes, but you can make that longer by editing the workflow YAML file. Each minute used counts against your GitHub actions quota. Also, don't do anything abusive with this, remember you are browsing the web from inside GitHub's infrastructure (actions runners), so treat them with respect!
Limitations: no audio, no DevTools, no docviewer (Because the ports are not accesible, although the services are running)
-----
BrowserBox is a leading-edge solution in the Zero Trust landscape, enabling embeddable multiplayer browsers in any web page on any device. Our cybersecurity focus is on ensuring that every web interaction is treated as potentially hostile, and isolating it, so that we protect your devices and network from harm.
Cross-platform support status:
| Platform | Status |
|--------------------------|--------------|
| Docker | ā
|
| Ubuntu | ā
|
| Debian | ā
|
| CentOS 9 | ā
|
| macOS | ā
|
| Amazon Linux (AWS EC2) | ā
|
| Windows\* | ā |
| Windows WSL | ā
|
\*Windows support is currently in development, but not yet officially supported.
Content delivery services status:
| Channel | Browser Service | Audio | Secure Document Viewer | Remote DevTools | WebRTC |
|--------------------------|-----------------------|----------|------------------------|-----------------|--------|
| HTTPS/DNS | ā
| ā
| ā
| ā
| ā
|
| Installed Web App (PWA) | ā
| ā
| ā
| ā
| ā
|
| Tor Hidden Service | ā
| ā
| ā
| ā
| ā |
| SSH Tunnel | ā
| ā
| ā
| ā
| ā
|
| ngrok* | ā
| ā | ā | ā | ā
|
\*audio, doc viewer, remote devtools not currently configured to work with ngrok, but support will be added in future.
By leveraging the principles of Remote Browser Isolation (RBI), real-time streaming and collaborative browserin (co-browsing or "multiplayer browsers"), BrowserBoxPro ensures that no web content directly interacts with the end user's device, while remaining accessible through a shareable, collaborative interface.
This guide will walk you through the seamless integration of BrowserBoxPro into your Zero Trust architecture.
- BrowserBox: Zero Trust Browsing
- Embracing Zero Trust with BrowserBox
- Key Features
- Deploying BrowserBoxPro in a Zero Trust Environment with Docker
- Zero Trust Installation Guide
- Installation
- Initial Machine Setup
- Installation Process
- Applications in a Zero Trust Framework
- Product Space Applications
- Creative Ways that Clients are Using BrowserBox
- Internal Tooling Applications
- Tech and Framework Applications
- Features of BrowserBox Pro in a Zero Trust Environment
- Licensing for Zero Trust
- Purchasing a commercial license
- Hardware Appliance (OEM) Licensing
- Sanctions Compliance
- Licensing Summary
- Pricing
- Elevate Your Zero Trust Strategy with BrowserBoxPro
- Copyright
In the evolving cybersecurity landscape, the Zero Trust model has emerged as a cornerstone. By assuming no trust by default and verifying every access request irrespective of its source, Zero Trust ensures robust security. BrowserBoxPro is at the forefront of this paradigm shift, offering:
- Web Isolation: Every web session is isolated, ensuring malicious content doesn't reach the end-user's device.
- Co-Browsing: Collaborative browsing without compromising security.
- Zero Trust Integration: Easily integrates into your existing Zero Trust infrastructure.
For the latest on how BrowserBox is shaping the Zero Trust landscape, visit our Company Blog.
- Updated Pricing - now with even more tiers for smaller use cases!
- BrowserBox Pro Goes Open Source with Multiple Licenses
- Tunnelling over SSH - You're guide to using Localhost Certificates and SSH port-forwarding to run BrowserBox Pro on a remote machine without a domain name, using SSH tunneling
- Advanced Streaming: BrowserBoxPro offers advanced streaming capabilities, allowing you to seamlessly browse websites, stream videos, and access web applications with superior performance.
- Enhanced Feature Set: Enjoy a wide range of enhanced features that enhance your browsing experience, including improved security, customizable settings, and optimized resource management.
- Superior Performance: BrowserBoxPro delivers exceptional performance, ensuring smooth and responsive browsing even for resource-intensive websites and applications.
- Flexible Usage: Whether you are a non-commercial user or using BrowserBoxPro for commercial purposes, you can benefit from the full range of pro features to enhance your browsing capabilities.
Before diving in, ensure you have docker installed!
Deploying BrowserBoxPro within a Zero Trust framework is straightforward:
1. Obtain the latest Docker container for BrowserBoxPro from our packages page on GitHub Container Registry.
2. Deploy the Docker container using our Zero Trust compliant run script. Choose a primary port number ($PORT) ensuring two extra ports are free both preceding and succeeding $PORT. Deploy by running:
`console`
PORT=8080 # or your preferred port
bash <(curl -s https://raw.githubusercontent.com/BrowserBox/BrowserBox/2034ab18fd5410f3cd78b6d1d1ae8d099e8cf9e1/deploy-scripts/run_docker.sh) $PORT
Upon successful deployment, BrowserBoxPro will be operational, reinforcing your Zero Trust strategy. Access the browser using the provided login link: https://.
For support or to purchase licenses, connect with us at sales@dosyago.com or visit: https://dosyago.com.
š Video Installation Guide for Pro: https://youtu.be/cGUJCCPDWNE
For detailed information and progress updates, please refer to the official documentation.
Follow these instructions to install BrowserBoxPro on your system.
Before installing BrowserBoxPro, ensure that your system meets the following requirements:
- Debian VPS with 1 cores, 1 GB RAM, and 25 GB SSD (e.g. Nanode from Linode)
- At least 5 Mbps internet connection
- A public hostname with a DNS A record pointing to your VPS's IP address, or localhost certificates installed on your local and remote machine (for example using mkcert)
First, update your distribution:
apt update && apt -y upgrade
And install a few basic tools:
apt install curl git wget
Now, prepare the machine by following these steps:
1. Create a new user to operate BrowserBoxPro:
`
adduser pro
2. Disable the password for the newly created user:
`
usermod -L pro
3. Create a new group for sudo privileges:
`
addgroup sudoers
4. Add the following line to the sudoers file to avoid entering a password for sudo operations:
`
%sudoers ALL=(ALL) NOPASSWD:ALL
Use the command to edit the sudoers file.
5. Grant sudo privileges to the user:
`
usermod -G sudoers pro
Switch to the pro user by executing the following command:`
sudo -u pro bash
Follow these steps to install BrowserBoxPro:
1. Clone the BrowserBoxPro repository:
`
git clone https://github.com/dosyago/BrowserBoxPro
2. Navigate to the cloned repository:
`
cd BrowserBoxPro
3. Run the global installation script, replacing with your domain name that points to the machine you're setting up (if you want to use it without a domain name, just use localhost here for the domain name, but you'll still need to copy the correct mkcert localsthost certificates to $HOME/sslcerts later):`
./deploy-scripts/global_install.sh
4. Start the main service on port 8080 and generate the login link:
`
setup_bbpro --port 8080
5. Launch BrowserBox:
`
bbpro
During the installation process, BrowserBoxPro will automatically install the required dependencies and configure the necessary settings.
BrowserBoxPro isn't just a tool; it's a comprehensive solution designed to fit seamlessly into a Zero Trust architecture. Here's how:
- Remote Browser Isolation: Fundamental to Zero Trust, ensuring no direct content interaction with user devices.
- Co-Browsing: Collaborate without compromising on security.
- VPN Alternatives: A more secure solution than traditional VPNs.
- Email Threat Mitigation: Content Disarm & Reconstruction (CDR) ensures safe email attachments.
- Secure Web Interaction: A user-friendly UI for secure third-party processes.
- A user-friendly UI that allows clients to perform 3rd-party processes without leaving your website.
- A fully customizable online hosted web browser that provides an alternative to downloadable browsers.
- The ability to record web app interactions to document bugs by capturing the event stream and viewport.
- A mechanism to create visual "How-To" guides illustrating key user stories.
- A tool for human-in-the-loop intervention to resolve stuck browser automation jobs and identify "selector drift" and script-page mismatch issues.
- A robust web proxy to seamlessly integrate 3rd-party processes lacking APIs.
- An interactive console to inspect, observe, and interact with browser automation tasks.
- A browser that can be automated, offering effective evasion of bot detection mechanisms that target pure headless Chrome.
- A scriptable console and interactive simulator for automation tasks, creating an intuitive feedback loop.
- An open web tag.
- An