Podcasts about hashes

Using Gemma4 with Ollama - Testing File Hash Analysis and Recommendations with AI https://isc.sans.edu/diary/Using%20Gemma4%20with%20Ollama%20-%20Testing%20File%20Hash%20Analysis%20and%20Recommendations%20with%20AI/33242 CPU Privilege Escalation https://github.com/xoreaxeaxeax/smiiiiiiiiiiiiiiii https://github.com/xoreaxeaxeax/skitter-creek-bath-salts GeoServer Vulnerability https://x.com/q1uf3ng/status/2087490992723407096 Windows USB Driver Vulnerability https://x.com/0xedh/status/2085842285481062887 My Upcoming Classes https://www.sans.org/profiles/dr-johannes-ullrich

This show has been flagged as Explicit by the host. New hosts There were no new hosts this month. Last Month's Shows Id Day Date Title Host 4673 Wed 2026-07-01 First contact conversation Archer72 4674 Thu 2026-07-02 Audiobooks Ahuka 4675 Fri 2026-07-03 Yard Inflatables operat0r 4676 Mon 2026-07-06 HPR Community News for June 2026 HPR Volunteers 4677 Tue 2026-07-07 UNIX Curio #10 - Checksums and Hashes Vance 4678 Wed 2026-07-08 High Resolution Elapsed Time in Shell Scripts Whiskeyjack 4679 Thu 2026-07-09 HPR Beer Garden 15 - Double IPA Kevie 4680 Fri 2026-07-10 Robert A. Heinlein: The Future History, Part 2 Ahuka 4681 Mon 2026-07-13 My Disabilities Antoine 4682 Tue 2026-07-14 Behind the Keyboard: A Cybersecurity Operator's Real-World Workflow operat0r 4683 Wed 2026-07-15 Recording the hallway track Ken Fallon 4684 Thu 2026-07-16 Sim Racing on the cheap! operat0r 4685 Fri 2026-07-17 Listening to SSB stations in the early 1980s Lennart Benschop 4686 Mon 2026-07-20 Debugging Security Cameras: Firmware Updates, Python Scripts and Windows Workarounds operat0r 4687 Tue 2026-07-21 UNIX Curio #11 - Merging Files Vance 4688 Wed 2026-07-22 Downloading Podcasts with a Shell Script Whiskeyjack 4689 Thu 2026-07-23 Cheap Yellow Display Project Part 8: Writing the code Trey 4690 Fri 2026-07-24 Playing Civilization V, Part 14 Ahuka 4691 Mon 2026-07-27 Viva la Coda Lee 4692 Tue 2026-07-28 Noise Music Tutorial 2: Using Audacity to Make Noise TheDUDE 4693 Wed 2026-07-29 Amateur Radio Field Days Archer72 4694 Thu 2026-07-30 HPR Beer Garden 16 - Belgian Blonde Kevie 4695 Fri 2026-07-31 Try not to buy a phone operat0r Comments this month Past shows hpr4644 (2026-05-21) "Response to comments on HPR4424: Newsboat..." by Archer72. Archer72 said: "Ken on Community Show HPR4676" (2026-07-06 13:48:39) Ken Fallon said: "hpr3962 :: It's your data" (2026-07-06 15:07:47) hpr4669 (2026-06-25) "HPR Beer Garden 14 - Super Strong Lager" by Kevie. The_Dud3 said: "Favorite Malt Liquores/Super Strong Lagers" (2026-07-22 02:07:59) hpr4672 (2026-06-30) "Hey Mum, I'm on Spotify ! " by Ken Fallon. Archer72 said: "Another great show!" (2026-07-08 09:46:44) This month's shows hpr4674 (2026-07-02) "Audiobooks" by Ahuka. The Librarian said: "Ook ?" (2026-07-02 10:50:38) hpr4677 (2026-07-07) "UNIX Curio #10 - Checksums and Hashes" by Vance. xmanmonk said: "Another great show" (2026-07-07 21:17:41) candycanearter07 said: "cool show :D" (2026-07-08 11:32:04) Vance said: "Thanks, and systemd as a future topic" (2026-07-09 01:50:23) Vance said: "Sorry, xmanmonk" (2026-07-12 03:20:02) hpr4678 (2026-07-08) "High Resolution Elapsed Time in Shell Scripts" by Whiskeyjack. candycanearter07 said: "cool ep" (2026-07-09 14:38:32) Whiskeyjack said: "Reply to candycanearter07 on HPR4678" (2026-07-09 22:48:47) hpr4681 (2026-07-13) "My Disabilities" by Antoine. Archer72 said: "Reading" (2026-07-22 13:43:46) hpr4684 (2026-07-16) "Sim Racing on the cheap!" by operat0r. Jim DeVore said: "Great episode!" (2026-07-28 03:43:23) hpr4685 (2026-07-17) "Listening to SSB stations in the early 1980s" by Lennart Benschop. Lucinda said: "Thank you" (2026-07-21 10:53:42) hpr4688 (2026-07-22) "Downloading Podcasts with a Shell Script" by Whiskeyjack. candycanearter07 said: "cool solution" (2026-07-22 23:14:22) Whiskeyjack said: "Response to candycanearter07 in HPR4688" (2026-07-23 19:14:55) Mailing List discussions Policy decisions surrounding HPR are taken by the community as a whole. This discussion takes place on the Mailing List which is open to all HPR listeners and contributors. The discussions are open and available on the HPR server under Mailman. The threaded discussions this month can be found here: https://lists.hackerpublicradio.com/pipermail/hpr/2026-July/thread.html Events Calendar With the kind permission of LWN.net we are linking to The LWN.net Community Calendar. Quoting the site: This is the LWN.net community event calendar, where we track events of interest to people using and developing Linux and free software. Clicking on individual events will take you to the appropriate web page. Provide feedback on this episode.

