Re: [PLUG] Enabling bi-directional ssh

On Sun, Nov 06, 2016 at 02:48:22PM -0800, Rich Shepard wrote: > debug1: Authentications that can continue: publickey > debug1: Next authentication method: publickey > debug1: Trying private key: /home/rshepard/.ssh/id_dsa > debug2: we did not send a packet, disable method > debug1: No more

Re: [PLUG] Enabling bi-directional ssh

I'm glad that you resolved the /etc/ssh host key files. It is common to stop sshd, remove the files and start sshd again to generate new set of host files. It is normally done when you create a host from disk image either locally or in the cloud. Otherwise you would have multiple hosts with

[PLUG] Resolved: Audio stopped working on Movie Player on Ubuntu 14.04

On 11/03/2016 03:31 PM, Dick Steffens wrote: > I think it was the day before yesterday that playback of audio files > stopped working on Movie Player on my Ubuntu 14.04 machine. If I open a > file in Audacity I can still get the sound to play. If that file is a > stereo file, I can get it to play

Re: [PLUG] Permissions for an entire PARTITION

How about using a file system windows can't read? On Nov 7, 2016 4:23 AM, "Richard Owlett" wrote: > > My primary use case is a laptop: >1. purchased explicitly for use as a test bed. >2. whose HD has been erased multiple times in ONE day. >3. is isolated from

Re: [PLUG] Enabling bi-directional ssh

On Mon, 7 Nov 2016, Rich Shepard wrote: > Sure enough, that does make a difference. Still denied access to the > remote portable from the local desktop and will work on that. Almost there. On the portable/remote there are server ssh_host keys. I can now ssh from the desktop/local to the

Re: [PLUG] Enabling bi-directional ssh

On Mon, 7 Nov 2016, David wrote: > If you read the script that is referenced by "whowd", there is a test for > the host keys, and that creation is bypassed because the file exists. My > apologies for presuming that you would read it more carefully. David, I read it but missed seeing that. >

Re: [PLUG] Enabling bi-directional ssh

On 11/07/2016 11:53 AM, Rich Shepard wrote: > On Mon, 7 Nov 2016, David wrote: > >> I don't recall which OS, but this link has the two main streams: >> > > dafr, > >And everyone agrees that when sshd is started it should create the server

Re: [PLUG] Enabling bi-directional ssh

On 11/7/2016 11:53 AM, Rich Shepard wrote: > On Mon, 7 Nov 2016, David wrote: >> I don't recall which OS, but this link has the two main streams: >> > dafr, > > And everyone agrees that when sshd is started it should create the server >

Re: [PLUG] Enabling bi-directional ssh

On Mon, 7 Nov 2016, David wrote: > I don't recall which OS, but this link has the two main streams: > dafr, And everyone agrees that when sshd is started it should create the server host_keys. Here it ain't doin' that. Sigh. Thanks,

Re: [PLUG] Enabling bi-directional ssh

On Mon, 7 Nov 2016, Larry Brigman wrote: > Normally the sshd start up script generates the host keys. This should be > automatic for system installs. Larry, That's what I assumed, but not what I have here. Perhaps I need to re-install sshd. Will try that before asking for help on the

Re: [PLUG] Enabling bi-directional ssh

On Mon, 7 Nov 2016, Rich Shepard wrote: > Still looking ... As root, generated an ssh key and put the file(s) in /etc/ssh. Still cannot start sshd; it cannot find /etc/ssh/ssh_host_ed25519_key even though all 444 bytes are present. Time to post on linuxquestions.org. Rich

Re: [PLUG] Enabling bi-directional ssh

On 11/07/2016 11:25 AM, Rich Shepard wrote: > On Sun, 6 Nov 2016, Rich Shepard wrote: > >> On the server/workstation and a portable ~/.ssh has 700 perms while the >> authorized_keys, known_hosts, and *.pub key files in that directory have 644 >> perms; the others are 600. > >I've identified

Re: [PLUG] Enabling bi-directional ssh

Normally the sshd start up script generates the host keys. This should be automatic for system installs. On Nov 7, 2016 11:28 AM, "Rich Shepard" wrote: > On Sun, 6 Nov 2016, Rich Shepard wrote: > > > On the server/workstation and a portable ~/.ssh has 700 perms

Re: [PLUG] Enabling bi-directional ssh

