Outside of his technical support engineer role at Loadbalancer.org, Neil is a keen motorcyclist and ham radio operator. He brings together an interesting mixture of Linux systems administrator, technical support engineer, and software tester.
TLS encryption (formerly known as SSL encryption) is used to improve the safety of data exchanged over a network. But where should it sit in your network architecture?
Hypervisors such as Hyper-V and VMWare ESXi have the ability to import disk images within their graphical WebGUI. However, Proxmox unfortunately lacks this feature.
All Secure Web Gateways require client IP transparency in order to implement any proper kind of security and authentication. Which can be a real pain if you have a load balancer in the middle.
We’re often asked how to configure our load balancer to protect both web servers and users.
In the early days of the Internet, there was very little encrypted traffic. People simply trusted that nobody was out to get them. But later on, security and encryption became an important part of online life.
It’s no big secret that a single processor can only handle so much processing in a given time. So what happens when you reach the limits of what a single processor can handle? Simple, you add more processors.