This show has been flagged as Clean by the host. This series is dedicated to exploring little-known—and occasionally useful—trinkets lurking in the dusty corners of UNIX-like operating systems. In UNIX Curio #8 ( HPR episode 4657 ), I talked about using standard utilities to compare files. Left unmentioned, however, was a method commonly used today—the hash function. As I've stated in previous entries, while I am an engineer, I don't have a background in computer science, so my understanding of the mathematics is limited. But I can give a practical description of what a hash function does. It takes an input, performs a set of calculations on it, and produces an output. As hash functions are practically used, the input is a set of bytes, such as a file or another piece of data like a password. The output is a numerical value in a fixed range—most often, expressed as hexadecimal characters. Because this "hash value" can always be represented in a certain number of bytes, its length as printed is usually a constant number of characters, padded with leading zeros if necessary. This episode will not cover the use of hashes in programming, focusing instead on using them to validate data. A hash function, or more specifically, a cryptographic hash function, has an additional property. It should be very difficult to predict what changes to the input would be required to produce a specific change in the output. An older, related concept is called a "checksum". While these are designed to vary when the input data is damaged or digits are transposed, they do not necessarily have that last property mentioned for cryptographic hashes. You have probably already encountered a checksum, even if you didn't recognize it. On a 16-digit number assigned to a Mastercard or Visa 1 credit or debit card, the first six digits identify the card issuer (such as a bank), the next nine digits are assigned to you by the issuer, and the last digit is a check digit. The check digit is calculated using the values of the previous 15 digits, and it is a simple way to avoid typos in entering a card number. In another example, every Ethernet frame that your devices send or receive includes a checksum 2 to help ensure that the contents weren't scrambled in transit. This is 32 bits long and is called a cyclical redundancy check, commonly referred to as a CRC. A CRC is also used in many other places—for example, the .zip file format includes one for each archive member, and this allows a program extracting files from the archive to identify if any were damaged. Our UNIX Curio for today is another example, the cksum utility 3 . It generates a 32-bit CRC based on the Ethernet algorithm. It operates on either a named file or standard input and outputs the CRC value, the length of the input, and the pathname if a file was given as an argument. Unlike most modern hashing programs, the checksum is printed as a decimal integer and is not padded, so it can be anywhere from one to ten digits long. The length value is the number of bytes in the input (actually specified as the number of octets , as systems could potentially use a byte that isn't eight bits long), also expressed as a decimal integer. There are two major ways that one could use cksum to check the validity of a file. First, if you are transferring a file from one UNIX-like system to another, you could run cksum against it on both systems and check that the CRC and length are the same. The utility can also be given multiple filenames as arguments, which would generate a list that can then be compared. The second way would be for someone publishing a file or set of files to also publish the CRC values, lengths, and names so that people downloading them could verify that they match. However, I don't think the practice of publishing lists like this really started until more recent hash functions like MD5 and SHA-1 came about so it is unlikely that anyone would publish CRC values instead. The advantage of these tools should be pretty obvious in comparison to cmp , one of the utilities discussed in UNIX Curio #8. To verify a file using cmp , you need two files to compare—if you're trying to check a large file you downloaded, you would need to spend the time and bandwidth to download a second copy. And if they didn't match, you would have no idea which of the two, if either, was correct. By contrast, cksum is quicker to run, doesn't require downloading a massive amount of excess data, and if run against the original file, makes clear what the correct value is. This utility is a follow-on from a program called sum , which operated very much the same. I had a bit of trouble tracking down the exact development history, but what seems clear is that two different variants 4 were popular: a BSD version and a System V version. Both output 16-bit checksums, but used different algorithms so they didn't give the same results. Also, the BSD version printed the length of the input data as the number of 1,024-byte blocks, while the System V version instead gave a count of 512-byte blocks. (Some sources claim that System V sum generates a 32-bit checksum 5 , which could possibly be true internal to the algorithm, but I have tested several independent implementations of the utility and all of them output a 16-bit value for both the System V and BSD algorithms.) From what I can tell, the BSD version 6,7 came first; it was in 3BSD but probably appeared even earlier. An identical copy of BSD's sum was included with UNIX/32V 8,9 , which was AT&T's 1979 port of Seventh Edition UNIX to the VAX and became one of the ancestors of System III. The divergence seems to have started with System III, released in 1980; its version of the sum utility 10,11 changed to a new default algorithm, though it could be made to use the BSD algorithm via the -r option. System V looks to have kept the same behavior as System III. It's not clear to me why this algorithm is universally called the "System V algorithm" rather than the "System III algorithm"; perhaps it is because System V saw much more widespread use. Instead of trying to reconcile these differences, the POSIX committee decided to create a new utility with a unique name, use a separate algorithm entirely, and avoid the block-length dispute by printing the length in octets instead of blocks. I should point out that POSIX states that the CRC algorithm for cksum does not strictly meet the mathematical definition of a "checksum". I don't know enough to say exactly why it doesn't qualify or to say whether either of the sum algorithms do. However, in less-formal usage the term "checksum" has gathered the meaning of any value used to represent or validate a set of data, so I am fine with using it no matter the technical details of the algorithm. When two different inputs produce the same checksum or hash value, this is called a "collision". Because the output value has a limited range, there are an infinite number of possible inputs that could produce a collision. From a practical standpoint the possibilities are more limited—the majority of these inputs are larger than the number of atoms in the universe, which can't fit on any machine. Unlike a cryptographic hash algorithm, the CRC is not specifically designed to resist an attacker crafting a malicious input that would cause a collision. However, it should be sufficient to detect accidental damage. Programs implementing more modern cryptographic hash algorithms are superior to the checksum utilities in avoiding collisions (whether malicious or accidental), but there are still three advantages that the older programs have. First, a system running a historical operating system might not have the hash programs available, but is more likely to have cksum or sum already included. Second, the checksum values are much shorter than the hashes output by the newer programs, making them easier for a user to compare by looking at them. This advantage is not as great as it might appear at first, because a common way to check a hash these days is to save a list of hashes and filenames—the hash programs can use that and do the comparison themselves, sparing the user from having to validate it character by character. The third advantage is that cksum prints the input length in bytes. This greatly limits the number of inputs that could be maliciously crafted to create a collision. I did a moderate amount of research on implementations of modern cryptographic hash algorithms and found that some, such as MD5, SHA-1, and SHA-2, do use the length of the input (often termed "message length" in the literature) as part of the material fed in to the algorithm, but none of the hashing utilities present this length to the user as part of its output. There are two possible reasons for this that seem evident to me. First, if one is hashing a password, you would certainly not want to give a clear indication of its length—that would give any attacker a massive head start on guessing the password. However, that doesn't explain why one would avoid printing the input length for a file that is made publicly available. Second, it is convenient in many contexts, such as database entries or in software (such as git ), for the hash to be a fixed length. Including an extra value that can be of variable length would complicate those use cases. However, the length value could simply be dropped and they would be no worse off than they are currently. Historically on UNIX, password hashing was treated differently from checksumming files— the crypt() function 12 was used for passwords while sum and later cksum were used to confirm a file's integrity. So even rather early on, these two use cases employed algorithms with different properties, but I haven't dived into the history deeply enough to know how intentional this was. My discussion in this episode focuses on the file use case, so understand that I'm largely avoiding the topic of password hashing. Digital signatures are yet another use case, one that I'm ignoring entirely. Every few years, some security researcher declares a particular hash algorithm to be "broken" and that everyone should move over to a new one, which generally has a longer hash. While the larger hash space certainly reduces the opportunity for collisions, this disrupts workflows, such as publishing information about software releases by e-mail, which still tends to observe a 78-character limit on each line 13 , making it harder to include a list of hashes with filenames next to them. This is in addition to the work of modifying software and scripts to use the new algorithm and managing how to treat past data. It seems to me that publishing the input length along with the hash would make it far more difficult to craft a malicious input that matches both, but I haven't found discussion of that during my investigation. (See the Appendix for a possible implementation.) Perhaps someone listening can record a response episode for HPR explaining that. References: Payment card number https://en.wikipedia.org/wiki/Payment_card_number Ethernet frame: Frame check sequence https://en.wikipedia.org/wiki/Ethernet_frame#Frame_check_sequence Cksum specification https://pubs.opengroup.org/onlinepubs/009695399/utilities/cksum.html GNU coreutils manual: sum https://www.gnu.org/software/coreutils/manual/html_node/sum-invocation.html FreeBSD 15.0 sum manual page https://man.freebsd.org/cgi/man.cgi?query=sum&sektion=1&manpath=FreeBSD+15.0-RELEASE+and+Ports 3BSD sum manual page https://www.tuhs.org/cgi-bin/utree.pl?file=3BSD/usr/man/man1/sum.1 3BSD sum source https://www.tuhs.org/cgi-bin/utree.pl?file=3BSD/usr/src/cmd/sum.c UNIX/32V sum manual page https://www.tuhs.org/cgi-bin/utree.pl?file=32V/usr/man/man1/sum.1 UNIX/32V sum source https://www.tuhs.org/cgi-bin/utree.pl?file=32V/usr/src/cmd/sum.c System III sum manual page https://www.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/man/man1/sum.1 System III sum source https://www.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/cmd/sum.c Crypt specification https://pubs.opengroup.org/onlinepubs/009695399/functions/crypt.html RFC 2822: Internet Message Format: Line Length Limits https://datatracker.ietf.org/doc/html/rfc2822#section-2.1.1 OpenSSH 10.1 released https://lwn.net/ml/all/dd12623ae86aa5eb@cvs.openbsd.org/ Appendix The MD5 hash algorithm was (and still is) widely used, but many people characterize it as being "broken" and discourage its use. Let us imagine a variant of this, called MD5.L, where the normal MD5 hash is followed by a "." character and the input length expressed as a hexadecimal number. Take, for example, the e-mail message announcing the release of OpenSSH 10.1 14 . At the bottom, it includes an SHA-1 hash and an SHA-2 256-bit hash for the available gzipped tar files. That longer hash is encoded with Base64 because if it were given as a hexadecimal number, it would make the line longer than 78 bytes. The MD5.L hash of the file would be one character shorter than the SHA-1 hash, as shown below. (The extra length of the name makes them both consume the same number of characters. The hashes shown are for the "portable" version of OpenSSH.) Some people claim SHA-1 is also broken, seeking to have people use newer and longer hash functions. For an attacker to compromise MD5.L in this example, they would not only have to create a valid tar file compressed with gzip containing a malicious payload having the right MD5 hash, that file would have to be exactly 1,972,831 bytes long (the decimal equivalent of 1e1a5f). While there are still many possible inputs that could be tried (256 1972831 , to be exact*), this is far fewer than the infinite possibilities for plain MD5, SHA-1, or SHA-2. If for some reason it is super important to have a fixed hash length, let's imagine another variation called MD5+L. In this one, instead of L being the input length, it is the input length modulo one terabyte (2 40 bytes), which can be represented by 10 hexadecimal characters, left-padded with zeros. While this approach substantially increases the number of possible inputs an attacker could try, it is likely that an intended victim would notice that the file they downloaded is larger (or smaller) than expected by that much. The MD5+L hash is longer than a SHA-1 hash, but still shorter than a 256-bit SHA-2 hash. SHA1 (openssh-10.1p1.tar.gz) = 7fd17b99d1beffb47cd380d64079e920bb0bd91f SHA256 (openssh-10.1p1.tar.gz) = ufx6K4JXlGem8vQ+SoHI4d/aYU3bT5slWq/XAgu/B1g= MD5.L (openssh-10.1p1.tar.gz) = 80dd9bb00a86519934710d05903fdf07.1e1a5f MD5+L (openssh-10.1p1.tar.gz) = 80dd9bb00a86519934710d05903fdf07+00001e1a5f Of course, if MD5 is considered to be too weak even with the inclusion of the length, one could produce a ".L" or "+L" version of any hash function. However, longer hashes will end up running into the 78-character limit. *This is a number with 4.75 million digits that the bc utility on my laptop took almost 5 minutes to calculate. Provide feedback on this episode.

