Powered by RND
PodcastsUddannelseHacker Public Radio

Hacker Public Radio

Hacker Public Radio
Hacker Public Radio
Seneste episode

Tilgængelige episoder

5 af 126
  • HPR4506: The UCSD P-System Operating System
    This show has been flagged as Clean by the host. 01 Overview This episode is about the UCSD p-System operating system. UCSD p-System is an operating system from the late 1970s which carried on into the 1980s. It ran on a variety of different micro and mini computers. The notable thing about it is that it ran programs on a portable virtual machine rather than directly on the native hardware. This podcast episode overview will give a very brief overview of the operating system, its features, and its history. This episode is for people who are interested in some of the more obscure history of the early microcomputer era. Don't expect to find something here that you can put to use in a practical way. 02 Pascal and UCSD 03 Commercialization 04 UCSD p-System Versions 05 Hosted Versions 06 Basic Concepts 07 File System 08 Virtual Memory and Multitasking 09 Architecture Independence with P-Code 10 Programming languages 11 The Fading Away of the p-System and its Demise 12 A Quick Tour of the p-System - Running it on Modern Hardware 13 A Quick Tour of the p-System - the User Interface 14 A Quick Tour of the p-System - OS Level Menu 15 A Quick Tour of the p-System - ASE Editor 16 A Quick Tour of the p-System - Filer 17 A Quick Tour of the p-System - Xecute 18 A Quick Tour of the p-System - DOS Filer 19 Conclusion The UCSD p-System is an example of an operating system from the early days of microcomputers that did not follow the conventions that we are used to today. It had features that were in many ways ahead of its time. Here are some examples of this. It was almost entirely written in a high level language, Pascal. Programs compiled to p-code (or Pascal code) that ran on an architecture indepedent virtual machine. Performance critical parts of the p-code could be compiled to native code. The user interface did not use a command line, indeed there was none. Instead it used a menu driven user interface. On the other hand it remained stuck on 8 bit limitations in a 16 bit world. It was closed source proprietary product, and when the vendor lost interest, the product died. It's an interesting bit of history, but I can't really recommend that anyone should expect to do anything useful with it today. I still have a copy that I bought when it was a current product, but it has been many years since I even looked at it, and I only resusitated it for the sake of making an HPR episode. 20 Adendum - Performance Benchmarks Provide feedback on this episode.
    --------  
  • HPR4505: New site - looks great!
    This show has been flagged as Clean by the host. New site is live as of 2025-10-22 Thanks to Archer72 (Mark Rice), Dave Morris, Ken Fallon, kwoot, Lee Hanken, and especially Roan Horning . Mailing list mention of blinding white page with use of the DarkReader Firefox plugin Go to More tab Set to Filter+ Go back to Filter tab Set Contrast to 50 - 60% Dark Reader settings Provide feedback on this episode.
    --------  
  • HPR4504: YouTube Subscriptions 2025 #7
    This show has been flagged as Clean by the host. I am subscribed to a number of YouTube channels, and I am sharing them with you. Links: https://www.youtube.com/@isaacarthurSFIA https://www.youtube.com/@lordtopcat https://www.youtube.com/@peevmania https://www.youtube.com/@jenniebreeden https://www.youtube.com/@Joe_Brennan_ https://www.youtube.com/@acousticeidolon https://www.youtube.com/@jonathabrooke https://www.youtube.com/@JoshSnares https://www.youtube.com/@JumboPixel https://www.youtube.com/@KaraandNate https://www.youtube.com/@katetectonics https://www.youtube.com/@kenmichaelsradio748 https://www.youtube.com/@KevinStratvert https://www.youtube.com/@KyleJones https://www.youtube.com/@LaLidoLoca https://www.youtube.com/@LakeStreetDive https://www.youtube.com/@LarkinPoe https://www.palain.com/ Provide feedback on this episode.
    --------  
  • HPR4503: One time passwords using oathtool
    This show has been flagged as Clean by the host. Oathtool 06 OATH Options and Oathtool The OATH standard has several options. You need to know which OATH options the site you wish to log into uses in order to use OATH. 07 Options - TOTP versus HOTP There are two different types of OATH one time passwords, HOTP and TOTP. HOTP uses a counter. I won't go into more detail on HOTP as I haven't come across anyone using it. TOTP uses the current time instead of a counter. The time is fed into the OATH algorithm along with the shared secret to generate a new password on both ends of the connection. All the instances of OATH that I am familiar with use TOTP. 08 TOTP Mode Totp has different "modes". These modes are hash encoding algorithms such as SHA1, SHA256, or SHA512. The correct mode must be selected in order to log in using OATH with TOTP. 09 Encoding - Hex versus Base32 Both ends of the connection must be initialized with a shared secret or key which is required as part of the OATH algorithm. This key could be encoded in one of two forms, either hexadecimal or base32. Web sites often do not document which encoding method they are using. If you cannot determine the encoding of the key by simply looking at it you may need to use trial and error during your first OATH log in attempts to see which type of key has been used. 10 Github and Pypi Options Github and Pypi are two of the most prominent web sites using OATH. Both use the same options, TOTP with SHA1 mode, and base32 encoding. 11 Using Oathtool oathtool is a simple command line application which generates one time passwords for use with OATH. It can be run in a terminal. However, can also be turned into a simple GUI application using Zenity. Will discuss this in more detail later. By default oathtool uses hotp and hex encoding. To use totp and base32 encoding you must specify these on the command line. To specify base32 encoding for use with for example Github, pass the "-b" or "--base32" argument on the command line. To specify TOTP, pass the "--totp" argument on the command line. By default, oathtool uses SHA1 with totp, so you don't need to specify that if you require SHA1. If you need a different TOTP mode, you specify that as part of the TOTP argument separated by an "=" character. For example "--totp=SHA256". 12 Oathtool Example Here is a simple example of using oathtool to create a one time password to use with Github or Pypi. Open a terminal and type the following. oathtool -b --totp SOMEBIGBASE32SECRETCODE The one time password will be printed out in the terminal. You can try this out without using a valid key so long as it is a valid base32 string. When used with a valid key you then enter that one time password into Github, Pypi, or other web site where it asks for the one time password. Note that I have not covered in the above how to store and retrieve the key securely, as that is too big of a topic to cover here. 13 Zenity Example Oathtool is a command line application, but if you are using Linux it is simple to convert it into a GUI application by using "Zenity". Zenity is a simple to use package that creates GUI windows on the command line or in a shell script. There are two steps to the proceess. First create the OTP from the key by using oathtool and save it in a variable. Next, call a Zenity "info" window with the OTP as part of the provided text. You can now copy and paste the OTP from the window into your web browser. To close the window, click on the "OK" button. See the previous note on storing the key securely. hprcode=$(oathtool -b --totp SOMEBIGBASE32SECRETCODE) zenity --info --width=150 --title="HPR 2FA" --text="<big>2FA code is:</big> \n\n $hprcode \n" If you are using Gnome you can make the script launchable from the desktop by creading a ".desktop" file in the "Desktop" directory. Provide feedback on this episode.
    --------  
  • HPR4502: Cheap Yellow Display Project Part 3: Reverse beacon network
    This show has been flagged as Clean by the host. Hello, again. This is Trey. Welcome to part 3 in my Cheap Yellow Display (CYD) Project series. You can find Part 1 in episode 4472 and Part 2 in episode 4488. We previously left our handy hero searching for a solution to an amateur radio signal propagation dilemma, while he is trying to become proficient with Morse code. The CYD technology is simmering in the back of his brain – an answer in search of a problem. Hah! I love trying to create the feel of a vintage radio or television series with the intro and outro for these episodes. But I am by no means the hero. I am simply Trey – a grumpy old man and tinkerer. Instead, the real hero in this episode is Keith VE3SVQ-THE SHAKY KEY on YouTube. So.... Let's see. Where were we? Oh yes. I have been trying to learn Morse code -.-. --.- -.-. --.- (CQ CQ) That was me, tapping out "CQ CQ" in Morse code using the practice set I keep on my desk. This consists of a set of code paddles, connected to an Arduino Nano, which I built several years ago based what I learned watching Code Practice Oscillator; Aka: The Three Arduinos on Jmhrvy1947's YouTube Channel, and based on the code from his GitHub https://github.com/jmharvey1/ArduinoCPO . I did need to make modifications, both to support the Ardunio Nano on which I chose to run it, and for my own sanity, as the way that I learned to write code for Ardunio is very different. I focus on readability and flexibility. You can see these changes on my own GitHub ( https://github.com/jttrey3/PracticeOscillator/blob/main/PracticeOscillator.ino ) Anyway, I have been studying. I have been watching videos. I have been practicing. I might actually be learning some of this stuff. If you are interested in more details about the resources I am using, leave a comment for this episode, or drop me an email using the address in my profile, and I may record an episode about it. The result is that I have been learning. But also, the google and YouTube algorithms have been learning about me. And they have started to feed me more videos about Morse code. It is both helpful, and super creepy at the same time. So one day, when I opened YouTube, a title in my feed caught my eye. " NEW CW OP USE THE REVERSE BEACON NETWORK TO IMPROVE YOUR CODE ". I said to myself, "Self, this could be interesting." I watched Keith's video and learned about the Reverse Beacon Network . According to their website, "The Reverse Beacon Network (RBN) is a revolutionary new idea. Instead of beacons actively transmitting signals, the RBN is a network of stations listening to the bands and reporting what stations they hear, when and how well." Let's pause for a second and discuss amateur radio beacons. These are stations which repeatedly broadcast their identity on dedicated frequencies. Other operators around the world, who hear a beacon, can evaluate the signal propagation between their station and the beacon location. The RBN is just the opposite. Here, the station operator can transmit a test signal with their call sign, using CW or other digital modes. Then, they can look at the RBN website to see which RBN listening stations received their transmission, and even get a signal report. On the main page of the RBN website, one can observe a world map with paths showing where signals were received, and where they originated based on the registered grid square of the originating call sign. The table displayed below the map reveals the sending and receiving call signs, their distance apart (In miles or kilometers), the frequency, the mode, the type of transmission, the signal to noise ratio, the speed of the transmission, and the time/date using UTC. This information is collected by a network of volunteer reverse beacon receiving stations all over the world, which monitor the various radio bands, decode transmissions of CW (Morse code), RTTY (Radio Teletype), and PSK31 or PSK63 (Digital modes using Phase Shift Keying). These receiving stations report what they receive as well as the signal strength back into the Reverse Beacon Network to be recorded and published over the internet. Dave Casler discussed the RBN back in 2016 on his YouTube video The Ham Radio Reverse Beacon Network, AD#32 . This gives very good detail of how the network works. This sounds like exactly what I have been looking for. All I need to do is come up with a way to reliably, accurately, and consistently transmit "CQ CQ CQ TEST DE" followed by my call sign three times at a constant 20 words per minute (WPM). If I can do this a few times, I can then check the RBN to see where I was received. By including the "TEST" string, recipients know that I do not wish to start a conversation. I can get accurate reporting of where my signal is going and how strong it is. But remember that my morse code skills are still inadequate. And my radios do not have "Keyer memories" like those which can be found in higher end transceivers like the Icom 7300, enabling programmed messages to be sent at the touch of a button. But there is a fairly inexpensive solution to this problem. One which has been nagging at the back of my mind. Maybe, I could use the Cheap Yellow Display to effectively add "Keyer memory" to any of my radios by simply plugging it in to the code key input port. These stored messages could be transmitted by simply touching their specific icon on the touch screen. Now we have a plan. But how will we do it? What else will we need to learn? Will it even work? Tune in to the next episode in the series to find out the answers to some of these questions and more! Provide feedback on this episode.
    --------  

Flere Uddannelse podcasts

Om 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.
Podcast-websted

Lyt til Hacker Public Radio, Relationer og mange andre podcasts fra hele verden med radio.dk-appen

Hent den gratis radio.dk-app

  • Bogmærke stationer og podcasts
  • Stream via Wi-Fi eller Bluetooth
  • Understøtter Carplay & Android Auto
  • Mange andre app-funktioner
Juridiske forhold
Social
v7.23.11 | © 2007-2025 radio.de GmbH
Generated: 11/10/2025 - 7:58:28 PM