Re: [PLUG] Running a Python application in the background

On 02/23/2017 08:16 PM, Thomas Groman wrote: > If your going to learn a new terminal multiplexer; make it TMUX. TMUX is > like screen but is a little more featured, less conflicting key > sequences, multi-user support, and more actively developed. > This must be one of them there "alternative

Re: [PLUG] Running a Python application in the background

On Thu, 23 Feb 2017, Galen Seitz wrote: > Traditionally this was done using nohup, but screen is probably a better > choice. Galen, I saw a reference to nohup but didn't pursue i. I forgot about screen. Thanks, Rich ___ PLUG mailing list

Re: [PLUG] Running a Python application in the background

On Fri, 24 Feb 2017, King Beowulf wrote: > Screen stable tag v4.5.0 2016-12-07 > http://git.savannah.gnu.org/cgit/screen.git > > Tmux v2.3 Sep 29, 2016 > https://github.com/tmux/tmux/releases > > Tmux and Screen have very similar functionality and most differences are a > matter of subjective

Re: [PLUG] Running a Python application in the background

On Thu, 23 Feb 2017, Thomas Groman wrote: > If your going to learn a new terminal multiplexer; make it TMUX. TMUX is > like screen but is a little more featured, less conflicting key sequences, > multi-user support, and more actively developed. Thanks, Tom. I now see I need to look carefully

Re: [PLUG] Running a Python application in the background

On Thu, 23 Feb 2017, Tom wrote: > I'd second the use of screen as that will allow you to reconnect with the > shell where you started the command should you need it. Another > alternative to nohup I often use: at -f commandToRun now The dependency is > to start atd.service > The advantages to

Re: [PLUG] boot filled

On 02/24/2017 07:57 AM, Denis Heidtmann wrote: > The last time this happened Tomas told me what to do, but I did not write > it down and my mind is a sieve. What is the solution? There are 9 > archived images. How do I safely throw out the older ones? > > Thanks, > -Denis Howdy. You don't

Re: [PLUG] Remote host lost ssh key verification [UPDATED]

On Fri, Feb 24, 2017 at 2:53 PM, King Beowulf wrote: > On 02/24/2017 02:16 PM, Rich Shepard wrote: > > On Fri, 24 Feb 2017, King Beowulf wrote: > > > >> for ssh or scp (cp over ssh), you only need one pub key for the > >> connection to work. NOT the ones in /etc/ssh. One

Re: [PLUG] Looking for Recruiter Recommendations

Have to give it some thought... I recall applying for a field service job servicing automatic barriers, like those used in secure facilities and embassies. The ones that pop up out of the ground. I submitted my resume on line, two minutes go by and I get a call, "can you come to our office in

Re: [PLUG] scp issue

On Fri, 24 Feb 2017, bro...@netgate.net wrote: > Just delete the entry from the known_hosts file. Should do the trick. Deleted ~/.ssh/known_hosts and tried to scp: $ scp salmo:projects . The authenticity of host '[salmo]: ([192.168.55.1]:21498)' can't be established. ED25519 key

[PLUG] Remote host lost ssh key verification

An attempt to scp directories to a laptop from the workstation failed because ssh saw a changed public key in known_hosts. How this happened I've no idea, but it needs fixing, perhaps by copying the correct ecdsa public key from the workstation to the laptop. On stackexchange I read that

Re: [PLUG] Remote host lost ssh key verification

On Fri, 24 Feb 2017, Rich Shepard wrote: > Advice on finding the reason ssh became FUBAR and fixing the problem is > needed. The situation is more confusing. I copied the two public keys from the workstation to the laptop. Initially, scp asked if I wanted to trust the connection and I

Re: [PLUG] boot filled

If you use ubuntu, you could use something like ubuntu-tweak or synaptic to let you select the kernels in a gui and delete them. If you are not on ubuntu, or prefer command line you can get the name of your current kernel uname -r list all kernels except what you are currently using dpkg -l |