Warum werden Systeme langsam, obwohl die Hardware doch immer schneller wird? Und warum endet die vermeintlich einfache Lösung so oft in einem Stack-Wechsel, der neue Probleme schafft statt alte zu lösen? Genau da setzen wir in dieser Episode an. Wir schauen auf Indexstrukturen, Datenstrukturen und die oft übersehene Frage, wie Workload, Hardware, Lese- und Schreibzugriffe und Algorithmen zusammenhängen. Denn häufig ist nicht die Datenbank schuld, sondern die falsche Struktur für den falschen Job.In dieser Episode sprechen wir über Red Black Trees, B-Bäume, B-Plus-Bäume, Hash-Indizes, Trie, Radix Tree, Bitmap Index und Bloomfilter. Wir machen das nicht abstrakt, sondern mit konkreten Beispielen aus der Praxis. Etwa mit Nginx und Timeout-Management im Event-Loop, mit HTTP-Routern und Prefix-Suche, mit Git und Bloom Filtern für schnellere Dateipfad-Abfragen oder mit Alerting-Systemen und Hashmaps. Dabei geht es auch um Big O, Cache Lines, Range Queries, Rehashing, Performance-Basics und die Frage, wann Optimierung sinnvoll ist und wann sie nur Overengineering produziert.Wenn du besser verstehen willst, warum manche Software unter Last einknickt und wie du mit dem richtigen Datenmodell, sauberen Metriken und etwas Architekturverständnis deutlich weiter kommst, ist diese Folge für dich. Und vielleicht ist die wichtigste Erkenntnis am Ende gar nicht, welche Indexstruktur die beste ist, sondern dass du sie in deiner eigenen Codebase vermutlich längst benutzt, oft nur ohne es zu merken.Bonus: Blumenfilter sind keine Blumen und streng genommen nicht mal ein richtiger Index.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

