PrestaShop 1.7.3 is now available
PrestaShop announces the new 1.7.3 version, which includes improvements and new features.
Among the new features introduced we find:
PrestaShop 1.7.3 is available at this address.Read more CMS Bulletin - April 2018
Kontena joins the Open Container Initiative
Kontena joins the Open Container Initiative (OCI).
Kontena is an open-source solution that allows you to manage containers in production, in a manner similar to Kubernetes.
It includes capabilities of high-availability, affinity rules, health check, orchestration, on-demand volume creation, multi-host networking, multicast and hybrid cloud support, VPN access, Let's Encrypt secrets and certificates, role-based access control, load balancing, SSL termination, automatic scaling, support for Docker Compose, service discovery, monitoring and logging with support for FluentD and StatsD, CLI, shells and WebUI and stack and image register.
The Open Container Initiative is a project of the Linux Foundation launched in 2015 by Docker, CoreOS and other leaders in the container sector that aims to create open standards regarding container format and runtime. It includes members such as Docker, CoreOS, VMware, Red Hat, SUSE, Oracle, OpenStack, Intel, Mesosphere, Google, AWS and, indeed, Kontena.
Google Cloud: 96 vCPU instances and support for Windows containers
Google Cloud announces new instances with 96 vCPUs.
Instances can have up to 624GB of RAM and Intel Xeon Scalable Processors (Skylake) with the AVX-512 instruction set and are available in the us-central1, northamerica-northeast1, us-east1, us-west1, europe-west1, europe-west4, and asia-east1, asia-south1 and asia-southeast1.
Furthermore, support for Windows containers (available via Docker) is announced by means of optimized VM images.
Mirai variant turns IoT devices into proxy servers
Fortinet has identified a variant botnet of Mirai, the famous botnet responsible for attacks to DynDNS and KrebsOnSecurity, in addition to DDoS attacks turns infected IoT devices into proxy servers.
The botnet, called Mirai OMG, installs a malware on the victim systems that generates two random ports, adds the appropriate firewall rules, then installs 3proxy, a minimal proxy server.
Fortinet has not detected botnet attacks, analyzed in a quiescent state, and the authors are supposed to sell access to IoT proxy servers.
The first week of the new year was characterized by the appearance of two major flaws in processors, the so-called Meltdown and Spectre announced by Google ProjectZero in this post, which afflict most of computers and devices in use today. The impact has been outstanding in terms of media coverage, and the topic has been the subject of discussion not just among IT professionals.
Meltdown and Spectre briefly
Meltdown and Spectre are two distinct vulnerabilities that affect computer processors: not just servers, laptops and desktops but also micro-computers, specialized computers and IoT devices. They were discovered by four different research teams who reported them to CPU manufacturers, several months prior the publication of the news; but these vulnerabilities are not new, in fact they have existed for decades. No computer with a processor produced in the last 20 years is to be considered immune and safe; a dedicated tool for Linux and BSD is available and provides information on the system status, and a similar tool for Windows exists too.
We are not aware of known attacks: antivirus can detect the code responsible for an attack, but not the vulnerability itself.
Previous article -> Introduction to Docker - pt.1
Images and Containers
An image is an ordered set of root filesystem updates and related execution parameters to be used in a container runtime; it has no state and is immutable.
A typical image has a limited size, doesn’t require any external dependency and includes all runtimes, libraries, environmental variables, configuration files, scripts and everything needed to run the application.
A container is the runtime instance of an image, that is, what the image actually is in memory when is run. Generally a container is completely independent from the underlying host, but an access to files and networks can be set in order to permit a communication with other containers or the host.
Conceptually, an image is the general idea, a container is the actual realization of that idea. One of the points of strength of Docker is the capability of creating minimal, light and complete images that can be ported on different operating systems and platforms: the execution of the related container will always be feasible and possible thus avoiding any problem related to the compatibility of packages, dependencies, libraries, and so forth. What the container needs is already included in the image, and the image is always portable indeed.Read more Introduction to Docker - pt.2
GURU advisor will be at the Mobile World Congress in Barcelona from February 22nd to 25th 2016!
MWC is one of the biggest conventions about the worldwide mobile market, we'll be present for the whole event and we'll keep you posted with news and previews from the congress.Read More