Re: [PLUG] scp issue

Now you just need the correct public key. Use the -v flag to scp for more output. On Fri, 24 Feb 2017, Rich Shepard wrote: > On Fri, 24 Feb 2017, bro...@netgate.net wrote: > >> Just delete the entry from the known_hosts file. Should do the trick. > > Deleted ~/.ssh/known_hosts and tried to

Re: [PLUG] boot filled

On 02/24/2017 07:57 AM, Denis Heidtmann wrote: > The last time this happened Tomas told me what to do, but I did not write > it down and my mind is a sieve. What is the solution? There are 9 > archived images. How do I safely throw out the older ones? While I don't have an answer to your

Re: [PLUG] Remote host lost ssh key verification

On 02/24/2017 07:33 AM, Rich Shepard wrote: >An attempt to scp directories to a laptop from the workstation failed > because ssh saw a changed public key in known_hosts. How this happened I've > no idea, but it needs fixing, perhaps by copying the correct ecdsa public > key from the

[PLUG] boot filled

The last time this happened Tomas told me what to do, but I did not write it down and my mind is a sieve. What is the solution? There are 9 archived images. How do I safely throw out the older ones? Thanks, -Denis ___ PLUG mailing list

Re: [PLUG] scp issue

Check permissions on .SSH and the files in it. Not at a system I can check to say what they should be. Some one else may be able to. Rod -- On February 24, 2017 08:39:42 Rich Shepard wrote: > On Fri, 24 Feb 2017, bro...@netgate.net wrote: > >> Just delete the

Re: [PLUG] boot filled

This works for me: http://ubuntuhandbook.org/index.php/2016/05/remove-old-kernels-ubuntu-16-04/ On Fri, Feb 24, 2017 at 9:36 AM, David wrote: > On 02/24/2017 07:57 AM, Denis Heidtmann wrote: > > The last time this happened Tomas told me what to do, but I did not write > > it

Re: [PLUG] scp issue

On Fri, 24 Feb 2017, bro...@netgate.net wrote: > Now you just need the correct public key. Use the -v flag to scp for more > output. $ scp -v salmo:projects . Executing: program /usr/bin/ssh host salmo, user (unspecified), command scp -v -f projects OpenSSH_7.4p1, OpenSSL 1.0.2k 26 Jan 2017

Re: [PLUG] boot filled

> On Feb 24, 2017, at 10:19 AM, Tony Schlemmer wrote: > > On Fri, 2017-02-24 at 09:36 -0800, David wrote: >> On 02/24/2017 07:57 AM, Denis Heidtmann wrote: >>> >>> The last time this happened Tomas told me what to do, but I did not >>> write >>> it down and my mind is a

Re: [PLUG] scp issue

On Fri, 24 Feb 2017, Rich Shepard wrote: > debug1: Connecting to salmo [192.168.55.1] port <>. > debug1: Connection established. The two hosts can communicate. > debug1: key_load_public: No such file or directory > debug1: identity file /home/rshepard/.ssh/id_rsa type -1 > debug1:

Re: [PLUG] scp issue

On Fri, 24 Feb 2017, Roderick Anderson wrote: > Check permissions on .SSH and the files in it. Rod, On the desktop: $ ll .ssh total 20 -rw-r--r-- 1 rshepard users 100 Nov 9 08:43 authorized_keys -rw-r--r-- 1 rshepard users 11 Feb 7 2015 config -rw--- 1 rshepard users 464 Oct 30 12:42

Re: [PLUG] boot filled

On Fri, 2017-02-24 at 09:36 -0800, David wrote: > On 02/24/2017 07:57 AM, Denis Heidtmann wrote: > > > > The last time this happened Tomas told me what to do, but I did not > > write > > it down and my mind is a sieve.  What is the solution?  There are 9 > > archived images.  How do I safely