Braden, Brock, and Dawson look back at the 2026 NFL Draft. Hear who they think made the best picks and who they think might've made some questionable decisions.

Join us for another exciting episode of the Between the Hashes Podcast, where Braden, Brock, and Dawson take a look at a big trade that happened last week. The Denver Broncos sent their first, third, and fourth-round picks in the upcoming NFL Draft to the Miami Dolphins for star wide receiver Jaylen Waddle. This addition gives Bo Nix another option in the passing game. Waddle is one of only 16 players since 2021 to record at least three 1,000-yard seasons, and he joins forces with Courtland Sutton, who had an impressive 1,017-yard season in 2025. Hear what the crew thinks of the move and where this puts the Broncos in title contention. They also discuss the Tennessee Titans, who have recently released their newly logo. The reaction has been mixed online, with fans split over whether the new look is an upgrade or downgrade. The crew reacts to the new logo and gives their thoughts on the design. All this and a complete first-round mock draft, packed with predictions and analysis from the crew on this week's episode of the Between the Hashes Podcast.

Last Friday, the Ravens made a big trade, acquiring Maxx Crosby from the Las Vegas Raiders. On Tuesday night, the Ravens "backed off" from the trade after he reportedly failed a physical, causing utter chaos within the league. How bad is Crosby's injury? How does this affect his trade value? Will the Raiders keep Crosby? Braden, Brock, and Dawson recap the chaos that has been the Maxx Crosby Trade Saga. Hear their thoughts on the situation and whether they think the Raiders will try to trade him somewhere else. All this and a deep dive on some of the bigger free agency moves on this episode of the Between the Hashes Podcast.

After seven seasons, the Kyler Murray era in Arizona will officially come to an end. The Cardinals have announced they will release the former first overall pick and are looking for the next QB to lead their franchise. Join Braden, Brock, and Dawson as they share their thoughts on this move by the Cardinals. Should the Cardinals pursue Malik Willis, explore options in the upcoming draft, or stick with Jacoby Brissett for another season? And who should consider taking a shot with Kyler Murray? All this and a recap on last week's NFL Draft Combine on this week's episode of Between the Hashes.

Braden and Dawson are back for another exciting episode of the Between the Hashes podcast as the NFL Offseason kicks into gear! With the NFL Combine taking center stage this week, they discuss which prospects to watch for and who has a good chancing of boosting their draft stock. They also look at the recent moves the Miami Dolphins have made, as it seems they are heading towards a rebuild, and explore who in the NFL might be franchise-tagged this offseason.

Join Braden, Brock, and Dawson on this week's Between the Hashes Podcast as they recap the Seahawks' dominant Super Bowl 60 win over the Patriots. They share their thoughts on Seattle's dominant win and what went wrong for New England. They discuss what the win means for Sam Darnold, who has had one of the biggest underdogs in NFL History, and what is next for Drake Maye, who struggled in every aspect of the game. All this and more on this week's episode of the Between the Hashes Podcast.

