https://www.vultr.com

The Everywhere Cloud

Deploy an instance.
Accelerate your application.


Terms and Conditions

By -

1. GENERAL PROVISIONS

By accessing or using this website or any of its contents, you hereby agree to these terms and conditions, and consent to be bound by it. If you do not agree, you should not access or use this website.

The authors of this website reserve the right to change these terms and conditions at any time without prior notice. Your continuance in accessing or using this website signifies your acceptance and agreement with these terms and conditions.

The authors of this website reserve the right to change its contents, and to restrict, withdraw, cancel, disconnect, deactivate, suspend or discontinue any or all of its contents without prior notice.

2. COPYRIGHT AND FAIR USE

This website is operated as a free service for the public. Some materials contained herein, however, are protected by copyright. You must abide by all the copyright notices or restrictions set by their respective copyright holders accordingly.

2.1. ORIGINAL WORKS

The use and distribution, with or without modification, of the intellectual properties of the authors of this website are subject to the following conditions:

2.1.1. For non-commercial purposes, the authors and this website must be properly credited as the source of the materials.

2.1.2. For commercial purposes, prior written permission from the authors must be sought before accessing any of the materials.

2.2. OTHER WORKS

The authors of this website duly recognize and acknowledge, and have no intent of infringing on, the intellectual property ownership of other copyright holders of their respective materials.

The authors of this website invoke the concept of fair use for educational and research purposes, in the interest of broadening the public's knowledge by making these materials easier to find on the Internet.

3. DISCLAIMER

The authors of this website make no representations with respect to the accuracy, credibility, validity, usefulness, timeliness, and completeness of the materials, any other works herein, or any of the third-party websites linked through it.

THIS WEBSITE AND ITS CONTENTS ARE PROVIDED BY THE AUTHORS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS WEBSITE AND ITS CONTENTS, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Therefore, by accessing or using this website or any of its contents, you shall do so at your own risk.

END OF TERMS AND CONDITIONS

Comments

Post a Comment

Popular posts from this blog

Enabling HTTPS in Home Assistant

By -
Image
The following procedure activates HTTPS for the Home Assistant server. The secure protocol uses TLS/SSL certificates to encrypt the data transferred between user and server. Although it is possible to make this home automation system, whether in  Linux or  FreeBSD , accessible over the Internet, Home Assistant is usually operated within private networks, either physical or virtual. In this case, self-signed certificates may be acceptable to use and quicker to deploy. ========== 1. Log in as the system account. 1.1. Linux, with $HOME "bin" included in $PATH (-i) of system account (-u). user@host: $ sudo -i -u homeassistant 1.2. FreeBSD, coming from "root" superuser. root@host: # su - homeassistant 2. Go to the Home Assistant configuration directory. user@host: $ cd ~/.homeassistant 3. Make a directory for SSL certificates. user@host: $ mkdir ssl 4. Ensure that only the system account and members of its group can access the directory. user@host: $ chmod 7
Read more

Configuring the FreeBSD Firewall with IPFW

By -
Image
IPFW is one of several firewalls included in FreeBSD by default. It has a command-line tool to handle the policies for incoming and outgoing connections. In the configurations discussed here, network connections "from any to any" are deliberately avoided to prevent potential bounce attacks from happening, if the server is not intended to act as a router. Instead, a request/respond or incoming/outgoing rule pair is adopted to direct the flow of network traffic. The main objective is to set up IPFW to block unauthorized remote access to unsecured ports on the server. But if attackers manage to break in through a vulnerability on some programs running on authorized incoming ports, the outgoing restrictions will prevent massive data exfiltration, stopping intruders dead in their tracks. A similar approach can be done on Debian-based Linux distributions using UFW . ========== 1. STRICT CONFIGURATION 1.1. Create a custom shell script for IPFW commands. root@host: #  ee /etc/myip
Read more

Running Home Assistant on FreeBSD Servers

By -
Image
Home Assistant is an open-source home automation system powered by Python, primarily intended to run on single-board computers like the Raspberry Pi, with Linux as the host operating system. The following procedure shows how to run Home Assistant Core on FreeBSD servers, on either physical or virtual machines. ========== 1. PREPARING THE SERVER 1.1. Update the package list and upgrade the existing packages. root@host: # pkg update && pkg upgrade -y 1.2. Install Python and other required packages. root@host: # pkg install python38 py38-sqlite3 openssl autoconf libffi rust 1.3. Create a system account with disabled login (-w no), a dedicated home directory (-m), and some informational text (-c comment). root@host: #  pw useradd homeassistant -w no -m -c "Home Assistant" 1.3.1. If groups for hardware input/output are present, append the system account. Else, skip this step for now. root@host: #  pw groupmod gpio -m homeassistant root@host: #  pw groupmod i2c -m homeassis
Read more