Re: [PLUG] Remote host lost ssh key verification

On Fri, 24 Feb 2017, King Beowulf wrote: > In that case, the only entries that you care about are in "known_hosts" > unless sshd is stopped. As root: > /etc/rc.d/rc.sshd restart Ed, Did this. > $ ssh susan@glaurung It generates the new known_hosts file then denies the connection. >

Re: [PLUG] scp issue

On 02/24/2017 10:50 AM, Rich Shepard wrote: > On Fri, 24 Feb 2017, Rich Shepard wrote: > >> debug1: Connecting to salmo [192.168.55.1] port <>. >> debug1: Connection established. > >The two hosts can communicate. > >> debug1: key_load_public: No such file or directory >> debug1: identity

Re: [PLUG] Remote host lost ssh key verification

On Fri, 24 Feb 2017, King Beowulf wrote: > Are you logging in via username/password or ssh key? Ed, I log into the laptop using username and password. To ssh from one to the other (today's experience is from a laptop to the desktop) I should be asked for my passphrase, not denied the

Re: [PLUG] boot filled

On 02/24/2017 08:36 AM, Dick Steffens wrote: > On 02/24/2017 07:57 AM, Denis Heidtmann wrote: >> The last time this happened Tomas told me what to do, but I did not write >> it down and my mind is a sieve. What is the solution? There are 9 >> archived images. How do I safely throw out the older

Re: [PLUG] boot filled

On Fri, Feb 24, 2017 at 10:56 AM, Bruce Kilpatrick wrote: > > > On 02/24/2017 07:57 AM, Denis Heidtmann wrote: > >> The last time this happened Tomas told me what to do, but I did not > write > >> it down and my mind is a sieve. What is the solution? There are 9 > >> archived

Re: [PLUG] Remote host lost ssh key verification

On 02/24/2017 10:25 AM, Rich Shepard wrote: > On Fri, 24 Feb 2017, King Beowulf wrote: > >> Are you logging in via username/password or ssh key? > > Ed, > >I log into the laptop using username and password. To ssh from one to the > other (today's experience is from a laptop to the desktop)

Re: [PLUG] scp issue

On Fri, 24 Feb 2017, Ken Stephens wrote: > Permissions on my .ssh directory are: > [kens@neptune ~]$ ls -ahl .ssh > total 24K > drwx--. 2 kens kens 4.0K Nov 22 20:24 . > drwx--. 80 kens kens 4.0K Feb 24 08:41 .. > -rw---. 1 kens kens 2.4K Dec 24 15:15 authorized_keys > -rw---.

Re: [PLUG] Remote host lost ssh key verification [UPDATED]

On Fri, 24 Feb 2017, King Beowulf wrote: > On DESTINATION computer: delete ~/.ssh/authorized_keys Ed, That's the problem: there's no public key for this laptop in ~/.ssh/authorized keys! If I copy the laptop's /etc/ssh/ssh_host_ed25519_key.pub to a thumb drive and from there to the

Re: [PLUG] Remote host lost ssh key verification [UPDATED]

On Fri, 24 Feb 2017, Rich Shepard wrote: > That's the problem: there's no public key for this laptop in > ~/.ssh/authorized keys! And, there's no public key for this laptop in the desktop's ~/.ssh/known_hosts. Rich ___ PLUG mailing list

Re: [PLUG] Remote host lost ssh key verification [UPDATED]

On 02/24/2017 01:01 PM, Rich Shepard wrote: > On Fri, 24 Feb 2017, King Beowulf wrote: > >> On DESTINATION computer: delete ~/.ssh/authorized_keys > > Ed, > >That's the problem: there's no public key for this laptop in > ~/.ssh/authorized keys! > >If I copy the laptop's

Re: [PLUG] Remote host lost ssh key verification [UPDATED]

On Fri, 24 Feb 2017, King Beowulf wrote: > Just delete ~/.ssh/known_hosts and it will regenerate from what's in > /etc/ssh Ed, This would wipe out the existing portable in known_host. I think the problem is more basic. While the laptop has ed25519 and ecdsa private/public keys in

Re: [PLUG] scp issue

On 02/24/2017 01:06 PM, Rich Shepard wrote: > On Fri, 24 Feb 2017, King Beowulf wrote: > >> 3. The public key in autheorized-keys (DESTINATION) does not match the >> PRIVATE KEY (SOURCE) > > Ed, > >I just found this to be the case and posted that in the updated message. > Since the private

Re: [PLUG] Remote host lost ssh key verification [UPDATED]

You have two choices here Rich: a) Yes it will wipe all existing entries from known_hosts file, but they will be all recreated when you login to those hosts again in the future. b) delete only the line in known_hosts file corresponding to the host you have difficulties to login to. When you do