Super Bowl week is here, and the boys are excited to talk about the final game of the season! Join Braden, Brock, and Dawson as they preview Super Bowl 60 between the NFC Champion Seattle Seahawks and the AFC Champion New England Patriots. They share key storylines heading into the game, what each team would need to do to come home with the win, and reveal who they have taking home the Lombardi Trophy.

Braden and Dawson dive into the latest coaching moves across the NFL. As some franchises welcome new head coaches and others decide to make a change, we're set for a new look in the NFL coaching world. Braden and Dawson discuss the Buffalo Bills' decision to fire long-time head coach Sean McDermott. They will talk about what this move means for the team's future. They will also recap the thrilling action from last week's Divisional Round of the NFL Playoffs and preview the Conference Championship Weekend.

Join us for a recap of an entertaining Wild Card Weekend, filled with exciting matchups and individual performances. Braden, Brock, and Dawson dive deep into last week's games and will give their predictions for the upcoming Divisional Round. They'll also share their thoughts on the surprising news of Mike Tomlin stepping down as Head Coach of the Pittsburgh Steelers.

Wild Card Weekend kicks off this weekend, and the boys are ready to take a look at some of the most interesting Wild Card games! Join Braden, Brock, and Dawson as they preview each matchup and share their predictions on which teams they think will move on to the Divisional Round. Plus, hear their reaction to the shocking news of the Baltimore Ravens firing John Harbaugh. Where might he end up this offseason? All this and more on this week's bonus episode of the Between the Hashes Podcast.

As the 2025 NFL Regular Season wraps up, the offseason work has kicked into full gear for some franchises! The Atlanta Falcons, Cleveland Browns, Las Vegas Raiders, and Arizona Cardinals have all fired their coaches after disappointing seasons. Join Braden, Brock, and Dawson as they break down who these teams should look at as their next head coach and suggest what each team should do to improve their team this offseason. The boys also debate which opening is the most appealing coaching job for potential head coaching candidates.

Join Braden, Brock, and Dawson as they dive into the highlights of Week 17, highlighted by some of the most exciting finishes of the NFL season, and get ready for a thrilling final week of the 2025 regular season, with insights, analysis, and predictions you won't want to miss!

Join Braden, Brock, and Dawson as they tackle this week's biggest headlines in the NFL. With star players Patrick Mahomes of the Kansas City Chiefs and Micah Parsons of the Green Bay Packers sidelined for the season due to ACL tears, the boys discuss what is next for both teams and whether they will both be back in contention for a Super Bowl run sometime in the future. They also look ahead to the final three weeks of the regular season, sharing their predictions for the remaining matchups. They'll give you an inside scoop on what the playoff picture might look like if their predictions are correct.

The Indianapolis Colts started the season 8-2 and have since lost three straight, and just lost starting Quarterback Daniel Jones to an injury. In a last-ditch effort, the Colts signed Philip Rivers, who had been retired for almost five years. Braden and Dawson react to the recent struggles in Indianapolis and whether or not Rivers can help the Colts get back to their winning ways.

Join Braden, Brock, and Dawson as they dive into last week's exciting Thanksgiving and Black Friday games! They'll share their insights on the Cowboys' impressive winning streak and how the Bears pulled off a stunning upset against the Eagles. The guys will also break down the remaining five weeks of the NFL season, offering their game-by-game predictions. Tune in to discover just how wild the NFL Playoffs could be if all their predictions come true!

Join Braden, Brock, and Dawson as they break down another wild week in the NFL. In this episode, they look at the playoff picture and share who they think is playing their best football right now. Tune in to hear their thoughts on all the action.

After another disappointing performance by the Kansas City Chiefs, Between the Hashes co-host and Chiefs fan Dawson Livingston wants to start the conversation on whether or not the dynasty in Kansas City is over. Hear his thoughts on the Chiefs and if Braden or Brock agree with his concerns on the future of the franchise.

Braden and Dawson react to the news of the New York Giants moving on from Head Coach Brian Daboll. They recap his time in New York and discuss what is next for the Giants, who seem to be stuck in a rebuild.

Braden and Brock recap the chaotic week leading up to the NFL Trade Deadline. From the shocking news of Sauce Gardner being sent to Indianapolis to the strategic moves of the Chargers trading for an offensive lineman to replace the injured Joe Alt, the boys break down every trade that went down. They will spotlight some of the key trades that may change the outlook of some teams heading into the last half of the season, as well as some of the notable names that didn't get traded before the deadline. Hear who the Braden and Brock have as the winners and losers of this year's trade deadline, and whether or not any of these trades have changed their thoughts on certain teams as we get closer and closer to the NFL Playoffs.

Join Braden, Brock, and Dawson in this episode as they explore the latest developments leading up to the NFL Trade Deadline. They look at some of the recent trades that have already happened in the NFL world and share their thoughts on the moves. The boys also list some impactful players who might be on the trading block, discussing the potential impact these players' getting traded could have on the outlook for the second half of the NFL season.

Joe Flacco makes his debut as a Bengal and puts on a show as the Cincinnati Bengals defeat their division rival, the Pittsburgh Steelers. The boys discuss whether Flacco and the Bengals have a chance to make the playoffs and potentially make a playoff run, depending on Burrow's injury. The boys will also react to the impressive comeback by the Denver Broncos against the New York Giants and discuss which NFL head coaches might be on the hot seat as we approach the midway point of the season.

Braden and Dawson react to the Sunday Night game between the Kansas City Chiefs and the Detroit Lions, analyzing the intense gameplay and the controversial low number of penalties called throughout the game. They'll discuss whether Baker Mayfield has positioned himself as the MVP frontrunner and take a closer look at the Indianapolis Colts, who are proving themselves as legitimate contenders in the NFL with their recent performances. Join us as we break down these thrilling topics, assess team performances, and look ahead to what these developments mean for the rest of the season!

