| chomwitt | after a lengthy discussion in oftc #lxqt i decided to create an issue https://github.com/lxqt/lxqt-config/issues/767 | 00:13 |
|---|---|---|
| chomwitt | a lxqt developer suggested that devuan should move to lxqt 0.17 | 00:14 |
| golinux | We move to whatever version Debian offers | 00:15 |
| chomwitt | a related debian (so maybe devuan) related filelight issue https://github.com/lxqt/lxqt-panel/issues/1661 | 00:16 |
| chomwitt | golinux, ok , i just say what they said to me | 00:17 |
| golinux | Thanks for letting us know | 00:19 |
| chomwitt | np | 00:19 |
| ham5urg_ | Is fwupd a good or bad thing? | 00:55 |
| ham5urg_ | How does "root 2653 1 0 00:42 ? 00:00:01 /usr/libexec/fwupd/fwupd" got loaded? I can't find it in /etc/init.d/ | 01:03 |
| ham5urg_ | I guess it is autoload when fwupdmgr is invoked and not been shutdown afterwards. | 01:08 |
| ham5urg_ | Unclean in my eyes. | 01:08 |
| ham5urg_ | If so | 01:08 |
| Hydragyrum | any reasonably easy way to check which files in /etc differ from the defaults shipped with packages? | 02:33 |
| gnarface | Hydragyrum: check for copies with an additional extension like .dpkg-new .dpkg-old or .dpkg-dist, stuff like that | 03:04 |
| gnarface | if there's a collision during an upgrade with a file a user changed, there's usually a backup of some sort | 03:04 |
| gnarface | off the top of my head i can't think of a simple command to actually compare them all recursively without writing scripts to automate looping through the process of re-downloading the stock package from the repo | 03:05 |
| gnarface | the best practice of course is to have already made a backup of /etc | 03:06 |
| gnarface | i realize that might not help much at this point though | 03:06 |
| onefang | Or use etckeeper. | 03:06 |
| Hydragyrum | yeah, I forgot to set up etckeeper on this install | 03:06 |
| Hydragyrum | I usually do use it | 03:06 |
| fsmithred | debsums -ca | 03:31 |
| fsmithred | Hydragyrum, gnarface ^^^ | 03:31 |
| Hydragyrum | where does that come from? apt-file doesn't find me a package containing anything called debsums | 03:32 |
| Hydragyrum | nvm my apt-file seems to be acting up | 03:33 |
| fsmithred | Package: debsums | 04:22 |
| fsmithred | Version: 2.2.3 | 04:22 |
| fsmithred | Priority: optional | 04:22 |
| Hydragyrum | yeah that worked really well, ty | 04:31 |
| chomwitt | Trying to install an epson inkjet driver,but as dpkg --info shows and as dpkg -i complains it has a dependency on 'lsb' a package non existant | 09:58 |
| rrq | the lsb package doesn't seem to provide anything other than a coupld of branding files and some subsystem dependencies, esp "cups"... an equivs package would probably wotk for you... | 10:16 |
| rrq | see https://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=lsb&x=submit | 10:16 |
| chomwitt | i'll try $ sudo apt-get install printer-driver-escpr | 10:18 |
| chomwitt | must be the driver i need | 10:18 |
| chomwitt | cool ,, its done, with cups installed i can print to a wifi printer while i am connected wired in the same access point | 10:48 |
| nckx | Does Devuan rely on eudev by default, and if is there a plan regarding its deprecation? <https://wiki.linuxfromscratch.org/lfs/ticket/4914> | 11:40 |
| nckx | *if so | 11:40 |
| fsmithred | nckx, yes and yes. #devuan-eudev | 11:53 |
| nckx | Thanks! | 11:56 |
| nckx | I wasn't aware of that channel. | 11:57 |
| fsmithred | it's only existed for a day or two | 11:57 |
| * chomwitt finds debtree diagrams on pkginfo.devuan.org cool! | 14:19 | |
| * chomwitt finds clickable debtree diagrams cooler ... | 14:21 | |
| jason1234 | LFS guys... https://gitlab.com/openbsd98324/openbrt unpack the rootfs.tar.gz and boot out of grub. you will get the smallest linux ever, without any base at all ... you can use it on top to make your own distribution of linux. Only the -static is needed to run command.s it allows to deploy devuan out of it, using tar and dpkg -x | 15:34 |
| blockhead | gotta love those git hub sites that don't even say what the project is or does *golf clap*. Nothing to do with real Linux From Scratch, it turns out. Oh, and oh dear, that's off topic, isn't it? | 15:42 |
| fsmithred | in beowulf and ascii, I could resize a qemu window by grabbing the corner with the mouse and moving it. In chimaera, this does not work. Any ideas on how to fix it? | 17:09 |
| fsmithred | grep -v no longer works? wtf? | 17:30 |
| fsmithred | how do I search inside every file on my computer to find the string 'lightdm-xsession' and only return lines that have that string? | 17:31 |
| fsmithred | or more to the point, how do I get xfce or whatever is sending me the error to stop trying to load a lightdm-xsession after lightdm has been purged and replaced with lxdm? | 17:31 |
| fsmithred | Xsession: unable to launch "lightdm-xsession" --- lightdm-xsession not found; falling b | 17:33 |
| ksx4system | fsmithred, only thing that comes to my mind would be writing a script executing cat and then grep on every file you'd like to "scan" | 17:54 |
| ksx4system | but there's probably better solution | 17:54 |
| fsmithred | I'm grepping one dir at a time to skip /proc | 17:54 |
| fsmithred | which was spamming the console | 17:54 |
| Xenguy | fsmithred, grep -rv foo * | 18:20 |
| Xenguy | should work, no? | 18:20 |
| fsmithred | Xenguy, not today | 18:20 |
| Xenguy | Otherwise, not sure how efficient it is, but could a combination of find and grep e.g. | 18:20 |
| fsmithred | I'm past that, anyway. Looking at $DESKTOP_SESSION now | 18:21 |
| fsmithred | yeah, I already used find with -exec to delete every file on the hard drive with lightdm in its name | 18:21 |
| Xenguy | find . -type f -exec grep -i foo {} \; | 18:21 |
| fsmithred | no shit. I am pissed off about this. | 18:21 |
| Xenguy | Weird | 18:21 |
| fsmithred | something is telling Xsession to use lightdm-session | 18:22 |
| fsmithred | I suspect it may be startxfce4, but if so, it's new in chimaera | 18:22 |
| fsmithred | I've used lxdm with xfce in beowulf and ascii, and it worked fine. | 18:22 |
| fsmithred | just had to set the session=/usr/bin/startxfce4 in lxdm.conf | 18:23 |
| fsmithred | and this isn't even the real issue. I just wanted to try lxdm to see if it made a difference. | 18:25 |
| fsmithred | how to get xfce to respect the language/locale that is selected at boot in a live iso? | 18:25 |
| fsmithred | in desktop-live isos and refracta-runit isos it works. In new refracta-xfce isos it does not work. I only get the keyboard on the desktop. | 18:26 |
| fsmithred | found it! in ~/.dmrc: session=lightdm-xsession (I changed it to default and set startxfce4 in lxdm.conf | 18:32 |
| fsmithred | Cestino! | 18:57 |
| fsmithred | I think that's where lightdm is going in Refracta | 18:58 |
| systemdlete | I am trying to set up a ssh and scp connection to a machine running dropbear (not openssh, etc). I can successfully scp a file to the remote (dropbear server), but ssh does not work. I'm using a ec22519 key pair. on the local system, I am using openssh-client on beowulf. Could there be a compatibility problem with this combination? | 21:03 |
| systemdlete | user and root logins to the remote are disabled. | 21:04 |
| systemdlete | (the public key file was transferred to the dropbear server side; scp works.) | 21:05 |
| systemdlete | thank you | 21:06 |
| rwp | systemdlete, Was it that logins were disabled? Was that the end result of the debug? | 21:30 |
| systemdlete | rwp: Never mind. I think I have this fire under control... ALMOST. | 21:30 |
| rwp | Most often on the client side I use 1 or 3 -v on the ssh to see what it says. | 21:31 |
| rwp | ssh -v remotehost.example.com, Hmm... ssh -vvv remotehost.example.com, and hopefully find a clue in there. | 21:31 |
| rwp | Multiple -v's increase verbosity. | 21:31 |
| systemdlete | I think the problem is that I am specifying the wrong user. But now it seems to be working, even though the pub file spec on the remote belongs to a regular user. | 21:31 |
| systemdlete | (yes, I did a trace.) | 21:31 |
| systemdlete | but root login is disabled. | 21:32 |
| systemdlete | on the remote I mean | 21:32 |
| rwp | If scp works then almost by definition ssh should work since scp *is* ssh and is using ssh. But your interactive login comment could be it. | 21:32 |
| systemdlete | "interactive login comment?" | 21:32 |
| rwp | Everyone disables root by default these days. Which is a pity. | 21:32 |
| rwp | You had said, ":04 <systemdlete> user and root logins to the remote are disabled." | 21:32 |
| systemdlete | Oh | 21:32 |
| systemdlete | I did that | 21:33 |
| systemdlete | I want all ssh and scp traffic to use secure connections. | 21:33 |
| systemdlete | besides, it avoids having to enter a password all the time | 21:33 |
| rwp | The OpenSSH default these days is "PermitRootLogin prohibit-password". | 21:34 |
| rwp | Which allows the use of keys, but not passwords. | 21:34 |
| systemdlete | right. | 21:34 |
| rwp | But many distros set that to an actual "PermitRootLogin no". Which just blocks it entirely. | 21:34 |
| systemdlete | well, I have disabled root login with password on the remote. | 21:35 |
| systemdlete | here's what is puzzling me. the key pair I am using was generated by an admin user not root on the local host. | 21:35 |
| systemdlete | I copied the pub file to the remote. | 21:36 |
| rwp | How did you disable root login with password? | 21:36 |
| rwp | Disabled it in /etc/shadow? Or used passwd -l or whatever? | 21:36 |
| systemdlete | but it allows root to connect without password, which I don't expect. The pub file has the username and hostname of the local, not root for the local | 21:36 |
| systemdlete | first off, the remote is running dropbear, not openssh. | 21:37 |
| systemdlete | second, there's a UI for all of this for the remote (it's a router) | 21:37 |
| systemdlete | (openwrt router) | 21:37 |
| systemdlete | hopefully that explains things more clearly. | 21:38 |
| rwp | Oh it's OpenWRT. Gotcha. | 21:38 |
| systemdlete | sorry. should have pointed that out more and earlier | 21:38 |
| rwp | Yes. I can *almost* but not quite know what is going on with OpenWRT. | 21:38 |
| systemdlete | yes. | 21:38 |
| systemdlete | I am also soliciting help in their channel with this. | 21:38 |
| rwp | The problem being that I (we?) don't actually know what the web UI is doing behind the scenes internally on the box. | 21:39 |
| systemdlete | I am no expert on cryptography or ssh. | 21:39 |
| systemdlete | right. | 21:39 |
| systemdlete | and it is a brand new release that has had some bugs so far | 21:39 |
| systemdlete | ergo, y'know | 21:39 |
| rwp | Fortunately we can mostly ignore the cryptography and just assume that part works like any other connection. | 21:39 |
| systemdlete | oh, I meant the keys and the manner in which ssh works in general, as opposed to specific tools and implementations | 21:40 |
| rwp | And since scp is working then we know that the crypto is working between the boxes. So no concerns about incompatibility between the ciphers or anything. | 21:40 |
| systemdlete | like in this instance, the way the protocol is supposed to do matching of identities etc | 21:40 |
| systemdlete | right. and ssh is working also. but it is working for root, not just my regular user | 21:41 |
| rs | systemdlete: Are you specifying root while attempting to ssh to openwrt? Doesn't ssh need a user regardless? | 21:41 |
| systemdlete | yes | 21:41 |
| systemdlete | well | 21:41 |
| systemdlete | yes and yes | 21:41 |
| rs | Or connect with "user"@host? | 21:41 |
| systemdlete | yep | 21:41 |
| systemdlete | erase! erase! erase! | 21:42 |
| systemdlete | doh | 21:42 |
| systemdlete | I got my windows mixed up | 21:42 |
| systemdlete | no, it really is the regular user that is successful with both ssh and scp | 21:42 |
| rs | why would you not want to login as root on openwrt? with a key and no http, or http'd disabled unless needed, im not sure the need to block ssh to root@host. | 21:43 |
| systemdlete | it isn't. | 21:44 |
| rs | it? | 21:45 |
| systemdlete | the router blocks users including root from entering a password | 21:45 |
| rwp | Right. I always unblock root entirely because I use long random generated passwords but with a key only is very safe. | 21:45 |
| rs | rwp: exactly. i also disable http entirely and use ssh to enable when necessary | 21:45 |
| systemdlete | is there a problem with things this way? | 21:46 |
| rwp | I also say no http/https on the WAN side but only allowed on the LAN side. | 21:46 |
| systemdlete | It is more convenient not to have to enter a password for one thing. | 21:46 |
| systemdlete | rwp: currently the router only allows connections from the lan side. | 21:46 |
| rwp | There is convenience. And then there is the initial setup debug time when things are not working. | 21:46 |
| rwp | But yes ssh keys are convenient and more secure. So that is what I use 99.44% of the time. | 21:47 |
| rs | systemdlete: Well, you shouldn't need a password for anything -- assuming you command line everything via ssh. | 21:47 |
| systemdlete | moreover, these will be "canned" instructions -- specific scripts, not ad hoc instructions | 21:47 |
| systemdlete | (actually, really only one script. so far anyway) | 21:48 |
| systemdlete | thanks to you both btw | 21:48 |
| rwp | If it wasn't OpenWRT but a standard system I would suggest looking in /var/log/auth.log for the server side of the debug trail. | 21:50 |
| rwp | Does the OpenWRT have any log files available for that side of the debug trail? | 21:50 |
| systemdlete | eh, not so much no | 21:50 |
| systemdlete | I think there are ways to increase the verbosity and so on, but I have not done that really | 21:51 |
| systemdlete | in fact, I have actually redirected logging to a local system where it is easier to do hunting | 21:51 |
| systemdlete | Also uses less space on the router | 21:51 |
| systemdlete | but I am not having any problems now, thanks to you guys | 21:52 |
| rwp | This is why my house router and WiFi Access Point is an actual small system running Beowulf. Have a full software stack there. Everything is just Devuan and normal. | 21:52 |
| rwp | You have things working and happy now? | 21:52 |
| systemdlete | yes | 21:52 |
| systemdlete | happy | 21:52 |
| rwp | \o/ | 21:52 |
| systemdlete | very happy | 21:53 |
| rwp | What was the secret that made everything work? | 21:53 |
| systemdlete | the secret? Well, to start with, specifying the correct user on the command line to ssh :D | 21:54 |
| rwp | That would do it! :-) | 21:54 |
| systemdlete | and then later, when I thought i was getting local root to execute ssh on the router, suddenly realizing the local shell was logged in as the local admin (regular) user, not local root! | 21:55 |
| systemdlete | I confused myself with that. | 21:55 |
| rwp | It can be easy to get tripped up that way. I most often do it when I am comparing three different remote system things and confuse myself on which terminal is which. | 21:56 |
| systemdlete | Yeah, I am using several command windows also. Some window managers don't keep up well with re-titling windows as I log in to remote systems, change users, etc | 21:57 |
| systemdlete | but on this desktop, which is lxde, it actually does a pretty good job of updating the window titles. I am even wearing my computer eyeglasses. So there is no excuse. | 21:59 |
| systemdlete | When they were giving out brains, I thought they said trains... | 21:59 |
| rwp | I use the normal PS1 which puts the user and hostname in the prompt. That helps. | 22:00 |
| rwp | But for OpenWRT I don't know what they have set up there. | 22:01 |
| systemdlete | agreed | 22:01 |
| systemdlete | pretty much that | 22:01 |
| systemdlete | it is 'root@routername# ' | 22:02 |
| systemdlete | and that shows up the same in ssh session, so that is fine. | 22:02 |
| systemdlete | the bigger problem is the window titles because I usually leave a lot of windows open all the time. | 22:03 |
| systemdlete | heck, I even label my desktop to reflect which host I'm on -- no kidding. | 22:03 |
| systemdlete | What I do is I change the comment field for the login user (not root) to say something like "welcome to beowulf" or whatever. | 22:04 |
| systemdlete | And that shows up in either the action widget or some other control on the panel for that desktop. | 22:04 |
| systemdlete | It helps a lot when I have to update/upgrade my VMs | 22:05 |
| rwp | I (ab)use the /etc/debian_chroot file for that all of the time on systems that don't otherwise have a reasonable name. | 22:05 |
| rwp | The default .bashrc file has PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ ' which puts the contents of that file in the prompt. | 22:06 |
| rwp | Personally I don't use the window titles very much. But it's a work flow ergo thing as everyone has different ways of doing things. | 22:06 |
| systemdlete | linux/unix are certainly flexible and adaptable | 22:12 |
| rwp | "UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity." --Dennis Ritchie | 22:12 |
| systemdlete | yeah, what you said | 22:13 |
| rwp | dmr said it not me! I just quoted him. | 22:13 |
| systemdlete | sorry... | 22:13 |
| rwp | And he should know. One of the two main original authors of the Unix system! | 22:13 |
| systemdlete | and one of two creators of C | 22:14 |
| joerg | . | 22:51 |
| joerg | . | 23:43 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!