SSH - fish, sftp - will settle for anything

[mzilikazi]

Now if I have to delete some key file or whatnot on the one machine every time I want to ssh into it from the other it sort of defeats the purpose and I am back to running up and down the stairs, no? Or can I keep the same key through reboots (if I only use one linux maybe on that downstairs puter?) My coworker says I could do something with a static IP but it is getting to be a bit beyond my level of expertise (none)

Heheh no you do not need to do that every time. You apparently re-ran the fix-ssh script which overwrote your ssh key. Now when you try to log in ssh does what it was meant to do. It tells you that something has changed (and it has).

ssh keeps a list of known hosts (/home/nishtya/.ssh/known_hosts). If a known hosts tries to connect again it references /home/nishtya/.ssh/known_hosts.

So you can basically start from scratch like so:

On each box do: rm -rf /home/nishtya/.ssh/known_hosts

Then ssh [email protected] and it will creat a new known_hosts file.

[nishtya]

it's possible. What is even weirder is though behind a router, I woke up this morning and these two machines had two different IP addresses from the night before

Afraid all this work is moot though, tonight or tomorrow morning I have to do a fresh install. I lost printer. This is the first time I haven't been able to repair it. It has happened before here and there through updates. I even did a whole dist upgrade in the hopes of getting it back but nada. I backed up my data and here I go again. This has to be the most singularly aggravating thing about linux. Something that was fine goes poof after some upgrade. And you're screwed.

[mzilikazi]

it's possible. What is even weirder is though behind a router, I woke up this morning and these two machines had two different IP addresses from the night before

Afraid all this work is moot though, tonight or tomorrow morning I have to do a fresh install. I lost printer. This is the first time I haven't been able to repair it. It has happened before here and there through updates. I even did a whole dist upgrade in the hopes of getting it back but nada. I backed up my data and here I go again. This has to be the most singularly aggravating thing about linux. Something that was fine goes poof after some upgrade. And you're screwed.

Dunno what to tell ya except that I have a box that started with woody back in 2002 and has been upgraded to sarge and never reinstalled. It works flawlessly.

Maybe give the upgrades a rest? You really only need to upgrade if a package needs a security fix or if it has a new functionality that you want/need. That's why Debian comes in multiple flavors.

[nishtya]

It isn't like I do upgrades for the sheer thrill of it :P generally I want a newer version of some proggie I like and it brings in the whole enchilida of dependencies (think KDE here). I usually go for the update if something I use has an annoying glitch (again, think KDE here) or there is new functionality. Then you get into the whole chicken&egg thing or is it shoe & nail

I held onto BH4 for ages in unstable debian terms (2-3months ) but finally gave in for something or another. If it wasn't for my fondness of KDE apps I probably could make do with far fewer upgrades.