In this week's episode, the boys take a look at the thrilling action of last week's NFL games. We break down the Arizona Cardinals and how they were unable to hold onto a significant lead against the Tennessee Titans. Brock, our Cardinals fan, will give his thoughts on the game and share what he wants the team to do after another heartbreaking close loss. We also recap the electrifying finish from Monday Night's Chiefs vs. Jaguars game. We will discuss whether it was a big win for the Jaguars or a terrible loss for the Chiefs. Tune in as we break down the plays, analyze key performances, and discuss the implications of these games for the rest of the season!

With Malik Nabers now out for the season with a torn ACL, the boys discuss whether it is time to get rid of turf fields in the NFL. Hear their opinions on the situation along with other takes as they recap and react to Week 4.

Dawson and Braden recap what was an exciting and special teams-driven Week 3 of the NFL. They will give out their Player of the Week picks and update their power rankings after teams like the Green Bay Packers and Los Angeles Rams lose their first game of the season.

Week 2 is in the books, and there is a lot to talk about. Dawson, Braden and Brock break down some of the notable injuries in the NFL and what it could mean to some Super Bowl contending teams.

Dawson, Braden and Brock recap the results from week 1. They discuss which teams impressed them and what teams they might be worried about heading into week 2.

New name, same entertaining football podcast. Dawson, Braden, and Brock preview the upcoming NFL season, discussing their predictions for the playoffs, regular season awards, and who they believe will win Super Bowl LX. Tune in for their insights!

KeywordsBitcoin, mining, 256 Foundation, open source, technology, community, ASIC, market dynamics, predictions, educationSummaryIn this episode of Pod 256, the hosts discuss various aspects of the Bitcoin mining community, including updates on the 256 Foundation, experiences from a recent meetup in Belgrade, and innovations in mining technology. They explore the importance of open-source mining, the challenges posed by copycats, and the dynamics of the Bitcoin market. The conversation also touches on predictions for Bitcoin's future price and the psychological aspects of Bitcoin pricing, emphasizing the need for education in Bitcoin adoption.TakeawaysThe 256 Foundation is actively engaging with the Bitcoin community.Rod shares insights from a recent meetup in Belgrade, highlighting community spirit.Open-source mining technology is evolving with new innovations.The importance of user experience in mining software is emphasized.Market dynamics are leading to a race to the bottom in pricing.New ASIC designs are impacting the mining landscape.Manufacturers and sellers play a crucial role in the Bitcoin ecosystem.Navigating copycats and knockoffs is a challenge for open-source projects.The state of the Bitcoin network is constantly changing, with fluctuations in hash rate.Education is key to fostering Bitcoin adoption and understanding. Chapters00:00 Introduction and Meeting Updates04:14 Rod's European Adventures and Community Engagement08:31 Innovations in Mining Technology12:33 The Future of Mining and Open Source Solutions16:49 The Shift from Proprietary to Open Hardware19:31 The Rise of Digital Shovel and Blue Axe20:57 Pricing Trends in Bid Axes22:19 The Race to the Bottom in Mining Hardware23:41 The Future of ASIC Manufacturers25:39 Challenges of Open Source in Mining27:51 The Impact of Rapid Development on Copycats28:34 State of the Network and Market Predictions38:25 The Mysterious Disappearance of Hashing39:06 Exploring the Hashes and Their Impact40:25 Community Contributions and Support41:34 The Rise of Ocean and Its Innovations42:46 Mining Dynamics and Market Fluctuations44:09 Treasury Strategies in Bitcoin Mining45:47 Market Sentiment and Bitcoin's Future48:31 The Psychological Aspect of Bitcoin Valuation50:25 Education and Resources for New Investors51:38 Upcoming Events and Community Engagement

File Hashes Analysis with Power BI Guy explains in this diary how to analyze Cowrie honeypot file hashes using Microsoft's BI tool and what you may be able to discover using this tool. https://isc.sans.edu/diary/File%20Hashes%20Analysis%20with%20Power%20BI%20from%20Data%20Stored%20in%20DShield%20SIEM/31764 Apache Camel Vulnerability Apache released two patches for Camel in close succession. Initially, the vulnerability was only addressed for headers, but as Akamai discovered, it can also be exploited via query parameters. This vulnerability is trivial to exploit and leads to arbitrary code execution. https://www.akamai.com/blog/security-research/march-apache-camel-vulnerability-detections-and-mitigations Juniper Patches Junos Vulnerability Juniper patches an already exploited vulnerability in JunOS. However, to exploit the vulnerability, and attacker already needs privileged access. By exploiting the vulnerability, an attacker may completely compromised the device. https://supportportal.juniper.net/s/article/2025-03-Out-of-Cycle-Security-Bulletin-Junos-OS-A-local-attacker-with-shell-access-can-execute-arbitrary-code-CVE-2025-21590?language=en_US AMI Security Advisory AMI patched three vulnerabilities. One of the, an authentication bypass in Redfish, allows for a complete system compromise without authentication and is rated with a CVSS score of 10.0. https://go.ami.com/hubfs/Security%20Advisories/2025/AMI-SA-2025003.pdf

Tool Update: Sigs.py Jim updates sigs.py. The tool verifies hashes for files and automatically recognizes what hash is used. https://isc.sans.edu/diary/Tool%20update%3A%20sigs.py%20-%20added%20check%20mode/31706 Google Announcing Quantum Safe Digital Signatures in Cloud KMS Google announced the option to use quantum safe digital signatures for its cloud key management system. https://cloud.google.com/blog/products/identity-security/announcing-quantum-safe-digital-signatures-in-cloud-kms Windows 11 Patch issues The February Patch Tuesday appears to have caused issues with a number of Windows 11 systems. In particular the usability of the file manager appears to be affected. https://www.windowslatest.com/2025/02/16/windows-11-kb5051987-breaks-file-explorer-install-fails-on-windows-11-24h2/ LTE/5G Vulnerabilities Researchers at the university of Florida have identified a large number of vulnerabilities in 5G and LTE networks. https://nathanielbennett.com/publications/ransacked.pdf

