In the client-server architecture used by the SSH protocol, a client can authenticate by providing a tunneled clear text password or by using a public/private key pair: this is called public key authentication. A user who logs in via a public key on a remote machine has complete access to the command line; in certain situations, however, it may be useful to associate a public key to a single specific command, for security reasons.
Quick response (QR) codes have surged in popularity over the last few years. They are an efficient way to share websites, wireless logins, app downloads, or even rewards programs at restaurants, and other things. You may have a use for them on a Linux system if you want to generate your own QR code as a quick way to share one of the previous examples or some other kind of information. To make your own QR code, you will need to download a QR code generator. In this tutorial, we have compiled a list of our favorite QR code generators for Linux. Check out our picks below to find one that suits you best.
Everything running on a Linux system is a process, either taking place in the foreground (visible to the user) or in the background (unapparent processes like system services). There are various states that a process can be in, those being running, uninterruptable sleep, interruptable sleep, stopped, and zombie. But what is a zombie process?
Hex editors allow users to edit a binary file after it has already been compiled. Ordinarily, you should make changes to a program by editing the source code and compiling it into an executable file. But if you do not have access to the source code, it is still possible to change various bytes of data of the compiled file, in the hopes that your edit will yield the desired results. This is a hacky solution that can be used for both honest and nefarious purposes.
It may be necessary to configure Linux IP forwarding on a Linux system in certain scenarios. If the Linux server is acting as a firewall, router, or NAT device, it will need to be capable of forwarding packets that are meant for other destinations (other than itself). Linux uses the net.ipv4.ip_forward kernel variable to toggle this setting on or off.
Everyone, nowadays, has several accounts and credentials to take care of, that’s why everyone needs a decent and possibly open source password manager. When it comes to managing passwords there are many choices available on Linux: in the past, for example we talked about “pass”, a great, command line oriented, password-manager based on standard tools such as GPG and git. In this article we explore an alternative which can be the ideal solution for individuals and small organizations: Vaultwarden.
When it comes to software deployment and development, Kubernetes has quickly risen in popularity as being one of the best tools for managing containerized applications at scale. The best way to squeeze the most performance and stability out of your Kubernetes cluster is, you guessed it, to run it on top of a Linux system. Linux has a proven track record of decades of stability in running the most demanding applications, and Kubernetes proves to be no exception. In this tutorial, we will look at the ways Linux and Kubernetes make a good combo in running a large cluster of applications at scale.
Container orchestration technology has become one of the best ways to create a cluster of fault tolerant and highly scalable applications. Currently, the two biggest names in the field are Kubernetes and Docker Swarm. Both are software that can create and manage a cluster of containerized applications.
Linux administrators can build a cluster with Kubernetes and deploy containerized apps inside of it. Kubernetes makes it easy to scale your containerized applications, keep them up to date, and it also provides fault tolerance by distributing the workload across numerous nodes. Installing minikube is one of the simplest methods to begin using Kubernetes.
Kubernetes is container orchestration software that allows us to deploy, manage, and scale containerized applications. Even though Kubernetes has a reputation for being highly reliable, the need to restart it may arise, just like it sometimes does for any other application or service. Kubernetes is split into different components that can all be restarted individually, so that other parts can continue running uninterrupted. Ideally, you should only restart the component you are troubleshooting.
Running a Kubernetes cluster can consume an incredible amount of system resources, depending on the size of your cluster, the services you are running, how many replicas are needed for scaling, and what kind of cluster you decide to launch (for example, kubeadm or minikube). Then again, a small cluster may consume next to no resources. Since there is so much variance in Kubernetes clusters, it can be hard to ascertain the system requirements for running one.
When getting started with Kubernetes, the jargon alone can be the source of a big learning curve. Words like pods, services, deployments, clusters, applications, nodes, namespaces, and many more all get tossed around constantly, and it can be impossible for a newcomer to even keep up with what is being said. Not to mention that after learning the basic terminology, it is a whole other subject to learn how all of these components fit in together to serve a Kubernetes cluster.