Re: [PLUG] scp issue

On 02/24/2017 12:29 PM, Rich Shepard wrote: > On Fri, 24 Feb 2017, King Beowulf wrote: > > >To repeat, I do not remotely login via ssh with a username and password, I > use the passphrase (which is not the same as a password since it contains > multiple words and punctuation.) > > Rich 1.

Re: [PLUG] Remote host lost ssh key verification [UPDATED]

On 02/24/2017 01:15 PM, Rich Shepard wrote: > On Fri, 24 Feb 2017, Rich Shepard wrote: > >> That's the problem: there's no public key for this laptop in >> ~/.ssh/authorized keys! > >And, there's no public key for this laptop in the desktop's > ~/.ssh/known_hosts. > Just delete

Re: [PLUG] scp issue

On Fri, 24 Feb 2017, King Beowulf wrote: > (remember: the default Slackware install of sshd does not use keys at all. > You login via normal username/password. See explanation on the other list > thread.) Having setup ssh/sshd on Slackware in 2003, and having it work with this laptop up

Re: [PLUG] scp issue

King Beowulf wrote: > On 02/24/2017 10:50 AM, Rich Shepard wrote: >> On Fri, 24 Feb 2017, Rich Shepard wrote: >> >>> debug1: Connecting to salmo [192.168.55.1] port <>. >>> debug1: Connection established. >> The two hosts can communicate. >> >>> debug1: key_load_public: No such file or

Re: [PLUG] Remote host lost ssh key verification [UPDATED]

On Fri, 24 Feb 2017, King Beowulf wrote: > for ssh or scp (cp over ssh), you only need one pub key for the > connection to work. NOT the ones in /etc/ssh. One of the ones in ~/.ssh Ed, Here's what I've done; there's still something left for me to do. On laptop: 1) ssh-keygen (using

Re: [PLUG] boot filled

Hi Denis, Need to run to remove unused old versions of kernels and other packages? Run: sudo apt autoremove --purge That should fix that for you automagically. If you want to prevent the problem happening in the future without remembering the command, you can configure it by following this

Re: [PLUG] Remote host lost ssh key verification [UPDATED]

I apologize for contributing to further confusion. I have not realized that you had two different email threads with different subjects going on the same topic. I should have staid out of it with so many messages in flight. Maybe, it would help to re-read the man page for ssh and make some notes

Re: [PLUG] Remote host lost ssh key verification [UPDATED]

On 02/24/2017 06:41 PM, Erik Lane wrote: snip- >> >> > Is there any reason why the public and private keys need to be different on > the different computers? (Purely out of curiosity about the technical > implementation.) It seems like you could create them on one computer and > copy paste

Re: [PLUG] Remote host lost ssh key verification [UPDATED]

On Fri, 24 Feb 2017, Tom wrote: > a) Yes it will wipe all existing entries from known_hosts file, but > they will be all recreated when you login to those hosts again in the > future. Tom, I thought this is the case when I moved the public key files to authorized_keys and found instant

[PLUG] Looking for Recruiter Recommendations

