Posted by: Anonymous Coward
on January 27, 2006 11:43 AM
.. wrong about one thing. Anonymous Reader is NOT an isolated case.
In fact, I would bet that anyone who does remote command line work at all is probably connecting to more than two or three machines in any given week.
I know that you CAN set up PKI, and that after that, its a little bit more convenient. But as you admit, this is only convenient if you only ever work with the same 2 or 3 machines, and those machines don't get rebuilt too often.
My experience is quite different to that, so the overhead of setting up and using PKI can easily outweigh the difficulty of using passwords that I'm already familiar with. Usernames and passwords have to be set up anyway. Once you have a login, you also automatically have password-based ssh connection. To me that is the easiest thing. You also mention security but again, I think you are not covering all possible scenarios. There are certainly scenarios (think isolated LAN) where security is a completely different problem from say, connecting across the internet. And yet ssh is useful on either.
As a result of this article, I will be looking more deeply into ssh - both in pipes, and in scripts - but there are a number of options I will explore before I look at PKI.
Are you sure, mkrenz, that it is not you that is the special case?
Learn about Linux
Download Linux
Get Linux help
Re:Sorry, mkrenz, but you are wrong ..
Posted by: Anonymous Coward on January 27, 2006 11:43 AMIn fact, I would bet that anyone who does remote command line work at all is probably connecting to more than two or three machines in any given week.
I know that you CAN set up PKI, and that after that, its a little bit more convenient. But as you admit, this is only convenient if you only ever work with the same 2 or 3 machines, and those machines don't get rebuilt too often.
My experience is quite different to that, so the overhead of setting up and using PKI can easily outweigh the difficulty of using passwords that I'm already familiar with. Usernames and passwords have to be set up anyway. Once you have a login, you also automatically have password-based ssh connection. To me that is the easiest thing. You also mention security but again, I think you are not covering all possible scenarios. There are certainly scenarios (think isolated LAN) where security is a completely different problem from say, connecting across the internet. And yet ssh is useful on either.
As a result of this article, I will be looking more deeply into ssh - both in pipes, and in scripts - but there are a number of options I will explore before I look at PKI.
Are you sure, mkrenz, that it is not you that is the special case?
#