WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: piCore-12.0beta1  (Read 1449 times)

Offline mortegai

  • Newbie
  • *
  • Posts: 8
Re: piCore-12.0beta1
« Reply #30 on: October 06, 2020, 02:18:08 PM »
Hi Juanito
Another way to test if group  sshd  exists.

Change this:
Code: [Select]
        busybox groups sshd >/dev/null 2>&1
        [ $? -ne 0 ] && busybox addgroup -g 33 sshd

To this:
Code: [Select]
        touch /tmp/groups
        chown tc:sshd /tmp/groups >/dev/null 2>&1
        [ $? -ne 0 ] && busybox addgroup -g 33 sshd

Or just change to
Code: [Select]
        grep -q sshd /etc/group
        [ $? -ne 0 ] && busybox addgroup -g 33 sshd


Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 8241
Re: piCore-12.0beta1
« Reply #31 on: October 06, 2020, 05:25:39 PM »
Hi mortegai
If you are going to do that, search for an exact match:
Code: [Select]
grep -q '^sshd:' /etc/group

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 12514
Re: piCore-12.0beta1
« Reply #32 on: October 07, 2020, 01:34:20 AM »
But now, if the sshd user does not exist (initial/pristine situation) occurs error:
Privilege separation user sshd not exist
and sshd does not run.

sshd ran on startup for me in testing using the modified openssh init.d script, but I presume now that was influenced by the backup.

I don't know of a reason why an additional user named sshd would be necessary for sshd to work on piCore - things work on Core/CorePure64 without it.

I will have access to a screen in a couple of days time to be able to troubleshoot.
« Last Edit: October 07, 2020, 02:02:34 AM by Juanito »

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 8241
Re: piCore-12.0beta1
« Reply #33 on: October 07, 2020, 06:55:03 AM »
Hi Juanito
Seems this already came up in piCore-12.0alpha1:
http://forum.tinycorelinux.net/index.php/topic,24196.msg153179.html#msg153179

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 636
Re: piCore-12.0beta1
« Reply #34 on: October 07, 2020, 01:38:30 PM »
If you could interpret anything he said.....  lol.

groups sshd was a carry over from piCore 11   (and possibly 10)   Its just that Juanito and I were trying to commonize configs between x86_64 and piCore.  We started with busybox, which is why "groups" got dropped and highlighted this issue.

We just have to figure out right solution.....without doing a big re-invention.

Offline Paul_123

  • Administrator
  • Hero Member
  • *****
  • Posts: 636
Re: piCore-12.0beta1
« Reply #35 on: October 10, 2020, 08:53:47 AM »
Openssh issue caused from confusion from x86_64, and different folks building things.

I've updated armv6/7 and aarch64 to openssh8.4p1 and commonized the privilege separation configuration with x86_64, which uses the user "nobody" as the non-privileged user.  nobody is supplied as a standard user in the piCore image, so no need to check anything anymore.

Online polikuo

  • Sr. Member
  • ****
  • Posts: 426
Re: piCore-12.0beta1
« Reply #36 on: October 12, 2020, 10:51:54 PM »
I'd like to remind all users here to fix, recreate and backup the file.
/usr/local/etc/ssh/sshd_config

The new openssh extension is recompiled with a different libexecdir.

At line 108, 109 we have
Quote
# override default of no subsystems
Subsystem       sftp    /usr/local/libexec/sftp-server
Replace that with the new route
Quote
Subsystem       sftp    /usr/local/lib/openssh/sftp-server

That should fix any quirky ftp functions / behaviors.

Online polikuo

  • Sr. Member
  • ****
  • Posts: 426
Re: piCore-12.0beta1
« Reply #37 on: October 15, 2020, 11:55:07 PM »
Hi, a quick report.  :)

Please append gnutls.tcz to vte.tcz.dep (12.x/aarch64)

vte won't run without it.

Online Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 12514
Re: piCore-12.0beta1
« Reply #38 on: October 16, 2020, 12:19:21 AM »
vte* deps adjusted - thanks for reporting this.