I am trying to find work in Portland from out of town. I have some friends in town, but no-one that has gotten their jobs through an agency or recruiter. Can anyone recommend anyone that they have worked with as being reasonably decent? Thanks, Purcell p.s. Yes I am doing the standard searching

Re: [PLUG] Looking for Recruiter Recommendations

Write it all, please. I am curious On 24 Feb 2017 15:46, "Chuck Hast" wrote: > Ha! I lost my job back at the end of Sept. I have been doing all of the > usual > stuff too. No joy! I think that most of them want entry level people and > when > they see my resume they know that

Re: [PLUG] Looking for Recruiter Recommendations

I have been looking for some headhunter or agency that specializes in field service work, but so far no real luck. Most of them shotgun you with a lot of useless stuff like killing bugs and rodents... (under field service) On Fri, Feb 24, 2017 at 3:38 PM, chris (fool) mccraw

Re: [PLUG] Remote host lost ssh key verification

On 02/24/2017 12:06 PM, Rich Shepard wrote: > On Fri, 24 Feb 2017, King Beowulf wrote: > >> In that case, the only entries that you care about are in "known_hosts" >> unless sshd is stopped. As root: >> /etc/rc.d/rc.sshd restart > > Ed, > >Did this. > >> $ ssh susan@glaurung > >It

Re: [PLUG] scp issue

On Fri, 24 Feb 2017, King Beowulf wrote: > (remember: the default Slackware install of sshd does not use keys at all. > You login via normal username/password. See explanation on the other list > thread.) From the desktop's sshd_config: # Authentication: #StrictModes yes RSAAuthentication

Re: [PLUG] scp issue

> On Fri, 24 Feb 2017, Rich Shepard wrote: > >> debug1: Connecting to salmo [192.168.55.1] port <>. >> debug1: Connection established. > >The two hosts can communicate. > >> debug1: key_load_public: No such file or directory >> debug1: identity file /home/rshepard/.ssh/id_rsa type -1 >>

Re: [PLUG] scp issue

On Fri, 24 Feb 2017, King Beowulf wrote: > 3. The public key in autheorized-keys (DESTINATION) does not match the > PRIVATE KEY (SOURCE) Ed, I just found this to be the case and posted that in the updated message. Since the private and public keys on each host are in /etc/ssh/ I need to

Re: [PLUG] scp issue

On Fri, 24 Feb 2017, a...@clueserver.org wrote: > What are the permissions on your local .ssh directory and files? 700 Rich ___ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug

Re: [PLUG] Remote host lost ssh key verification [RESOLVED]

On Fri, 24 Feb 2017, Rich Shepard wrote: > Now I'm confused about what should be in each host's > ~/.ssh/authorized_keys and ~/.ssh/known_hosts. > Do the id_ed25519.pub files from one host belong in the authorized_keys > files on other hosts? Yes, they do. I suspect that known_hosts is

Re: [PLUG] Remote host lost ssh key verification [UPDATED]

On 02/24/2017 02:16 PM, Rich Shepard wrote: > On Fri, 24 Feb 2017, King Beowulf wrote: > >> for ssh or scp (cp over ssh), you only need one pub key for the >> connection to work. NOT the ones in /etc/ssh. One of the ones in ~/.ssh > > Ed, > >Here's what I've done; there's still something

Re: [PLUG] Looking for Recruiter Recommendations

I've had stellar success as a job hunter with Edgelink : http://www.edgelink.com. They are more about "let us figure out what you're good at and filter jobs for you" than "throw you at everything available and see what sticks". They'll interview you before suggesting anything. They found me two

Re: [PLUG] Looking for Recruiter Recommendations

Ha! I lost my job back at the end of Sept. I have been doing all of the usual stuff too. No joy! I think that most of them want entry level people and when they see my resume they know that I will probably not stay around long be cause they are not paying enough, so they do not even worry, or I