Server, agent, and web-ui
# get build-essentials
apt-get install build-essential
# get server
wget http://www.ossec.net/files/ossec-hids-2.6.tar.gz| * | |
| / \ | |
| / \ | |
| +_/ / / | \ \ \_+ | |
| ||*|||*|| | |
| |+||*||+| | |
| / \ | |
| +_/ / / | \ \ \_+ | |
| ||*|||*|| | |
| |+||*||+| |
$ bundle install --deployment
You are trying to install in deployment mode after changing
your Gemfile. Run `bundle install` elsewhere and add the
updated Gemfile.lock to version control.
You have added to the Gemfile:
* source: rubygems repository https://[email protected]/me/, https://rubygems.org/| Title: DiscordCanary crashed with SIGSEGV in _XReply() | |
| SegvAnalysis: | |
| Segfault happened at: 0x7f73b6eb6b5d <clone+109>: mov %rax,%rdi | |
| PC (0x7f73b6eb6b5d) ok | |
| source "%rax" ok | |
| destination "%rdi" ok | |
| Stack memory exhausted (SP below stack segment) | |
| SP (0x7f73aafb8cc0) ok | |
| Reason could not be automatically determined. |
| // Package main is intended to provide a working example of how to properly | |
| // read from a net.Conn without losing data or integrity. The data is generated | |
| // from alphabetical characters rather than simply rand to prevent the | |
| // generation of an `EOF` | |
| package main | |
| import ( | |
| "crypto/md5" | |
| "fmt" | |
| "io" |
| # Install older linux kernel (extras for docker) | |
| apt-get install -y linux-image-4.4.0-53-generic linux-image-virtual linux-image-extra-4.4.0-53-generic linux-image-virtual | |
| # Point to desired kernel entry (from /boot/grub/grub.cfg) v menuentry within submenu | |
| sed -i 's|GRUB_DEFAULT.*|GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 4.4.0-53-generic"|g' /etc/default/grub | |
| # ^From grub.cfg:17 ^menuentry title from grub.cfg:53 | |
| # Generate new grub.cfg | |
| update-grub | |
| # Reboot into specified kernel |
This guide assumes you have a remote dev server set up and have deploy[ed] dry-run, as well as added the mytest.dev dns alias to the dry-run environment
Create a config file for portal
portal.json{ "api-token": "123", "api-host": "0.0.0.0", "api-port": 8443,
>> "just-proxy": true,
This requires two apps that you own/have access to. For clarity, we'll refer to the app with the shared database as the "server" app, and the one wanting to connect, the "client" app. This is not recommended nor supported by nanobox.
Note: You'll need to ensure NANOBOX_USERNAME and NANOBOX_PASSWORD are set on your "client" app
Fetch the nanobox binary. Run from your client component(s) in your client app