On Sun, 6 Nov 2016, Rich Shepard wrote: > On the server/workstation and a portable ~/.ssh has 700 perms while the > authorized_keys, known_hosts, and *.pub key files in that directory have 644 > perms; the others are 600. I've identified the problem and am working on finding the solution.

Re: [PLUG] Specifying white space as delimiter for 'cut'

Hello there, > I tried using cut to list permissions and filenames from a directory >listing, example: > > ls -l | cut -d"\b" -f 1,9 > temp.txt > >but the delimiter is more than a single character. Using -d " " for >the delimiter does not work as there are more than a single space

Re: [PLUG] Specifying white space as delimiter for 'cut'

On Mon, 7 Nov 2016, Michael Rasmussen wrote: > cut can use other delimiters besides spaces. And can, helpful in this > case, choose arbitrary byte offsets: >michael@bivy /srv/photo/365_2012 % ls -l | head | cut -b1-10,53- > The man page for cut lists "-b, --bytes=LIST" as the first described

Re: [PLUG] Specifying white space as delimiter for 'cut'

On Mon, 7 Nov 2016, Larry Brigman wrote: > Looking at the info on cut, you cannot do it in a single command. You > would need to use sed. or tr with a pipe Thanks, Larry. I thought that cut needed a consistent delimiter but thought it might accommodate any whitespace defined by a single

Re: [PLUG] Specifying white space as delimiter for 'cut'

cut can use other delimiters besides spaces. And can, helpful in this case, choose arbitrary byte offsets: michael@bivy /srv/photo/365_2012 % ls -l | head total 706024 drwxrwxr-x 10 michael michael 36864 Feb 16 2015 2012 drwxrwxr-x 2 michael michael 12288 Jul 8 14:21

Re: [PLUG] Specifying white space as delimiter for 'cut'

Looking at the info on cut, you cannot do it in a single command. You would need to use sed. or tr with a pipe On Mon, Nov 7, 2016 at 8:01 AM, Larry Brigman wrote: > Woops extra $ in the script. > ls -l | awk '{print $1 $NF;}' > > > On Mon, Nov 7, 2016 at 8:00 AM,

Re: [PLUG] Specifying white space as delimiter for 'cut'

Woops extra $ in the script. ls -l | awk '{print $1 $NF;}' On Mon, Nov 7, 2016 at 8:00 AM, Larry Brigman wrote: > Try using awk > ls -l | awk '{print $1 $$NF;}' > > Note if the file timestamp (creation or modification) is over a year old > it changes and the output may

Re: [PLUG] Specifying white space as delimiter for 'cut'

Try this: ls -la | awk '{print $1, $9}' On Mon, 7 Nov 2016, Rich Shepard wrote: > I tried using cut to list permissions and filenames from a directory > listing, example: > > ls -l | cut -d"\b" -f 1,9 > temp.txt > > but the delimiter is more than a single character. Using -d " " for the >

Re: [PLUG] Specifying white space as delimiter for 'cut'

Try using awk ls -l | awk '{print $1 $$NF;}' Note if the file timestamp (creation or modification) is over a year old it changes and the output may not have 9 columns then. On Mon, Nov 7, 2016 at 7:47 AM, Rich Shepard wrote: >I tried using cut to list permissions

Re: [PLUG] Specifying white space as delimiter for 'cut'

On Mon, 7 Nov 2016, bro...@netgate.net wrote: > Try this: > ls -la | awk '{print $1, $9}' Brooks, Yes, awk will do the job. I wanted to learn if cut could also be used with a variable delimiter. Thanks, Rich ___ PLUG mailing list

[PLUG] Specifying white space as delimiter for 'cut'

I tried using cut to list permissions and filenames from a directory listing, example: ls -l | cut -d"\b" -f 1,9 > temp.txt but the delimiter is more than a single character. Using -d " " for the delimiter does not work as there are more than a single space separating fields, and the

Re: [PLUG] Enabling bi-directional ssh

On Sun, 6 Nov 2016, Tom wrote: > I struggle to understand what is local and what is remote and what files > you have where. So here is the minimum what you need to do/audit: > > Local machine .ssh/: > id_ed25519 - r/w by user only (600) > id_ed25519.pub - r/w by user + r by group and others (644)

[PLUG] Permissions for an entire PARTITION

My primary use case is a laptop: 1. purchased explicitly for use as a test bed. 2. whose HD has been erased multiple times in ONE day. 3. is isolated from ANY network. 4. has multiple installs of Debian, primarily classed as: a. a full GUI install - what one would get choosing