So the password wasn’t originally invented for security. So finally you could have multiple users getting the most possible out of the mainframe. Multiple users could now connect to the same system and the idle time of users could be used as active time for another user. So Fernando and his team were tasked with solving this problem, and they came up with his concept of time-sharing. We’re not actually using the CPU on the machine. It wasn’t practical to have developers connected to the mainframe all the time, because most of the time, what are we doing? We’re typing, we’re thinking about things, we’re refactoring. So these programs were put in a queue, and in the early days, they were run in serial, which means you had to wait days or hours for your program to run, and come back later to get the results. So think about that next time you go to deploy your code, bringing a giant box of punch cards and dropping it on the sysadmin’s desk. Users would write their programs on punch cards, and then submit the punch cards to the operators to run. These powerful machines were big and expensive to run. You see, back in those days, computers were these giant, hulking machines that filled entire rooms. And he’s also known as the inventor of the modern computer password. He’s one of the pioneers of time-sharing computer systems, and he led the team that developed the first compatible time-sharing system for mainframes. This dashing gentleman is Fernando Corbató. So, why do we participate in this crazy ritual every few months, and how did we get here? Most importantly, who can we blame? I did some research, and I tracked down the inventor of the modern computer password. I’m going to do it this afternoon, I promise.” Nobody likes this, right? And this is just 1 password on 1 machine. Why can’t I just keep the password I have? I really like my password. A day may come when I change this password, but today is not that day. I can still get 2 more weeks use out of it, and after all it took me 3 weeks just to memorize the darn thing. The pain of changing passwordsĭoes anybody else do this? I do this. Let’s be honest, all right? Nobody came to this talk because you like changing passwords, right? Did we all wake up this morning and go, “I’m going to change my password today.” No. There’s nothing to make you feel old like seeing your childhood toy in a museum. Do a pilgrimage to the Living Computer Museum. I highly recommend, if you’re ever in Seattle, go pay this place a visit. This is taken at the Living Computer Museum in Seattle. Vintage, or heritage systems, right? This is a fairly recent photo, but that is a Commodore 64 in the photo. I like building things, so now I travel and help users get started with HashiCorp tools. Today I’m a solutions engineer with HashiCorp. My name is Sean Carolan, and I’m a former or recovering systems administrator. Sean Carolan Solutions Engineer, HashiCorp HashiCorp solutions engineer Sean Carolan demonstrates some of the ways you can clean up and automate your password management with Vault.
#Vault password manager windows#
Using built-in tools that you already have installed on your servers (Bash or Powershell), you can automatically generate secure passwords for Linux or Windows servers and store them safely in Vault. Thankfully, Vault is a system that automates away most of the headaches associated with key and password rotation.
Password management is a thorn in the side of many sysadmins. Credentials are often shared by multiple users, or the same username and password can be used to access multiple systems.
#Vault password manager how to#
For more in-depth tutorials and documentation for how to use HashiCorp Vault for password rotation, visit the Vault track on HashiCorp Learn.
0 kommentar(er)
