Book Image

Puppet 3: Beginner's Guide

By : John Arundel
Book Image

Puppet 3: Beginner's Guide

By: John Arundel

Overview of this book

<p>Everyone's talking about Puppet, the open-source DevOps technology that lets you automate your server setups and manage websites, databases, and desktops. Puppet can build new servers in seconds, keep your systems constantly up to date, and automate daily maintenance tasks. <br /><br />"Puppet 3 Beginner's Guide" gets you up and running with Puppet straight away, with complete real world examples. Each chapter builds your skills, adding new Puppet features, always with a practical focus. You'll learn everything you need to manage your whole infrastructure with Puppet.<br /><br />"Puppet 3 Beginner’s Guide" takes you from complete beginner to confident Puppet user, through a series of clear, simple examples, with full explanations at every stage.</p> <p>Through a series of worked examples introducing Puppet to a fictional web company, you'll learn how to manage every aspect of your server setup. Switching to Puppet needn't be a big, long-term project; this book will show you how to start by bringing one small part of your systems under Puppet control and, little by little, building to the point where Puppet is managing your whole infrastructure.</p> <p>Presented in an easy-to-read guide to learning Puppet from scratch, this book explains simply and clearly all you need to know to use this essential IT power tool, all the time applying these solutions to real-world scenarios.</p>
Table of Contents (17 chapters)
Puppet 3 Beginner's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Access control


Having created the user's account, we now need to provide a secure way for him to log in. We can do this using the SSH protocol.

What is SSH?

SSH is a more secure way of controlling user access than the traditional "username and password" approach. Instead of using a password, which the user has to keep secret, it uses two pieces of information: the public key and the private key. Only the private key has to be secret. You can put your public key on any computer, or publish it to the world if you like. But no one can log in to an account controlled by your public key unless they also have the matching private key.

This has the pleasant consequence that you only need one SSH key, and you can use it for everything. It's a very bad idea to use the same password for multiple accounts, but with SSH, that's no problem. So long as you keep the private key secret, you can use your public key everywhere.

Managing SSH keys

Puppet can manage SSH public keys and authorize them for user accounts...