Zu den letzten Episoden gab es viel inhaltliches Feedback, auf das Christopher und Sylvester in Folge 19 gerne eingehen. Außerdem reden die beiden noch einmal über das Tor-Projekt, denn eine aktuelle und interessante Angriffswelle auf das System hat es gerade so nicht in die vergangene Folge geschafft. Anschließend schauen sich die Hosts einige in letzter Zeit bekannt gewordene Security-Fails an. Die sind teilweise wirklich erschreckend und fanden sich ausgerechnet in Produkten von IT-Sicherheitsfirmen. So mancher Hersteller muss sich offenbar nochmal die Basics hinter die Ohren schreiben. Um Zertifikate geht es natürlich auch wieder, denn was wäre das Internet, ohne Geknarze in seiner Public-Key-Infrastruktur? - [Frontal-Bericht](https://www.youtube.com/watch?v=7anmIIwg0gI) - [BCP-38](http://www.bcp38.info/index.php/Main_Page) - [Passwort-Hashing-Funktionen](https://www.heise.de/hintergrund/IT-Security-Wie-Schluesselableitungsfunktionen-funktionieren-und-was-sie-leisten-9241241.html) - [Géant vs. Sectigo](https://doku.tid.dfn.de/de:dfnpki:tcsfaq:aktuellesituation) Mitglieder unserer Security Community auf heise security PRO hören alle Folgen bereits zwei Tage früher. Mehr Infos: https://pro.heise.de/passwort

Brendan Schaub reveals talking it out with SteveWillDoIt after Steve made some negative Twitter/X posts about him, Bryan discusses why he's really starting to like MMA reporter Luke Thomas, and the guys talk current events around the world including Reggie Bush getting back his Hesiman Trophy, Kanye's new venture and much more! True Classic - Upgrade your wardrobe and get up to 25% OFF @trueclassic at https://trueclassic.com/FIGHTER ! #trueclassicpod #sponsored JOYMODE - https://usejoymode.com/fighter or enter code: Fighter at checkout for 20% off your first order Sportsmans's Cove Lodge - http://alaskasbestlodge.com/ Use code “TFATK” at checkout for 10% off your first trip! Fieldcraft Survival - https://fieldcraftsurvival.com/fighter Use code: Fighter20 for 20% OFF Training and Product Happy Hippo - https://happyhippo.com/pages/brendan-schaub Promo Code: Thiccc24 for 20% OFF for LIFE!

1986, Mexico City, Nairobi, Phnom Penh, Frankfurt, DC area Hashes, --- Send in a voice message: https://podcasters.spotify.com/pod/show/ononh3/message Support this podcast: https://podcasters.spotify.com/pod/show/ononh3/support

This Week: The Chiefs! Drastic temperatures and snow in the South East. Strep throat. Dust mites. Shoe spikes. Justin takes up tap dancing. Hash is fucking dog food. Farmer's Dog. Why is rent so much? Why are mortgages so much? T. Swift is not “unlucky”. Tearful fans. Digging Up the Past in Paris. The black-eyed pea capital of the world. That piece of magic bread under hot chicken. "If it's dirty, it's good". Done with pancakes.  Recorded January 21st, 2024 We would be honored by your support and, sweet Jesus, it would help Justin sleep at night: https://anchor.fm/sushi-jackknife/support Nathan and Justin's Music: https://judystruckstop.bandcamp.com/ As Always:  Twitter: @SushiJackknife @badlandsbadley @Bob_ThangPod Email: sushijackknife@gmail.com instagram: justindrakecroft, siddandthefinches --- Support this podcast: https://podcasters.spotify.com/pod/show/sushi-jackknife/support

Robert De Niro and his ex-assistant Graham Robinson have “fully and finally resolved” their nasty court battle — and the legendary actor will NOT appeal the recent court decision entered against him.Advertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

Last week's news about evidence of LastPass vault decryption targeting cryptocurrency keys, and the UK's backing down on its encryption monitoring legislation. How hardware security modules (HSMs) allow cryptographic operations like code signing without exposing private keys. Browser identity segregation using multiple profiles rather than separate browsers. Requirements and best practices for securely wiping data from modern solid state drives. A countdown clock for the 32-bit UNIX time rollover in the year 2038. Steve's plan to move off Twitter and onto email lists for Security Now communication. A deep dive into cryptographic hash collisions, using fewer hash bits, and balancing anonymity with statistical meaning. Show Notes - https://www.grc.com/sn/SN-940-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6.

Last week's news about evidence of LastPass vault decryption targeting cryptocurrency keys, and the UK's backing down on its encryption monitoring legislation. How hardware security modules (HSMs) allow cryptographic operations like code signing without exposing private keys. Browser identity segregation using multiple profiles rather than separate browsers. Requirements and best practices for securely wiping data from modern solid state drives. A countdown clock for the 32-bit UNIX time rollover in the year 2038. Steve's plan to move off Twitter and onto email lists for Security Now communication. A deep dive into cryptographic hash collisions, using fewer hash bits, and balancing anonymity with statistical meaning. Show Notes - https://www.grc.com/sn/SN-940-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6.

Last week's news about evidence of LastPass vault decryption targeting cryptocurrency keys, and the UK's backing down on its encryption monitoring legislation. How hardware security modules (HSMs) allow cryptographic operations like code signing without exposing private keys. Browser identity segregation using multiple profiles rather than separate browsers. Requirements and best practices for securely wiping data from modern solid state drives. A countdown clock for the 32-bit UNIX time rollover in the year 2038. Steve's plan to move off Twitter and onto email lists for Security Now communication. A deep dive into cryptographic hash collisions, using fewer hash bits, and balancing anonymity with statistical meaning. Show Notes - https://www.grc.com/sn/SN-940-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6.

Last week's news about evidence of LastPass vault decryption targeting cryptocurrency keys, and the UK's backing down on its encryption monitoring legislation. How hardware security modules (HSMs) allow cryptographic operations like code signing without exposing private keys. Browser identity segregation using multiple profiles rather than separate browsers. Requirements and best practices for securely wiping data from modern solid state drives. A countdown clock for the 32-bit UNIX time rollover in the year 2038. Steve's plan to move off Twitter and onto email lists for Security Now communication. A deep dive into cryptographic hash collisions, using fewer hash bits, and balancing anonymity with statistical meaning. Show Notes - https://www.grc.com/sn/SN-940-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6.

Last week's news about evidence of LastPass vault decryption targeting cryptocurrency keys, and the UK's backing down on its encryption monitoring legislation. How hardware security modules (HSMs) allow cryptographic operations like code signing without exposing private keys. Browser identity segregation using multiple profiles rather than separate browsers. Requirements and best practices for securely wiping data from modern solid state drives. A countdown clock for the 32-bit UNIX time rollover in the year 2038. Steve's plan to move off Twitter and onto email lists for Security Now communication. A deep dive into cryptographic hash collisions, using fewer hash bits, and balancing anonymity with statistical meaning. Show Notes - https://www.grc.com/sn/SN-940-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6. Sponsors: bitwarden.com/twit joindeleteme.com/twit promo code TWIT drata.com/twit

Last week's news about evidence of LastPass vault decryption targeting cryptocurrency keys, and the UK's backing down on its encryption monitoring legislation. How hardware security modules (HSMs) allow cryptographic operations like code signing without exposing private keys. Browser identity segregation using multiple profiles rather than separate browsers. Requirements and best practices for securely wiping data from modern solid state drives. A countdown clock for the 32-bit UNIX time rollover in the year 2038. Steve's plan to move off Twitter and onto email lists for Security Now communication. A deep dive into cryptographic hash collisions, using fewer hash bits, and balancing anonymity with statistical meaning. Show Notes - https://www.grc.com/sn/SN-940-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6.

Last week's news about evidence of LastPass vault decryption targeting cryptocurrency keys, and the UK's backing down on its encryption monitoring legislation. How hardware security modules (HSMs) allow cryptographic operations like code signing without exposing private keys. Browser identity segregation using multiple profiles rather than separate browsers. Requirements and best practices for securely wiping data from modern solid state drives. A countdown clock for the 32-bit UNIX time rollover in the year 2038. Steve's plan to move off Twitter and onto email lists for Security Now communication. A deep dive into cryptographic hash collisions, using fewer hash bits, and balancing anonymity with statistical meaning. Show Notes - https://www.grc.com/sn/SN-940-Notes.pdf Hosts: Steve Gibson and Leo Laporte Download or subscribe to this show at https://twit.tv/shows/security-now. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit You can submit a question to Security Now at the GRC Feedback Page. For 16kbps versions, transcripts, and notes (including fixes), visit Steve's site: grc.com, also the home of the best disk maintenance and recovery utility ever written Spinrite 6.

In order to truly understand why Bitcoin works, we must understand a fundamental tool that operates at basically every level of the system. The hash function. And using the hash function, we can build one of the most important elements of the game theory that keeps the system honest, Proof of work. This is the second episode of the Bitcoin Basics series: Hashes & Proofs of Work To play around yourself with the hashing tools discussed you can: - open a Terminal window on your Mac or Linux computer and type...  shasum -a 256 [insert file] Replacing [insert file] with the file path of whatever you wish to hash (you can usually drag and drop) - On Windows open the "command prompt" and type... Get-FileHash -Path [insert file] To verify my Proof of Work done in the episode: echo -n "H18" | shasum -a 256 (this works on Mac & Linux, but unfortunately the process on Windows was too complicated to go through the trouble of confirming it) Don't forget to check out our amazing sponsors: • Dive into the Bitcoin only wallet, the cypherpunk calculator, and a company that has built secure Bitcoin products for nearly a decade. Code BITCOINAUDIBLE gets 9% off everything in your cart! (https://guyswann.com/coldcard) • Gets sats back every time you dump fiat at a store, to pay your bills, everything in your fiat life pays you sats with the Fold Debit Card and FoldApp. 20,000 FREE SATS! at (https://guyswann.com/fold) • The best place to onboard a true Bitcoiner - Stack sats automatically, withdraw automatically, and learn or get help from the best team of Bitcoiners out there with Swan Bitcoin. (https://swanbitcoin.com/guy) -------------------------------------- "You never change things by fighting the existing reality. To change something, build a new model, that makes teh existing model obsolete." – R. Buckminster Fuller Learn more about your ad choices. Visit megaphone.fm/adchoices

In Hour 4, Tobin lashes out on Lebron for 10 straight minutes while Leroy attempts to box in this Semantic Samurai. We close the show out with a interview of the former Boxing Promoter of the year, newly inducted Florida Boxing Hall of Famer and friend of the show Peter Khan joins us with Hialeah Gardens' very own Alien King Aaron Aponte. 

Roberto Di Cosmo, Computer Science professor at University Paris Diderot and founder of the Software Heritage initiative, discusses how to protect against sudden loss from the collapse of a "free" source code repository provider, how to protect...