| Xenguy | SSH question: Would you say it is best practice to generate SSH keys for each PC, or do people commonly just use a single pair of keys for all their personal PC's? | 00:29 |
|---|---|---|
| yeti | I'm using one identity per user@system and that already makes a lot of identities. I'd prefer to even use one keyset for each "connection" (user1@source-->user2@target) but I'm not there yet. maybe it's alredy too much what I already have here... | 00:35 |
| rwp | I use one identity for my desktop and one more identity for multiple mobile laptops. The laptops conceptually are all the same. If one were lost or stolen I would invalidate the key using the desktop key and create a new key for the mobile devices. | 01:46 |
| rwp | Note that if you have more than six identities then one runs up again sshd MaxAuthTries. | 01:51 |
| Xenguy | Thanks yeti , rwp | 01:57 |
| Xenguy | I also noticed some docs recommend, e.g. ssh-keygen -t ed25519 -C "email@address.net" | 02:00 |
| Xenguy | But it seems to me I've always used something more along the lines of '-C "username@host" | 02:00 |
| yeti | you can call it "the weekend key" if you want. | 02:02 |
| Xenguy | Sure, but usually there are so-called best practices associated with these operations, and that's usually what I'm looking to discern. | 02:02 |
| rrq | maybe, if you think of the public "key" as a lock that is unlocked by the private key (as a key) then maybe it makes snese to label the lock by the key holder rather than by what it unlocks. | 02:43 |
| Xenguy | Do all Swedes think like this? | 02:50 |
| Xenguy | Is this why the Norse have a love/hate relationship with them? | 02:52 |
| Xenguy | Thank you also, it certainly qualifies as a 'hot take', as they say nowadays | 02:54 |
| plasma41 | rwp: You might be interested ^the diagram I shared earlier today as I cited you in the source | 04:10 |
| rwp | Xenguy, I label my keys by editing the .pub file and editing the comment there. It's only a comment. In my I say "desktop" and "laptop". It's just a comment tag and can be anything that makes sense to you to identify the key. Since otherwise the key itself is not immediately intelligible to humans looking at it. | 06:53 |
| rwp | On our shared hosts where we use keys to access multiple people on those hosts we use the email address in the comment field. | 06:53 |
| D-HUND | plasma41: thank you! . o O ( dang, totally forgot about ~/.Xresources ) | 07:57 |
| Afdal | Anyone use timidity? | 11:20 |
| Afdal | I'm trying to add timidity to my sysvinit services so MIDI will get directed to timidity instead of a non-existent sound card | 11:21 |
| Afdal | but I don't see a timidity service available in my services list? | 11:21 |
| Afdal | even though I've got it installed and otherwise setup? | 11:21 |
| Afdal | do I need to manually build a timidity.service file >:/ | 11:26 |
| Afdal | rofl okay, there's a timidity-daemon package I didn't have | 11:32 |
| Afdal | :D | 11:32 |
| Afdal | only now there's another problem >:( | 11:32 |
| Afdal | Starting TiMidity++ ALSA midi emulation: timidity failed! | 11:32 |
| Afdal | Can I get sysvinit to spit out something more verbose here :/ | 11:38 |
| Afdal | this isn't a very helpful error -.- | 11:38 |
| Afdal | uh wait, service timidity status says the service is running | 11:39 |
| Afdal | even though it says it failed... | 11:39 |
| Afdal | okay, indeed it is running :) | 11:40 |
| Afdal | why does sysvinit spit out this confusing error | 11:40 |
| Afdal | Well I guess I managed to solve my own problem >_> | 11:41 |
| amarsh04 | Afdal, I've had problems with timidity also. My other pc still has old PCI slots and a SoundBlaster Audigy 2ZS with wavetable synth | 11:54 |
| amarsh04 | brb | 11:54 |
| Afdal | Apparently running timidity as a service is uh | 12:20 |
| Afdal | interfering with all other pulseaudio sound | 12:20 |
| Afdal | it kills my audio for all other programs that aren't running MIDI | 12:21 |
| Afdal | hmm, am I not allowed to let sysvinit handle this... or it ends up competing with pulseaudio? | 12:22 |
| Afdal | if I run timidity as a daemon manually with timidity -iA it doesn't do this :/ | 12:23 |
| Afdal | I suppose I can just run timidity as a daemon through xfce4-session | 12:37 |
| Afdal | and that gets it to load properly after pulseaudio | 12:37 |
| Afdal | instead of taking over completely | 12:38 |
| Afdal | but I'd rather avoid that kind of hack -_- | 12:38 |
| rwp | I would tell plasma41 if they were here that I appreciate the citation but the authoritative answer is in the source. (Like Obiwon says, "Use the source Luke.") | 15:27 |
| djph | heh | 18:46 |
| gnarface | Afdal: attempting to use timidity with dosbox i discovered similar issues and could only solve them by launching timidity as the same user that's running dosbox. i'm not sure what the point of the daemon mode is actually, because it doesn't seem to be useful except as a stand-alone thing. | 20:03 |
| gnarface | (and i'm not even using pulseaudio either, but i'm sure that does complicate the situation more) | 20:04 |
| gnarface | i basically ended up just leaving the timidity sysvinit service disabled and writing a wrapper script for dosbox that pre-launches timidity and closes it afterwards | 20:06 |
| gnarface | (i don't consider this a big deal at this point anymore because i already needed to keep a bucket of wrapper scripts for a dozen stupid wine things anyway) | 20:09 |
| greenjeans | greenjeans also keeps a handy bucket o' scripts onhand, lol | 20:35 |
| Afdal | maybe I should learn about wrappers... | 21:14 |
| Afdal | I don't really like the idea of a background process running all the time when I'm not using it anyway... | 21:14 |
| gnarface | Afdal: go into your ~/.bash_profile and find this block then uncomment it: https://paste.debian.net/1369147/ | 21:16 |
| gnarface | (then relog) | 21:16 |
| Afdal | uhhh what's that do | 21:16 |
| gnarface | after that, just create ~/bin and anything executable in there will tab-complete like a stock system executable | 21:17 |
| gnarface | it's not required to do this, it's just a convenient place you can keep all your wrapper scripts | 21:17 |
| gnarface | the comment literally tells you what it does | 21:17 |
| Afdal | oh okay | 21:18 |
| Afdal | hmm | 21:18 |
| Afdal | I don't really like to keep all my binaries in my home directory though <.< | 21:18 |
| gnarface | they're not necessarily binaries, they can just be shell scripts. here's an example of my dosbox wrapper script. https://paste.debian.net/1369148/ | 21:18 |
| gnarface | (ignore the "ALSA_GNAR" thing, that's an unrelated fix for a stupid alsa driver snafu) | 21:19 |
| Afdal | so the basics of a wrapper script are... | 21:20 |
| gnarface | it calls the system stock binary but adds some extra commands and/or environment variables to customize the behavior to your purposes | 21:20 |
| Afdal | #1 start the process you want running before the program, #2 start the program (you can close it through its own GUI), #3 close the process you wanted running during the program | 21:21 |
| gnarface | this one just starts timidity first and keeps track of the PID so it can stop it automatically after you exit dosbox | 21:21 |
| Afdal | is that right | 21:21 |
| Afdal | ah, you need to keep track of the process id | 21:21 |
| gnarface | well, you don't need to but that's the fundamentally more elegant way | 21:21 |
| gnarface | you could hardcode it to call "killall timidity" or whatever but that's ghetto | 21:21 |
| gnarface | you got the idea though | 21:21 |
| gnarface | this is very basic scripting, you can handle it, and it'll be a good stepping stone to fancier stuff | 21:21 |
| Afdal | I have already written fancier bash scripts than this :) | 21:22 |
| Afdal | just not familiar with wrappers | 21:22 |
| gnarface | don't get scared of the terminology, it's nothing really fancy. i used to balk at the notion of having to remember i have a bunch of wrapper scripts too, but somewhat ironically once i needed more than one of them it stopped being a problem | 21:23 |
| gnarface | most my wrapper scripts just add extra environment variables | 21:23 |
| Afdal | Since you say you use timidity for a wine a lot | 21:24 |
| greenjeans | point of order: the script as pasted is not a bash script | 21:24 |
| greenjeans | dash FTW | 21:24 |
| Afdal | maybe you can help me figure out how to get wine to use the right sound port for timidity | 21:24 |
| gnarface | ...stuff that's only relevant to that one program that i don't want cluttering up the global environment constantly, etc | 21:24 |
| Afdal | this is more complicated than I was expected >.> | 21:24 |
| Afdal | do you have to set it through the windows registry editor? | 21:24 |
| gnarface | Afdal: oh, a point of clarification, i use timidity for dosbox. i just also use wrappers for wine, but i don't use timidity with wine | 21:25 |
| Afdal | oh okay | 21:25 |
| gnarface | i'm not sure i have any wine games that use midi currently... | 21:25 |
| gnarface | hmm, well with dosbox it's quite simple to set these three lines in the dosbox config: | 21:27 |
| gnarface | mpu401=intelligent | 21:27 |
| gnarface | mididevice=alsa | 21:27 |
| gnarface | midiconfig=128:0 | 21:27 |
| gnarface | those work fine with timidity defaults, though games themselves typically also have to be specifically told to use midi on a per-game basis | 21:28 |
| gnarface | i'm not sure what the wine equivalent would be for this, since the stuff i'm playing in wine typically isn't this old | 21:28 |
| gnarface | it might "just work" | 21:29 |
| Afdal | Wine stuff is setup by default to listen to the uh | 21:29 |
| Afdal | midi through port 0 | 21:30 |
| Afdal | somehow you've got to tell it to look on one of the virtual ports established by timidity... | 21:30 |
| Afdal | err, not listen to | 21:30 |
| Afdal | but output to :) | 21:30 |
| Afdal | winehq's wiki page on midi setup needs to be better written tbh -_- | 21:32 |
| Afdal | what's this -Os >/dev/null 2>&1 & stuff at the end of your timidity line gnarface | 21:44 |
| gnarface | Afdal: "-Os" is output to ALSA, and the rest of the line after that is just to background timidity and discard any console noise it might generate. there's a shorthand version of the syntax to do the same thing but ironically the long form is easier for me to remember | 21:46 |
| gnarface | literally, ">/dev/null" redirects stdout to /dev/null, and "2>&1" redirects stderr to [same place as stdout], and then & backgrounds | 21:50 |
| gnarface | those are all shell syntax parts, not specific to timidity | 21:52 |
| Afdal | thanks :) | 21:53 |
| gnarface | np | 21:53 |
| plasma41 | Afdal: Speaking of wrappers, I recommend checking out Section 5.1, "Customizing the cal command", of Kernighan' & Pike's "The UNIX Programming Environment". | 23:04 |
| Afdal | uh | 23:04 |
| Afdal | is this a book >_> | 23:04 |
| Afdal | I've never even heard of the cal command <_< | 23:04 |
| plasma41 | Afdal: A quite famous book. The cal program itself isn't important in particular, it's just used as an example program which has a subpar interface that can be made more pleasant using a wrapper. | 23:07 |
| Afdal | is this cal like calories | 23:10 |
| Afdal | or calcium... | 23:10 |
| plasma41 | calendar | 23:14 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!