Hacker Public Radio

Hacker Public Radio
Hacker Public Radio

Hacker Public Radio is an podcast that releases shows every weekday Monday through Friday. Our shows are produced by the community (you) and can be on any topic that are of interest to hackers and hobbyists.

Episódios

  1. HÁ 1 DIA

    HPR4329: Maintaining The Remote System

    Maintaining The Remote System I have renamed the project Libre Indie Archive because the name theindiearchive is already someone else's domain. I never would have renamed The Indie Archive but I do think that Libre Indie Archive is more descriptive, hence, better. I am getting close to a pre beta push up to codeberg. Anyone following along who wants to help test, you can do this with two or three old systems. Let me know. Email hairylarry@gmail.com or on Mastodon I am @hairylarry@gamerplus.org. I have decided to develop and document for Xubuntu first and here's the reasons why. I bought an older HP small form factor office system with 4 Gigabytes of ram. HP Compaq 4000 Pro Pentium Dual-Core E6600 3.06GHz 4GB RAM Thirty dollars on ebay with shipping and taxes. I was testing Libre Indie Archive on it. Because of the age of the system Ubuntu wouldn't install. I tested it with some BSD systems and installed Indie Archive without a GUI. Ghost BSD didn't install but Midnight BSD did install so I used the Midnight BSD GUI and installed Indie Archive. None of this was easy for me because I'm a BSD newb and unless you already use BSD I can't recommend it for Libre Indie Archive. Remember, not all indie producers are computer programmers, and I want Indie Archive to work for those producers as well as for the computer savvy. Then on a whim I thought I would try the Xubuntu 24.04 distro and it installed no problems. Thanks XFCE for keeping it light. The other reason I am developing and documenting for Xubuntu is that I can use the Xubuntu install document and install on Ubuntu or Debian with only minor differences. I know because I tried it. This is probably also true for other Debian and Ubuntu derived distributions. So, if you want to help, you could take the Xubuntu install document and see if it works on other distributions. Write down what you had to change and let me know. I plan on making an install checklist out of the install document and it would be great to have a checklist with the actual commands for several distributions. So, that was the intro. Now on to the topic. I am planning on installing remotenear and remotefar systems, remotenear being a short drive away (or maybe in your home if your studio is not in your home, like mine) and the remotefar further away to avoid losing data in the case of a regional catastrophe like flood, fire, tornado, or hurricane. Still even a short drive is not what I want to do any time there might be something I need to check on a remote system so I have devised a way to manage it from the secondary system. When a remote system is delivered to a new location it will be headless. No monitor, no keyboard, and no mouse. At the remote location it is plugged into a UPS and attached to the network with an ethernet cable and attached to the UPS with a usb cable. Then it is turned on. Even without a keyboard or a mouse there is still some local control of the system available. As part of the remote system install we go into the power management settings and next to "when power button is pressed" we select shutdown. So, a short press on the power button initiates a Xubuntu shutdown just like the shutdown that you get from the menu or Alt F4. If that doesn't work a long press of the power button will turn the system off. This is like unplugging the system or losing power and is not recommended but Xubuntu will rebuild the file structure when the system is restarted. And if you do lose power the UPS will send a signal to the computer shutting it down with a controlled shutdown, just like a short press of the

  2. HÁ 2 DIAS

    HPR4328: Use SELinux the easy way

    The most basic security toggle on your Linux computer is the setenforce command. Using just a single setenforce instruction, you can configure SELinux to allow a violation it would normally prevent. There are two states: Enabled and Permissive. By default, SELinux is Enabled (also represented as 1 when using Boolean values). To set SELinux to permissive mode: $ sudo setenforce Permissive When something works in Permissive mode, you've successfully identified the symptom, but you haven't fixed the problem yet. Activate Enforcing mode again: $ sudo setenforce Enforcing Check the status of SELinux You can check the state of SELinux at any time using the sestatus command: $ sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: enforcing [...] Look at labels and contexts If you have a running Linux system, then you have an example of what SELinux requires for normal operation. You don't have to learn about security contexts or memorize labels. For most anything you try to do on your computer, there are likely already files doing something similar. Use those files as templates. You can look at the security labels of any file you have access to by using the -Z (that's a capital Z) option of ls: $ touch hellotouch hello.txt $ ls -Z hello.txt unconfined_u:object_r:user_home_t:s0 hello An empty file created by a user in the user's own home directory has, as you might expect, a very specific security profile. Even with the executable bit set, that file would not be permitted to run as a systemwide service. It just doesn't have the correct security context. If you use an ll alias, try adding the -Z option to its option list so you get used to seeing SELinux labels. The more you see what labels exist on your system, and how they relate to various system roles, you're more likely to recognize when they're wrong. Copy contexts Suppose you were developing a custom SELinux service for your laptop. You've written a shell script, a service file, and you've placed them in the appropriate system locations. You're also careful to set ownership and permissions correctly. But no matter what you do, you get errors when attempting to start the service. You suspect that SELinux might be preventing an unrecognized service from running. That would normally be appreciated, but in this case you want to make an exception. First, confirm that the service runs successfully with SELinux in Permissive mode: $ sudo setenforce Permissive $ sestatus | grep Current Current mode: permissive $ sudo systemctl start hello.service || echo "fail" $ $ sudo setenforce Enforcing Then look at the files you've created using the -Z and compare them with other files that you know to be working properly. Note the differences: $ ls -Z /usr/lib/systemd/system/hello.service unconfined_u:object_r:systemd_unit_file_t:s0 $ ls -Z /usr/lib/systemd/system/rdisc.service system_u:object_r:rdisc_unit_file_t:s0 The working service (rdisc.service in this example, chosen at random) features the system_u label as well as a special rdisc_unit_file_t label. Suppose you know from previous experience with ls -Z that a common SELinux label for systemd serv

  3. HÁ 3 DIAS

    HPR4327: Chatting with Sgoti

    Chatting wth Sgoti Sgoti talks about SSH and Github. openbsd: PreferredAuthentications Specifies the order in which the client should try authentication methods. gssapi-with-mic,hostbased,publickey,keyboard-interactive,password openbsd: HostKeyAlgorithms $ssh -Q HostKeyAlgorithms; ssh-ed25519 ssh-ed25519-cert-v01@openssh.com sk-ssh-ed25519@openssh.com sk-ssh-ed25519-cert-v01@openssh.com ssh-rsa rsa-sha2-256 rsa-sha2-512 ssh-dss ecdsa-sha2-nistp256 ecdsa-sha2-nistp384 ecdsa-sha2-nistp521 sk-ecdsa-sha2-nistp256@openssh.com webauthn-sk-ecdsa-sha2-nistp256@openssh.com ssh-rsa-cert-v01@openssh.com rsa-sha2-256-cert-v01@openssh.com rsa-sha2-512-cert-v01@openssh.com ssh-dss-cert-v01@openssh.com ecdsa-sha2-nistp256-cert-v01@openssh.com ecdsa-sha2-nistp384-cert-v01@openssh.com ecdsa-sha2-nistp521-cert-v01@openssh.com sk-ecdsa-sha2-nistp256-cert-v01@openssh.com openbsd: IdentitiesOnly Specifies that ssh(1) should only use the configured authentication identity and certificate files (either the default files, or those explicitly configured in the ssh_config files or passed on the ssh(1) command-line), even if ssh-agent(1) or a PKCS11Provider or SecurityKeyProvider offers more identities. The argument to this keyword must be yes or no (the default). This option is intended for situations where ssh-agent offers many different identities. Sample ssh config. #Github Primary Yubikey Host github User git HostName github.com Port 22 IdentityFile ~/.ssh/github-yubikey-0 #Github Secondary Yubikey Host github User git HostName github.com Port 22 IdentityFile ~/.ssh/github-yubikey-1 #Global properties. Host * PubkeyAuthentication=yes PreferredAuthentications=publickey,keyboard-interactive PubkeyAcceptedAlgorithms=sk-ssh-ed25519@openssh.com,ssh-ed25519,rsa-sha2-512 #ssh-ed25519 #ssh-ed25519-cert-v01@openssh.com #sk-ssh-ed25519@openssh.com #sk-ssh-ed25519-cert-v01@openssh.com #ssh-rsa ssh-keygen -t ed25519-sk -C "user@domain.tld" -f ~/.ssh/github-yubikey-0; ssh-keygen -t ed25519-sk -C "user@domain.tld" -f ~/.ssh/github-yubikey-1; chmod --change =400 ~/.ssh/github*; #Owner only! lawrencesystems: SSH with YubiKey FIDO U2F Authentication. yubico: YubiKey 5 Series github: Generating a new SSH key and adding it to the ssh-ag

  4. 27 DE FEV.

    HPR4324: 24-25 New Years Eve show episode 2

    mumble: Official website of the Mumble project wikipedia:) Mumble (software) from Wikipedia ncbi: Generalisable 3D printing error detection and correction via multi-head neural networks liqcreate: Resin 3D-printing: Ec, Dp, cure depth & more explained tomshardware: How to Fix 3D Prints Not Sticking to the Bed simplify3d: Not Sticking to the Bed tinkercad: Tinkercad is a free web app for 3D design, electronics, and coding. etherpad: Etherpad is a highly customizable open source online editor providing collaborative editing in really real-time. jitsi: More secure, more flexible, and completely free video conferencing openai: Whisper is an automatic speech recognition (ASR) system raspberrypi: We are Raspberry Pi. We make computers. wikipedia: ESP32 hamuniverse: Tools, test equipment and shack accessories for the new ham radio operator dxzone: Radio Tools and Utilities for amateur radio operators dxengineering: Amateur Radio Equipment & Tools morsecode: Morse Code Keyer wikipedia: Morse code inksystem: CISS - continuous ink supply system wikipedia: Continuous ink system wikipedia: Three-phase electric power archives: Housing in New Zealand teara: Early houses... of New Zealand freedesktop: PulseAudio Volume Control kde: Plasma is a Desktop f-droid: What is F-Droid? i3wm: i3 is a tiling window manager, completely written from scratch. samsung: Galaxy S23 android: Android Debug Bridge (adb) wikipedia: Android Debug Bridge (adb) dolby: Dolby On: Record Dolby Sound and Video slackware: The Slackware Linux Project fedoraproject: Fedora Linux | The Fedora Project qtractor: Qtractor An Audio/MIDI multi-track sequencer ardour: Recording - Ardour DAW snapcraft: Snapcraft - Snaps are universal Linux packages wiki

4,2
de 5
34 avaliações

Sobre

Hacker Public Radio is an podcast that releases shows every weekday Monday through Friday. Our shows are produced by the community (you) and can be on any topic that are of interest to hackers and hobbyists.

Você também pode gostar de

Para ouvir episódios explícitos, inicie sessão.

Fique por dentro deste podcast

Inicie sessão ou crie uma conta para seguir podcasts, salvar episódios e receber as atualizações mais recentes.

Selecionar um país ou região

África, Oriente Médio e Índia

Ásia‑Pacífico

Europa

América Latina e Caribe

Estados Unidos e Canadá