[04:22] so what do I do to resolve these - https://apaste.info/AXxB [04:24] donofrio: ask VMWare? [04:24] donofrio: i assume you are using something from VMWare on Bionic? [04:24] this is on my home 18.04 install.... [04:24] heck yah [04:25] donofrio: afaict, not an ubuntu thing? [04:26] inxi @ https://apaste.info/Ab1S [04:26] donofrio: those have all probably changed version in Bionic, e.g., libpng16 is what's there [04:26] donofrio: it's not up to ubuntu to make sure some 3rd prty, non-ubuntu software works [04:26] donofrio: that's up to vmware [04:26] donofrio: so again, you're probably doing something not supported by vmware [04:26] yah libpng16 is installed [04:27] donofrio: right, but the program/tool you are using is looking for libpng12 [04:27] so do I need a symlink? [04:27] so it needs to be rebuilt. [04:27] no [04:27] that would be the absolute wrong thing to do, since there is an ABI change [04:27] donofrio: you should talk to who makes the software to update it for bioni [04:27] *bionic [04:27] so bugtrac this I should? [04:27] and it's not ontopic for ubuntu+1 [04:27] donofrio: like i said, presumably you should be talking to vmware [04:28] k tnx [04:28] "had to ask" === chu is now known as yuken === yuken is now known as Guest72076 === Guest72076 is now known as chu [15:07] what is the ownership for /root/.ssh supposed to be. Openssh server keeps complaining about ownership. I tried `chmod 000 -R /root/.ssh` I tried `chown sshd -R /root/.ssh; chmod 500 /root/.ssh; chmod 400 /root/.ssh/authorized_keys` [15:07] ownership and permissions [15:11] Lope: 700 the dir, 600 the files [15:11] very similar to what I did [15:11] and who must own it? [15:11] root [15:12] Although in general logging in as root with ssh isn't enabled [15:12] Maybe only with keys, not with passwd, I don't remember the exact setup [15:12] well I've got PermitRootLogin I tried without-password [15:12] and also tried prohibit-password [15:13] Start with setting up the correct permissions/owner [15:13] Ah it worked! [15:14] seems the permissions were wrong. 700 dir and 600 files works. [15:14] strange that 500 dir and 400 files didn't work. [15:14] or even 000 everything. [15:15] I suppose it's just checking for specific permissions and that's all it cares about. [15:17] Lope: 400 means no write access [15:17] 000 means no access [15:17] of course they wouldn't work [15:18] I believe ssh checks for a specific mode, not for "anything less or equal to..." [15:18] Now I can connect and get a shell, but I connect int he same way with sshfs and it says connection reset by peer? [15:18] Can you connect with sshfs as a normal user, not root? [15:18] alkisg: must be a specific mode. [15:19] alkisg: root doesn't get checked for permissions. [15:19] try being root and writing to a read only file etc, you can do anything. [15:19] You mean at the file system access level; ssh probably uses stat. [15:20] okay, so you mean root can be denied access in some ways if root doesn't have permission? [15:20] Of course [15:20] "if your ssh dir is not 700, I won't give you access" [15:20] Hmm, i suppose that could be how encfs works. [15:20] A one-line if in the code [15:20] I can't imagine why ssh would special-case root. It would do the same checks without caring about the uid. [15:21] sshfs root@foo:/ /mnt/bar -C -o allow_root,IdentityFile=/baz [15:22] I get connection reset by peer [15:22] Try as another user... [15:23] Non root. To bisect where the error is. [15:23] bit of a hassle :p [15:23] OK, try random stuff then, it might be quicker. :) [15:24] I'm guessing it might be some new SSH setting that prevents sshfs [15:24] sshfs works fine here in 18.04 [15:28] Weird. it worked when I ran it as root === ubott2 is now known as ubottu === siel_ is now known as siel === tfgbd is now known as tfgbd_ === tfgbd is now known as tfgbd__