680: Go Hack Yourself

1
00:00:11,488 --> 00:00:16,033
Hello, friends, and welcome back to your weekly Linux doc show. My name is Chris.
2
00:00:16,033 --> 00:00:16,945
My name is Wes.
3
00:00:17,345 --> 00:00:18,303
And my name is Brent.
4
00:00:18,303 --> 00:00:21,933
Hello, gentlemen. Coming up on the show, we'll break down the openness of HFly
5
00:00:21,933 --> 00:00:23,713
you probably need to know about.
6
00:00:23,934 --> 00:00:27,493
And then we're going to attack our own systems. In the spirit of finding issues
7
00:00:27,493 --> 00:00:32,369
before the bad guys do, we're going to go over how to red team your own network for fun and security.
8
00:00:32,653 --> 00:00:34,830
Then we're going to round out with some great booths, some picks,
9
00:00:35,602 --> 00:00:38,493
and a lot more. So before we get to all of that, let's say time-appropriate
10
00:00:38,493 --> 00:00:41,005
greetings to our mobile room. Hello, VirtualLug. Hey, guys.
11
00:00:43,473 --> 00:00:44,338
Hello, gang.
12
00:00:44,639 --> 00:00:48,189
Look at those guys. Hello, everybody. And hello up there in the quiet listening.
13
00:00:48,189 --> 00:00:49,951
Hello to the live Matrix Room. Yeah, we're live.
14
00:00:50,822 --> 00:00:55,019
We make it a Tuesday on a Sunday over at jblive.tv, and you can get it at jupiterbroadcasting.com
15
00:00:55,019 --> 00:00:56,365
slash calendar in your time zone.
16
00:00:57,689 --> 00:00:58,483
My time zone?
17
00:00:58,750 --> 00:00:59,629
Well, any time zone.
18
00:00:59,629 --> 00:01:01,966
We never know what time zone you're in. That's why we have the system.
19
00:01:02,581 --> 00:01:06,479
If we deployed the calendar today, we'd probably say it's using AI to automatically
20
00:01:06,479 --> 00:01:07,527
determine your location.
21
00:01:08,409 --> 00:01:10,818
It is, in fact, not. It may be using JavaScript.
22
00:01:10,946 --> 00:01:13,199
It's, I guess, whatever Google Calendars do it.
23
00:01:14,040 --> 00:01:17,558
I also want to say good morning to our friends over at Define Networking.
24
00:01:18,115 --> 00:01:21,869
Go check out Define.net slash unplugged and meet Managed Nebula from Define
25
00:01:21,869 --> 00:01:26,132
Networking. It's built on the open source Nebula platform. We love it. We use it. It's great.
26
00:01:26,834 --> 00:01:30,349
Nebula gives you fast encrypted peer-to-peer networking without routing everything
27
00:01:30,349 --> 00:01:31,641
through somebody else's cloud.
28
00:01:32,546 --> 00:01:37,819
And it's ready for modern networks. IPv6 is built in with IPv4 or dual stack
29
00:01:37,819 --> 00:01:43,088
support when you need it. And the technical implementation should be studied.
30
00:01:43,291 --> 00:01:45,027
I'm telling you, it's great.
31
00:01:45,288 --> 00:01:48,569
And you can run your own lighthouses, so that way you can define your network.
32
00:01:48,569 --> 00:01:51,186
You have control of the core of your network.
33
00:01:51,471 --> 00:01:53,880
And, of course, they'll now provision one for you as well as part of Manage
34
00:01:54,240 --> 00:01:55,551
Nebula, and you could use Bolt.
35
00:01:56,636 --> 00:02:00,792
It's huge. It was originally built for Slack, for serious scale, serious privacy.
36
00:02:01,222 --> 00:02:06,086
And today you can connect up to 100 hosts for free, no credit card required.
37
00:02:06,464 --> 00:02:08,501
You just go to define.net slash unplug.
38
00:02:08,937 --> 00:02:14,129
Nothing else offers Nebula's level of resilience, speed, and scalability.
39
00:02:14,129 --> 00:02:16,919
I am telling you, you're going to be impressed. Get started 100 hosts,
40
00:02:16,919 --> 00:02:18,788
absolutely free, no credit card required.
41
00:02:19,682 --> 00:02:23,859
Defined.net slash unplugged. Big thank you to Defined for sponsoring the Unplugged
42
00:02:23,859 --> 00:02:28,159
program. And go redefine your VPN experience. Control your network destiny at
43
00:02:28,159 --> 00:02:30,374
Defined.net slash unplugged.
44
00:02:32,604 --> 00:02:36,662
We now have the schedule for Texas Linux Fest 2026.
45
00:02:36,865 --> 00:02:40,720
Yeah, you can go check it out if you're curious what talks are on offer.
46
00:02:41,178 --> 00:02:44,500
For a quick reminder here, it will be at the UT Commons Event Center,
47
00:02:44,500 --> 00:02:48,600
same place as last year, November 6th through the 7th, 2026.
48
00:02:48,600 --> 00:02:52,900
Yeah, not October, November 6th through the 7th. And there is early bird pricing
49
00:02:52,900 --> 00:02:57,918
right now. You do need to buy tickets. That ends soon, very soon.
50
00:02:58,434 --> 00:03:01,830
So go grab your tickets now and support Texas Linux Fest.
51
00:03:02,347 --> 00:03:05,170
and we'll have a link to the full schedule. We are still putting together our
52
00:03:05,170 --> 00:03:09,156
plan. We really, really do want to go. We feel like there's a few of these events.
53
00:03:09,772 --> 00:03:13,644
Really, there's no other industry that does an event like Texas Linux Fest.
54
00:03:14,131 --> 00:03:18,485
The Linux community is unique in this where it's community-run, community-organized,
55
00:03:19,541 --> 00:03:22,677
And it's so more like refreshing and recharging.
56
00:03:22,677 --> 00:03:26,087
It's such a great time. It's so welcoming. It's so earnest and open.
57
00:03:26,087 --> 00:03:30,327
Well, how do you describe the difference between this and like a commercial vendor?
58
00:03:30,327 --> 00:03:31,097
Night and day.
59
00:03:31,097 --> 00:03:32,617
Night and day, right?
60
00:03:32,617 --> 00:03:36,550
Like going to see family instead of like some kind of scale work function.
61
00:03:36,869 --> 00:03:42,967
I could do five. I could do five Texas Linux events to one like Red Hat Summit. You know what I mean?
62
00:03:44,335 --> 00:03:47,437
It really is a recharger. And so even if you're not a podcaster,
63
00:03:47,437 --> 00:03:51,227
if you're not in the JB community directly, but you're just kind of in the industry
64
00:03:51,227 --> 00:03:54,835
or kind of in the Linux space, I think you'll really, really enjoy it if you can make it.
65
00:03:55,450 --> 00:04:00,067
Well, speaking of beloved Linux conferences, we do have some news on scale as well.
66
00:04:01,427 --> 00:04:04,867
24x will be taking place next year, but the dates are different.
67
00:04:04,867 --> 00:04:06,807
Before it's been like early March.
68
00:04:06,807 --> 00:04:07,157
Yeah.
69
00:04:07,157 --> 00:04:09,867
Now it's going to be early April. April 1st through the 4th,
70
00:04:09,867 --> 00:04:12,327
2027 at the Pasadena Convention Center.
71
00:04:12,327 --> 00:04:16,407
April could be really busy. Yeah. Yep, at the Pasadena Convention Center.
72
00:04:17,387 --> 00:04:19,577
And they do have their call for presentations going now.
73
00:04:19,577 --> 00:04:24,202
Yeah, open now. So closes November 1st. You've got a little while, but don't sleep on it.
74
00:04:24,771 --> 00:04:27,348
And then last but not least, really, Nix Vegas.
75
00:04:27,685 --> 00:04:32,287
Yeah, so Nix Vegas and DEFCON 34 just wrapped up. I was lucky enough to go last
76
00:04:32,287 --> 00:04:33,356
year, had a wonderful time.
77
00:04:33,600 --> 00:04:37,207
And they did it again this year. Another fantastic looking badge and a great
78
00:04:37,207 --> 00:04:40,577
set of talks. And it seems like an even more impressive setup because they've
79
00:04:40,577 --> 00:04:43,977
already got those talks turned around and up on YouTube. So if you want to go
80
00:04:43,977 --> 00:04:45,268
check them out, please do.
81
00:04:45,570 --> 00:04:46,499
Links in the notes.
82
00:04:48,873 --> 00:04:54,888
All right, so OpenSSH 10.5 has come out, and it's A, an important update that
83
00:04:54,888 --> 00:05:01,450
you probably need to install, but B, I think it sort of shows us the shape of things to come.
84
00:05:01,601 --> 00:05:06,038
It is perhaps an example of what's probably going to be more and more common.
85
00:05:06,038 --> 00:05:09,408
So, Mr. Payne, as best you can, can you kind of tell us what's going on and
86
00:05:09,408 --> 00:05:10,998
why they had to release 10.5 this week?
87
00:05:10,998 --> 00:05:15,698
Yeah, the big bit here is around SSH agent forwarding, which maybe you've done,
88
00:05:15,698 --> 00:05:19,158
right, where you have like an SSH agent to handle how you handle your keys.
89
00:05:19,158 --> 00:05:22,688
Maybe you got a fancy YubiKey or something or you just got a key with a password
90
00:05:22,688 --> 00:05:23,597
and all of that kind of going.
91
00:05:24,178 --> 00:05:27,368
But you want to be able to use that throughout a network, right?
92
00:05:27,368 --> 00:05:30,058
So like you're going to one box and then you want to be able to still use your
93
00:05:30,058 --> 00:05:33,558
agent to be able to answer cryptographic questions further down the chain.
94
00:05:33,998 --> 00:05:38,145
So that's where SSH agent forwarding comes in. Well, there was an interaction
95
00:05:38,394 --> 00:05:43,068
between agent locking and OpenSSH's session binding that could allow certain
96
00:05:43,068 --> 00:05:48,428
operations that were supposed to stay local happen remotely through a forwarded agent.
97
00:05:48,428 --> 00:05:48,814
Uh-oh.
98
00:05:48,994 --> 00:05:56,017
Yeah, this included adding PKCS11 tokens and in some cases using destination-restricted keys.
99
00:05:56,951 --> 00:06:01,970
The SSH client also, the update for it also fixes a potential use after free bug.
100
00:06:01,970 --> 00:06:07,110
And on the server side, they've fixed the restrict option in authorized keys.
101
00:06:07,110 --> 00:06:12,885
So it now properly applies to tunnel forwarding too. So more work in the tunnel area.
102
00:06:13,419 --> 00:06:16,124
Worth noting though, tunnel forwarding is still disabled by default.
103
00:06:16,490 --> 00:06:18,890
So it only applies if you've actually explicitly turned it on.
104
00:06:18,890 --> 00:06:20,230
Though plenty of people do.
105
00:06:20,230 --> 00:06:22,289
Yeah, yeah. Guilty.
106
00:06:22,411 --> 00:06:27,010
And then, furthermore, OpenSSH says it's seen, surprise, surprise,
107
00:06:27,010 --> 00:06:31,734
not really, they're seeing a surge in AI-assisted vulnerability reports.
108
00:06:32,077 --> 00:06:35,410
Now, of course, a lot of them don't really hold up under realistic threat models.
109
00:06:35,410 --> 00:06:36,721
You kind of fill out the details.
110
00:06:37,600 --> 00:06:41,730
But they do explicitly say findings backed by human analysis,
111
00:06:41,730 --> 00:06:44,296
test cases, and fixes are welcome.
112
00:06:44,952 --> 00:06:48,050
And perhaps more interestingly, they've seen vulnerabilities first found with
113
00:06:48,050 --> 00:06:51,718
AI, later independently discovered by other researchers.
114
00:06:52,369 --> 00:06:56,580
So two notes to that, Wes. Number one is it's sort of this double-edged sword
115
00:06:56,580 --> 00:07:00,200
that we continue to see with AI contributions is,
116
00:07:01,035 --> 00:07:09,150
maybe you get 10 crappy slop reports and then you get one or two genuinely important security reports.
117
00:07:09,150 --> 00:07:13,710
And they still have to go through those 10 or 11 slop reports to get that one genuine.
118
00:07:13,710 --> 00:07:17,590
And figuring out how to do that well and at scale is now a new open problem.
119
00:07:17,590 --> 00:07:25,780
But also, it seems likely that the genuinely good reports will increase as things
120
00:07:25,780 --> 00:07:29,630
like KimiK3 and DeepSeek4 become more prevalent in the community.
121
00:07:29,630 --> 00:07:33,570
Yeah, the signals and noise should get better as model capability and our techniques get better.
122
00:07:33,570 --> 00:07:33,880
Yeah.
123
00:07:33,880 --> 00:07:34,774
You would hope.
124
00:07:34,942 --> 00:07:39,230
Yeah, yeah. So there, but that doesn't mean they see less submissions, right?
125
00:07:39,230 --> 00:07:43,150
So they're going to have this – and OpenSSH is one of many that are going to
126
00:07:43,150 --> 00:07:48,130
have this accelerated issue of if one LLM with one guy can find it,
127
00:07:48,130 --> 00:07:50,580
then another gal with another LLM is going to find it. And it's almost –,
128
00:07:51,572 --> 00:07:55,667
It could almost be an assumed that if an LLM found that bug,
129
00:07:55,667 --> 00:07:58,985
it's almost public at that point. So there's sort of an urgency in which they have to move.
130
00:07:59,148 --> 00:08:02,067
Yeah, and especially because we've seen like with Bitcoin projects,
131
00:08:02,067 --> 00:08:06,127
I think OpenSSH is another one, right, where it's independently maintained,
132
00:08:06,127 --> 00:08:11,547
not a huge team, and is like a high leverage tool where if you can own that,
133
00:08:11,547 --> 00:08:13,266
then you can really get everywhere.
134
00:08:14,357 --> 00:08:17,627
They do also say that as, you know, and I wonder if we'll see this more because
135
00:08:17,627 --> 00:08:20,797
it's kind of a stress test of the whole like software delivery pipeline.
136
00:08:21,177 --> 00:08:24,597
They are talking about doing release fixes, releasing fixes more frequently.
137
00:08:24,597 --> 00:08:27,137
Yeah, faster release cadence because of this problem.
138
00:08:27,197 --> 00:08:28,231
Which is probably a good idea.
139
00:08:29,525 --> 00:08:34,357
Maybe. I mean, it doesn't mean that the rail boxes and Ubuntu LTS boxes up there
140
00:08:34,357 --> 00:08:35,795
are going to get updated any sooner. No.
141
00:08:36,265 --> 00:08:39,417
But hopefully it means we do have to polish that and pay us more attention.
142
00:08:39,417 --> 00:08:42,827
It's a good excuse to invest in securing that entire pipeline.
143
00:08:42,827 --> 00:08:45,327
And I mean, you're right. It doesn't mean anyone actually does the updates,
144
00:08:45,327 --> 00:08:46,457
but at least maybe they're there.
145
00:08:46,457 --> 00:08:49,923
Maybe it forces people to adopt a system that can update more frequently.
146
00:08:50,707 --> 00:08:54,017
I would imagine this updated release cadence, though, puts a lot of pressure
147
00:08:54,017 --> 00:09:00,018
on these projects to push forward in a pace they haven't previously seen.
148
00:09:00,169 --> 00:09:04,906
And so is that sustainable long term? I sure hope so, because we need it more than ever.
149
00:09:05,138 --> 00:09:06,490
I think that's an open question, too.
150
00:09:07,309 --> 00:09:11,197
Yeah. And could there be more security mistakes that slip in if you're going
151
00:09:11,197 --> 00:09:13,317
faster? There's always that concern as well.
152
00:09:13,985 --> 00:09:18,170
And it's, I think, isn't just an open SSH story, like we've said.
153
00:09:18,640 --> 00:09:22,337
We're really discovering bugs that have sat quietly for years getting discovered
154
00:09:22,337 --> 00:09:27,731
now because a machine that just has unlimited patience can go through and find these things.
155
00:09:29,119 --> 00:09:32,509
So we're going to see, I think, more projects with more frequent security releases.
156
00:09:33,013 --> 00:09:35,692
They're going to have to have some sort of continuous scanning themselves and
157
00:09:35,692 --> 00:09:37,229
some sort of assisted triage.
158
00:09:38,129 --> 00:09:42,724
And you may see some of these projects. Would you be surprised,
159
00:09:43,259 --> 00:09:48,494
to find like an maybe not OpenSSH, but a project like OpenSSH have a daily branch
160
00:09:48,796 --> 00:09:53,161
that a company like maybe Red Hat and Canonical and others are ingesting?
161
00:09:53,598 --> 00:09:56,502
they're running their own checks against it and they're shipping those patches
162
00:09:56,502 --> 00:09:59,924
as fast as possible to their customers after they've done a pass for quality checks.
163
00:10:00,673 --> 00:10:05,412
You could see like these LTS distros getting a faster stream of software to
164
00:10:05,412 --> 00:10:06,438
resolve some of this stuff.
165
00:10:07,320 --> 00:10:11,542
So I think it doesn't look like an isolated incident. And it reminds me of a
166
00:10:11,542 --> 00:10:16,892
talk just a couple of weeks ago that OpenAI gave at Black Hat 2026.
167
00:10:16,892 --> 00:10:22,422
And this was just a few days after it became public that OpenAI's testing models
168
00:10:22,422 --> 00:10:26,302
had breached hugging faces systems and it's a good talk willing to the whole
169
00:10:26,302 --> 00:10:28,538
talk. I thought it was surprisingly candid.
170
00:10:28,734 --> 00:10:29,622
Yeah. Refreshing.
171
00:10:29,622 --> 00:10:34,642
Uh, very technical and, um, some stuff I think is new.
172
00:10:34,642 --> 00:10:37,482
Some stuff in here is novel and there's a bit in here.
173
00:10:37,482 --> 00:10:42,082
That's one of their takeaways is that as these models advance and as agents
174
00:10:42,082 --> 00:10:45,875
begin to work together, which is something that led to this breach,
175
00:10:46,550 --> 00:10:50,122
uh, you're going to have to have a different speed in which you respond to,
176
00:13:29,213 --> 00:13:33,121
Wes made an implication of this earlier, but this has been really pronounced
177
00:13:33,121 --> 00:13:36,381
over in the Bitcoin community recently as that's sort of been the front line
178
00:13:36,381 --> 00:13:39,851
because you compromise a Bitcoin wallet, you can steal somebody's funds,
179
00:13:39,851 --> 00:13:41,251
you immediately get the reward.
180
00:13:41,251 --> 00:13:46,741
And so it's been going through the Bitcoin community almost like locusts,
181
00:13:46,741 --> 00:13:50,281
just going from one project after the other, stealing funds and whatnot as they
182
00:13:50,281 --> 00:13:52,659
use these tools, mostly via Kimmy K3,
183
00:13:53,628 --> 00:13:58,272
to find weaknesses in projects like by scanning GitHub repos and exploiting those.
184
00:13:58,736 --> 00:14:01,561
Yeah. The other thing that kind of stuck out with some of these recent quote
185
00:14:01,561 --> 00:14:04,646
unquote escapes or just the various stories we've been talking about is just,
186
00:14:05,279 --> 00:14:10,101
that it's not really like suddenly all security principles are thrown out the window.
187
00:14:10,101 --> 00:14:14,491
If anything, it means things like defense in depth and like knowing where you're,
188
00:14:14,491 --> 00:14:16,821
you know, what your threat vectors are and like what you're actually trying
189
00:14:16,821 --> 00:14:20,051
to protect and why and having a good understanding of what's going on with your
190
00:14:20,051 --> 00:14:21,821
systems is more important than ever.
191
00:14:21,821 --> 00:14:24,435
I mean, there is a component of being able to find more zero days,
192
00:14:24,830 --> 00:14:30,321
but a lot of this is also the orchestration side, being able to go from doing
193
00:14:30,321 --> 00:14:34,781
a scan to actually executing through to getting a persistent vector or getting
194
00:14:34,781 --> 00:14:35,741
through the network or whatever.
195
00:14:35,741 --> 00:14:39,541
Yeah, like in the case of the OpenAI exploit, they took advantage of a package
196
00:14:39,541 --> 00:14:42,491
manager that was connected to the internet that had exploits,
197
00:14:42,491 --> 00:14:47,121
and then they took advantage of a web dev share that was available to do agent coordination.
198
00:14:47,441 --> 00:14:51,114
So they didn't create those exploits. They took advantage of those things,
199
00:14:51,572 --> 00:14:52,971
which they can be very good at.
200
00:14:53,267 --> 00:14:56,901
You're right. So if they had proper isolation and proper security on the OpenAI
201
00:14:56,901 --> 00:14:58,683
network, these things would have never gotten out.
202
00:14:58,794 --> 00:15:01,341
Yeah, there's just ways you could design it if you're really trying to do this
203
00:15:01,341 --> 00:15:05,621
in a hardened way from the get-go, though that would surely slow you down.
204
00:15:05,621 --> 00:15:08,921
Of course, I guess the silver lining or maybe the steel man,
205
00:15:08,921 --> 00:15:12,211
it would be as the models get more advanced, they have to come up with new and
206
00:15:12,211 --> 00:15:14,653
more sophisticated ways to isolate them, perhaps.
207
00:15:15,140 --> 00:15:17,480
But when you look into the root cause, it is.
208
00:15:18,698 --> 00:15:19,528
There was mistakes made.
209
00:15:19,632 --> 00:15:23,286
And, you know, it's not like necessarily there's, we will see different zero
210
00:15:23,286 --> 00:15:25,066
day rates across different projects.
211
00:15:25,106 --> 00:15:30,046
And there's been, you know, and a big part of this is sort of an economic thing
212
00:15:30,046 --> 00:15:32,026
of there's one part of like, what is the frontier?
213
00:15:32,166 --> 00:15:35,976
What is the, you know, you can pop novel software quickly sort of aspect.
214
00:15:35,976 --> 00:15:40,026
But then just the other side is you just now have this market to be able to
215
00:15:40,446 --> 00:15:43,013
buy the automation on demand for the rest of it.
216
00:15:43,228 --> 00:15:47,436
yeah and i think that just sort of changes what which low-hanging fruit now
217
00:15:47,436 --> 00:15:49,166
becomes economic to actually attack.
218
00:15:49,166 --> 00:15:54,156
Yeah now it's can you afford the credits the token credits and uh can you you
219
00:15:54,156 --> 00:15:56,066
know are you creative of what project you pointed out etc.
220
00:15:56,546 --> 00:15:59,816
Yeah and that's where i think there's also then on the defensive side as we
221
00:15:59,816 --> 00:16:01,119
kind of heard a little bit there is,
222
00:16:01,648 --> 00:16:03,522
like we're going to talk a little bit about maybe what you can do with your
223
00:16:03,661 --> 00:16:06,446
your home lab or things like that but we also need to figure out how we can
224
00:16:06,446 --> 00:16:11,606
invest at scale for the free and open source communities because projects are
225
00:16:11,606 --> 00:16:13,455
going to need resources on the defensive side.
226
00:16:13,750 --> 00:16:17,216
Yeah, so I figured it was worth time figuring out how we could,
227
00:16:17,216 --> 00:16:22,026
as they say, red team ourselves to try to figure out where we have low-hanging fruit.
228
00:16:22,026 --> 00:16:25,906
Because my suspicion is, and I don't like making this forecast,
229
00:16:25,906 --> 00:16:28,123
but I suspect likely that,
230
00:16:28,576 --> 00:16:32,456
a lot of the free software we rely on for infrastructure is going to get poked
231
00:16:32,456 --> 00:16:37,497
at pretty soon because that's the same infrastructure banks rely on, e-commerce relies on.
232
00:16:37,793 --> 00:16:40,636
A lot of money rides on top of the Linux stack.
233
00:16:40,636 --> 00:16:43,736
It's embedded in the industry in innumerable places.
234
00:16:43,736 --> 00:16:46,716
Yeah, and then there's monitoring and spying. If you pop, there's all kinds
235
00:16:46,716 --> 00:16:49,455
of advantages to popping the stuff that we rely on every single day.
236
00:16:50,175 --> 00:16:54,262
So I'm sort of operating under the assumption that once they get done having
237
00:16:54,262 --> 00:16:57,321
their fun with the Bitcoiners, they're kind of coming for the rest of us.
238
00:16:57,669 --> 00:17:00,402
And you're starting to see it a little bit with OpenSSH. That makes sense.
239
00:17:00,402 --> 00:17:01,559
That'd be another low-hanging fruit.
240
00:17:01,971 --> 00:17:05,262
The other one that could be fun if you want to do a little homework is Apple
241
00:17:05,262 --> 00:17:09,782
released a patch for remote desktop. And now, you know, the AI-assisted reverse
242
00:17:09,782 --> 00:17:12,432
engineering made it possible for them to go out and chase every single Mac that
243
00:17:12,432 --> 00:17:15,096
hasn't been patched now. And so now there's a cat and mouse game playing out.
244
00:17:15,456 --> 00:17:17,424
That's happening right now as we record this episode.
245
00:17:17,935 --> 00:17:21,792
So how do you protect yourself? It seems like it's clanker versus clanker.
246
00:17:21,792 --> 00:17:25,972
It's like some sort of horrible sci-fi novel where you need to have a defensive
247
00:17:25,972 --> 00:17:27,896
clanker that's checking your own systems.
248
00:17:28,237 --> 00:17:35,523
And so I built a red team agent that has been hacking our infrastructure literally all week long.
249
00:17:44,277 --> 00:17:49,462
Chris, you alluded to attacking your own infrastructure, which I would imagine
250
00:17:49,462 --> 00:17:53,676
revealed a few things. But A, how and B, why?
251
00:17:55,353 --> 00:17:58,848
All right. You know, the why is just to try to catch stuff.
252
00:17:59,260 --> 00:18:03,329
Also, you know, just try to get a sense of what it needs to be retired first.
253
00:18:03,666 --> 00:18:07,712
Last week, we talked about retiring our node box. And so I figured before we
254
00:18:07,712 --> 00:18:12,592
take it offline, let's attack it and see how vulnerable and risky it really
255
00:18:12,592 --> 00:18:14,916
was to have that thing in production. So you can get a sense of that.
256
00:18:15,265 --> 00:18:17,892
It could be nice to run it against your VPSs. I want to stress that this is
257
00:18:17,892 --> 00:18:21,322
for really to audit your own stuff, to make sure you're safe.
258
00:18:21,322 --> 00:18:23,026
And that's really the intention of all of this.
259
00:18:23,322 --> 00:18:26,592
And also to kind of get a sense of what kind of automation was out there in
260
00:18:26,592 --> 00:18:32,002
terms of, you know, like we can run Nmap or a couple commands ourselves,
261
00:18:32,002 --> 00:18:34,312
but like, can we take it to the next level?
262
00:18:34,312 --> 00:18:37,952
You could totally just, you could do a lot of this with some port scanning and
263
00:18:37,952 --> 00:18:41,542
identifying the versions of stuff and then going looking up that version with
264
00:18:41,542 --> 00:18:43,963
CVEs it has. I was like, you could do this manually.
265
00:18:44,515 --> 00:18:50,360
I wanted to be able to go to my agent data and say, data, attack this system and give me a full audit.
266
00:18:50,540 --> 00:18:54,852
And what it would do is it would initiate some of those basics,
267
00:18:54,852 --> 00:18:56,839
like an NMAP and a ping and all that kind of stuff.
268
00:18:57,344 --> 00:19:01,772
Identify what services are open and what versions of them. And then based on
269
00:19:01,772 --> 00:19:04,536
that, look up the CVEs and then proceed to try to exploit them.
270
00:19:04,948 --> 00:19:06,846
And then if it gets that far, give me a report.
271
00:19:07,386 --> 00:19:11,107
And so to accomplish that, I'm using a project. There's a lot of them out there.
272
00:19:12,210 --> 00:19:13,209
Don't do as I do.
273
00:19:15,461 --> 00:19:20,409
I'm using a project called Hextrike AI. And it's essentially a collection of
274
00:19:20,409 --> 00:19:25,849
MCPs with behind it 150 different security tools and a bunch of different autonomous
275
00:19:25,849 --> 00:19:28,864
AI subagents that can do these tasks.
276
00:19:29,699 --> 00:19:35,429
And it's pretty conventional in the execution order, but actually pretty great
277
00:19:35,429 --> 00:19:41,559
in the document, discovery, discovery, documentation, authorization for more advanced attacks.
278
00:19:42,739 --> 00:19:50,269
So Hextrike is both a very powerful tool but can also be a foot gun because
279
00:19:50,269 --> 00:19:54,806
of the types of tools it's using. They're moving so fast, the tools themselves often have exploits.
280
00:19:55,712 --> 00:19:59,379
So you have to build this in a way where it's extremely isolated because there
281
00:19:59,379 --> 00:20:03,107
is conceivably a possibility where these types of tools can be turned back around on yourself.
282
00:20:03,879 --> 00:20:09,586
So I spent quite a bit of time designing this in a way where it was completely offline and isolated.
283
00:20:09,754 --> 00:20:13,269
individual components would be spun up on demand continue to be isolated,
284
00:20:13,269 --> 00:20:18,209
operated with wrappers and the MCPs and so underneath it there's a really really
285
00:20:18,209 --> 00:20:21,840
good set of tools, one of them is called Nuclei, N-U-C-L-E-I,
286
00:20:23,161 --> 00:20:26,408
which does a lot of the CVE heavy lifting, SQL map.
287
00:20:26,828 --> 00:20:30,488
Oh, Nuclei, yeah. Oh, yeah, thank you. Hydra's in there, Hashcat's in here,
288
00:20:30,988 --> 00:20:37,038
NetExec, various DNS tools, web exploits, framework exploits, binary analysis tools.
289
00:20:37,038 --> 00:20:37,912
Fuzzers.
290
00:20:38,126 --> 00:20:43,678
Yeah, there's a lot of really good stuff in here. And what I wanted is I wanted
291
00:20:43,678 --> 00:20:48,778
something that was essentially on demand for my agent, that I could have a system
292
00:20:48,778 --> 00:20:50,008
that then they would give me a report.
293
00:20:50,608 --> 00:20:54,189
It would be documented in a particular place every single time,
294
00:20:54,624 --> 00:20:56,354
and I would get a summary in Telegram.
295
00:20:56,807 --> 00:21:02,828
And so the idea was is I want to do an attack by prompt is kind of what I was
296
00:21:02,828 --> 00:21:04,968
going for. And I know you looked at this, Wes.
297
00:21:04,968 --> 00:21:08,438
Oh, yeah. I got a sort of – I'm curious to see how similar our setups were.
298
00:21:08,438 --> 00:21:14,038
Well, okay. So I went pretty wild. I will admit I blew way too much time on
299
00:21:14,038 --> 00:21:18,076
this. I literally started this project when I got home from the show last week.
300
00:21:18,581 --> 00:21:19,328
You can cook it.
301
00:21:19,328 --> 00:21:22,179
And I finished it this morning while we were doing the stream.
302
00:21:23,148 --> 00:21:24,648
Yeah, during the pre-show as far as I saw.
303
00:21:25,928 --> 00:21:28,438
But I went way over complicated because I wanted to isolate.
304
00:21:28,438 --> 00:21:30,086
I wanted to integrate it with my Hermes agent.
305
00:21:30,742 --> 00:21:31,658
Oh, yeah, that's nice.
306
00:21:31,658 --> 00:21:34,978
If you just ran it standalone with the MCP tools like through open code,
307
00:21:34,978 --> 00:21:36,758
I think it would be a much leaner, faster setup.
308
00:21:36,758 --> 00:21:38,008
Yeah, so that's what I basically did.
309
00:21:38,008 --> 00:21:38,658
Tell me about this.
310
00:21:38,658 --> 00:21:43,678
Yeah, I stood up Kali VM because Hextrike doesn't provide the tools.
311
00:21:43,678 --> 00:21:46,428
It just like runs them and orchestrates them and makes them available,
312
00:21:46,428 --> 00:21:47,744
services them to the agent.
313
00:21:48,209 --> 00:21:51,118
and I just figured like half of these are already in Cali and the rest are in
314
00:21:51,118 --> 00:21:54,108
easy repos or easy to run on Cali because it's all designed on that,
315
00:21:55,168 --> 00:22:00,348
so I got that spun up in just a quick QEMU VM and then have forwarded some ports
316
00:22:00,348 --> 00:22:05,989
there to wire up SSH access for the agent as well as the MCP server back and then,
317
00:22:06,669 --> 00:22:08,024
Yeah, kind of just kicked it off from there.
318
00:22:08,024 --> 00:22:12,816
I think VM is a really good approach. You know, that keeps it as isolated as you kind of can.
319
00:22:13,514 --> 00:22:16,171
Yeah, and then I chose to connect it up with a mesh network,
320
00:22:16,537 --> 00:22:19,764
a quick little nebula network, and then I could just kind of add some groups
321
00:22:19,764 --> 00:22:22,074
that I could add it into. And so I knew just like, okay, well,
322
00:22:22,074 --> 00:22:23,246
whatever I'm actually going to target.
323
00:22:23,386 --> 00:22:25,634
Like, obviously, you're not going to do the full, like, layer two,
324
00:22:25,634 --> 00:22:28,964
like, all the complicated, but for sort of scanning what services were running
325
00:22:28,964 --> 00:22:30,694
and that kind of thing, it was perfect.
326
00:22:30,694 --> 00:22:33,694
Right, for really, which is what a remote attacker is going to go after,
327
00:22:33,694 --> 00:22:38,264
right? Like my analysis going in is what is somebody who's not familiar with
328
00:22:38,264 --> 00:22:41,344
the LAN, somebody who's remote likely going to get maybe they've somehow got
329
00:22:41,344 --> 00:22:43,904
on the Wi-Fi or the LAN, but they're not really intricately familiar with it.
330
00:22:43,904 --> 00:22:45,554
So I think that accomplishes that.
331
00:22:45,554 --> 00:22:48,084
And then obviously in another situation, like if I was trying to scan like a
332
00:22:48,084 --> 00:22:51,074
public VPS of mine, then I would attack it through that interface or whatever.
333
00:22:51,074 --> 00:22:55,514
I like the, you know, Mesh Network Nebula, just put the host on there that you're scanning.
334
00:22:56,354 --> 00:22:59,804
A lot of this too was like I was learning how to use this tool, right?
335
00:22:59,804 --> 00:23:03,104
So it's like I didn't really want, I wasn't, I haven't got as far as like,
336
00:23:03,104 --> 00:23:06,634
this is like a trusted tool that I know well, right? So I kind of wanted to
337
00:23:06,634 --> 00:23:08,924
have some known good hosts I could attack and be like, okay,
338
00:23:08,924 --> 00:23:12,954
this is stuff that even if something goes wrong is fine and I have backups of and all the rest.
339
00:23:12,954 --> 00:23:15,884
So one of the nice things about Hextrike is because it is essentially,
340
00:23:15,884 --> 00:23:18,956
like Wes said, it's orchestrating established tools, but you can have...
341
00:23:19,611 --> 00:23:23,548
it is aware of like these are critical like financially important systems or
342
00:23:23,548 --> 00:23:26,461
production important systems and this is a box i can bang on.
343
00:23:26,704 --> 00:23:30,598
And it comes with it seems like a lot of prompts that it it provides with as
344
00:23:30,598 --> 00:23:33,698
you as you run through the tools and integrate with it that kind of shape that
345
00:23:33,698 --> 00:23:37,318
too so it's very the resulting system just out of the box is pretty careful
346
00:23:37,318 --> 00:23:40,548
around like i'm only going to do this with authorization and like you know are
347
00:23:40,548 --> 00:23:41,448
we checking the boxes and.
348
00:23:41,448 --> 00:23:43,638
One of the things i spent a lot of time was reducing ceremony.
349
00:23:43,638 --> 00:23:44,088
That was the.
350
00:23:44,088 --> 00:23:47,168
Term i had to keep using is like it wants you to sign with a key here wants
351
00:23:47,168 --> 00:23:49,618
you to open up a markdown document initially and put your name in there and
352
00:23:49,618 --> 00:23:54,478
a date like it is serious about authorizing stuff i'm like no no no no no i
353
00:23:54,478 --> 00:23:55,138
don't want to do any of that.
354
00:23:56,078 --> 00:23:59,488
So i did do like some some initial tests so like it was doing nmap it was doing
355
00:23:59,488 --> 00:24:03,158
some curls against stuff it was using a fuzzer to attack just sort of basic
356
00:24:03,158 --> 00:24:08,535
ports and web services it was using nuclei um yeah it did some ssfrf probes
357
00:24:08,866 --> 00:24:10,311
the it didn't find too much because.
358
00:24:10,428 --> 00:24:11,238
Everything's up to date.
359
00:24:11,238 --> 00:24:14,788
Right yeah it's like a nix os box yeah up to date but uh it did the thing that
360
00:24:14,788 --> 00:24:16,874
it would have found if it was a problem uh
361
00:24:17,278 --> 00:24:21,418
is it did immediately latch on that i have an llm gateway yeah there right and
362
00:24:21,418 --> 00:24:24,178
it was like uh you know you have like pretty much all your stuff i can't get
363
00:24:24,178 --> 00:24:27,608
the actual key data but i can get every all the rest of the metadata about the
364
00:24:27,608 --> 00:24:29,538
key and i can see all your models and i can send requests,
365
00:24:30,438 --> 00:24:35,038
but it did try like fuzz insert uh sir xng didn't find anything there so good
366
00:24:35,038 --> 00:24:38,938
good and then as a parallel request i was checking out um the new
367
00:24:39,358 --> 00:24:42,918
meta model uh muse glimmer that they released because that was their first open
368
00:24:42,918 --> 00:24:46,468
weight model for a while and this is before we set up Hextrike.
369
00:24:46,468 --> 00:24:49,162
So I just had that run and trying to do,
370
00:24:49,644 --> 00:24:53,102
Because a bunch of these tools are also in Nix packages. So I did a separate
371
00:24:53,102 --> 00:24:55,982
attempt with an unknown model. So it was kind of a mixed bag.
372
00:24:55,982 --> 00:24:59,242
But to just see like, well, if I just give you some of the basic tools that
373
00:24:59,242 --> 00:25:02,392
you would want anyway, how far can you get on the same thing?
374
00:25:02,392 --> 00:25:02,722
Sure.
375
00:25:02,943 --> 00:25:06,222
And kind of similar results, not as rich, not as well structured,
376
00:25:06,222 --> 00:25:10,512
but it did get, it did find basically the same thing. It was telling though, because one of the...
377
00:25:10,712 --> 00:25:13,272
This is using the meta self-hosted model?
378
00:25:13,272 --> 00:25:17,752
Yes. And I was running it on a rented RTX A6000.
379
00:25:17,752 --> 00:25:22,302
um one issue with that model is it seems to be kind of high with hallucinations
380
00:25:22,302 --> 00:25:26,702
and oh after doing a review like it did all of the stuff it just definitely
381
00:25:26,702 --> 00:25:30,232
did some exaggerating in the report so it's another like you're gonna if you're
382
00:25:30,232 --> 00:25:32,652
going to use this kind of automation definitely apply,
383
00:25:33,112 --> 00:25:35,062
sort of good techniques to cut down that kind of.
384
00:25:35,062 --> 00:25:38,512
I'd be curious if you tried one of the distilled kimmy k3 models where they've
385
00:25:38,512 --> 00:25:41,609
left in all the cybers offensive defensive stuff.
386
00:25:42,195 --> 00:25:45,887
Good idea that could be some some follow-up yeah yeah i did try like a whole
387
00:25:46,079 --> 00:25:50,578
crisscross of models i put in the doc deep seek memo quen's nematron so i was,
388
00:25:51,228 --> 00:25:54,462
i drove a few of this with a bunch of them just to see which ones would refuse
389
00:25:54,462 --> 00:25:55,702
and which ones would actually i got.
390
00:25:55,702 --> 00:26:00,992
I got constant refusal from um gpt constant refusal like it as soon as it realized
391
00:26:00,992 --> 00:26:05,062
it was dealing with a cyber security tool it would bail it could build all the
392
00:26:05,062 --> 00:26:06,744
scaffolding and all the configs,
393
00:26:07,534 --> 00:26:10,792
but when it kind of like dug in and realized, oh, no, this is a tool for hacking,
394
00:26:10,792 --> 00:26:12,612
it would stop the whole session.
395
00:26:13,443 --> 00:26:19,439
So I have to give a huge shout out to Minimax M3 thinking, not only is that
396
00:26:19,439 --> 00:26:24,629
sucker an open source model, but like never said no, never said no.
397
00:26:24,629 --> 00:26:28,499
Now, it's not the most clever model, but it's a hell of a worker.
398
00:26:28,499 --> 00:26:32,369
And it had no problem driving some of this for me when GPT would say no.
399
00:26:32,369 --> 00:26:34,509
And I'm trying to do self-defense here. I'm not trying to attack anybody.
400
00:26:34,509 --> 00:26:35,589
I'm just trying to do self-defense.
401
00:26:36,170 --> 00:26:40,802
Also, I got to try Grok 4.6 for like 15 minutes before I ran out of usage.
402
00:26:41,284 --> 00:26:46,319
And that also had no problem. and boy did it cook so yeah i like that you tried
403
00:26:46,319 --> 00:26:48,749
the different models i also use deep seek for a lot.
404
00:26:48,941 --> 00:26:52,929
Yeah i think the only one of the like uh open ones or you know that non-frontier
405
00:26:52,929 --> 00:26:57,229
class was like high three that refused me on one part of that yeah it was kind
406
00:26:57,229 --> 00:27:00,289
of surprising um but the rest of them yeah it was all totally fine.
407
00:27:01,358 --> 00:27:04,645
Yeah, the bouncing around sort of stunk. So one of the things I built into my
408
00:27:04,645 --> 00:27:07,965
Hermes system is when it begins, so normally it's being,
409
00:27:09,225 --> 00:27:12,105
it's like, it might be on, if it's on a GPT model, when it begins a process,
410
00:27:12,105 --> 00:27:15,105
it has to switch over to Minimax, or if it's really going deep,
411
00:27:15,105 --> 00:27:18,255
it could go, yeah, actually, it has a, it drops to DeepSeek,
412
00:27:18,255 --> 00:27:20,445
and if DeepSeek's slow or unavailable, it uses Kimi K3.
413
00:27:20,445 --> 00:27:20,985
Oh, nice.
414
00:27:20,985 --> 00:27:22,235
Yeah, it's got like a whole-
415
00:27:22,265 --> 00:27:22,735
A little tiered.
416
00:27:22,735 --> 00:27:26,365
System. I love it. Yeah, yeah. So just as a recap, you kind of have these goals,
417
00:27:26,365 --> 00:27:29,058
these attack goals, these audit goals that you give Hextrike,
418
00:27:29,481 --> 00:27:33,645
and then you task the agent to go off and perform one of those audit goals.
419
00:27:33,645 --> 00:27:37,185
Hextrike runs all of the various tools, orchestrates all of the stuff you've
420
00:27:37,185 --> 00:27:38,955
heard about for years, plus stuff you've never heard of.
421
00:27:39,367 --> 00:27:44,095
If it finds something, it then sort of can kick off a next layer.
422
00:27:44,095 --> 00:27:48,017
So there's a level one pass, a level two pass, and that level three pass,
423
00:27:48,255 --> 00:27:51,245
it can actually go in there and try to exploit stuff if you've given it permission
424
00:27:51,245 --> 00:27:53,166
to do that and investigate further.
425
00:27:53,775 --> 00:27:59,155
So that is sort of the setup I wanted. And I figured we could do a little demo if you want.
426
00:27:59,155 --> 00:27:59,987
Yeah, we should.
427
00:28:00,138 --> 00:28:04,102
You want to try it? See how it goes? So I have it ready to go.
428
00:28:04,945 --> 00:28:10,445
I will say that for time I'm not going to do the most extensive,
429
00:28:10,445 --> 00:28:12,269
right? Because there's 150 different tools in here.
430
00:28:12,687 --> 00:28:15,725
All of this. So the way this kicks off is I prompt my agent,
431
00:28:15,725 --> 00:28:19,519
my Hermes agent data to access the,
432
00:28:19,995 --> 00:28:25,215
system the hex strike system via a set of mcps and then it has a separate set
433
00:28:25,215 --> 00:28:28,895
of wrappers i've created to sort of audit and monitor the process and then it
434
00:28:28,895 --> 00:28:32,331
generates a markdown report and it saves it to a sync thing directory
435
00:28:32,760 --> 00:28:37,404
that will sync to my computer so when we're done we'll get the high level results sound good boys
436
00:28:37,834 --> 00:28:39,587
are you ready here we go,
437
00:29:11,779 --> 00:29:14,426
Oh, yeah, I forgot to mention it. It plays a little thinking music while it
438
00:29:14,426 --> 00:29:15,806
scans. That's how I roll.
439
00:29:16,026 --> 00:29:16,306
Mandatory.
440
00:29:16,306 --> 00:29:17,096
It's a nice touch.
441
00:29:17,096 --> 00:29:20,256
Thank you. Thank you. So, all right. So here we got our report.
442
00:29:20,256 --> 00:29:24,539
This is the box we retired last week. It's still online because it's finishing up some work.
443
00:29:25,497 --> 00:29:29,566
And it's not a perfect report. I think I could have turned it up a little bit
444
00:29:29,566 --> 00:29:30,953
and had to be a little more aggressive.
445
00:29:31,679 --> 00:29:35,319
So we don't have any, like, massive vulnerabilities standing out here.
446
00:29:36,102 --> 00:29:40,259
But it discovered 10 TCP services were reachable and tested remotely.
447
00:29:40,775 --> 00:29:45,146
and it discovered that OpenSSH identifies itself as 8.2p1.
448
00:29:45,797 --> 00:29:47,526
That doesn't sound modern.
449
00:29:47,735 --> 00:29:53,372
And NGINX identifies itself as 117.18. Cockpit is well behind as well.
450
00:29:54,429 --> 00:29:56,426
Here's the one I thought you might find interesting though, Wes.
451
00:29:57,854 --> 00:30:01,917
Port 3000 leaks an application stack trace to an unauthenticated scanner.
452
00:30:03,206 --> 00:30:03,838
What's that?
453
00:30:07,094 --> 00:30:11,266
A malformed basic http request produces a 500 internal survey or the response
454
00:30:11,266 --> 00:30:16,869
exposes the internal paths including app utils proxy js app utils safe handler js
455
00:30:17,270 --> 00:30:21,176
and expresses router internals it even reveals the failing operation cannot
456
00:30:21,176 --> 00:30:23,040
read properties of undefined reading ends with,
457
00:30:24,387 --> 00:30:27,836
so it's sort of an information disclosure error handling weakness it discovered
458
00:30:27,836 --> 00:30:31,046
that would be a little interesting to push on potentially like you read what's
459
00:30:31,046 --> 00:30:34,486
on 3000 so you could come back one of the things you could do this report is
460
00:30:34,486 --> 00:30:36,986
say all right come back and let's push on that right because you get.
461
00:30:36,986 --> 00:30:38,016
Things you can go drill down.
462
00:30:38,016 --> 00:30:42,546
On if it seems worthwhile it kind of it kind of critiques the uh bitcoin lightning
463
00:30:42,546 --> 00:30:49,846
setup we have for uh hey for responding to network requests anything is jump
464
00:30:49,846 --> 00:30:51,496
out anything jump out at you wes,
465
00:30:54,460 --> 00:30:58,080
It gave us a one-sentence takeaway. The audit found a surprisingly broad and
466
00:30:58,080 --> 00:31:01,760
somewhat chatty surface, including admin, Bitcoin, Lightning,
467
00:31:01,760 --> 00:31:05,200
and RPC interfaces. But the part designed to determine whether any of this actually
468
00:31:05,200 --> 00:31:08,980
is vulnerable and failed, it failed because we didn't do the actual deeper scan.
469
00:31:09,460 --> 00:31:13,187
So the strongest conclusion is interesting exposure, incomplete security assessment,
470
00:31:13,431 --> 00:31:14,772
no vulnerabilities detected yet.
471
00:31:15,631 --> 00:31:18,940
So then it gives us a list of what we could do next here, five further steps
472
00:31:18,940 --> 00:31:23,967
to drill in deeper here, and get Nuselli giving us a complete working vulnerability report.
473
00:31:24,118 --> 00:31:27,580
Nuselli completes the report, but sometimes it doesn't complete in time,
474
00:31:27,580 --> 00:31:30,270
so it doesn't get included. And then we also...
475
00:31:30,440 --> 00:31:33,400
Oh, yeah, I think that was one thing I saw, the bot identify with Hextrite,
476
00:31:33,400 --> 00:31:35,740
some timeouts weren't always handled kind of that great.
477
00:31:35,740 --> 00:31:38,346
Yeah, yeah. So there's a little bit you have to fix in there.
478
00:31:38,915 --> 00:31:43,385
Also, it suggests we renew or rotate some of our TLS certificates before September 6th.
479
00:31:43,582 --> 00:31:48,780
And I think that also speaks to this, to like, it's kind of nice just from understanding
480
00:31:48,780 --> 00:31:51,780
what all is happening, especially on a box like this that's like just been kind
481
00:31:51,780 --> 00:31:55,190
of off in the corner right checking up on things especially you could go poke
482
00:31:55,190 --> 00:31:57,200
around like your whole tail net and check things out.
483
00:31:57,200 --> 00:31:57,840
There or.
484
00:31:57,840 --> 00:31:58,611
You know whatever.
485
00:31:58,780 --> 00:32:01,850
Right once the bulk of getting hex strike set up and depending how you do it
486
00:32:01,850 --> 00:32:04,194
it could be a really quick thing or it could be a week-long thing,
487
00:32:04,670 --> 00:32:08,240
um but then the end of thing is like all right go check this box go audit it
488
00:32:08,240 --> 00:32:11,380
for me and then you can have a produce report that's consumable for yourself
489
00:32:11,380 --> 00:32:14,626
or a team of people just depends on what your audience is so that's all manageable,
490
00:32:15,357 --> 00:32:18,360
um and there is a few things in here like we need to get open ssh if we were
491
00:32:18,360 --> 00:32:19,462
going to keep this box online,
492
00:32:20,440 --> 00:32:23,590
my immediate takeaways are we would have to update we would have to update open
493
00:32:23,590 --> 00:32:25,342
ssh nginx and cockpit and,
494
00:32:26,381 --> 00:32:30,830
we'd probably want to look at this json rpc service on 5 000 or 50 000 or whatever
495
00:32:30,830 --> 00:32:34,770
it is and the service on 3 000 we probably need to figure out what those are
496
00:32:34,770 --> 00:32:36,464
this http thing that we're leaking.
497
00:32:37,440 --> 00:32:42,380
It does at least seem uh like it makes sense given what the box is.
498
00:32:42,380 --> 00:32:42,660
Which is.
499
00:32:42,660 --> 00:32:46,360
A crazy smattering of docker composed containers with a whole bunch of different ports.
500
00:32:46,900 --> 00:32:50,855
And those paths are umbral paths that it's exposing through that port 3000.
501
00:32:52,080 --> 00:32:56,114
So that, you know, right there, if I were putting my old hat on back in the
502
00:32:56,114 --> 00:32:58,614
day when I was getting hired to do these security audits with tools that were
503
00:32:58,614 --> 00:33:01,944
way less cooler than this, that would be the number one thing I would go.
504
00:33:02,404 --> 00:33:04,999
I'd go knock on that port 3000 a lot more and figure out what's going on there,
505
00:33:05,864 --> 00:33:09,854
because it's revealing the internal structure of the entire frickin' Umbral
506
00:33:09,854 --> 00:33:12,279
setup, which is where the Bitcoin node lives.
507
00:33:12,842 --> 00:33:15,464
So that's a pretty juicy reveal right there. And if you knew going in,
508
00:33:15,844 --> 00:33:18,684
like I do, the Umbral app structure, I would immediately recognize that.
509
00:33:20,569 --> 00:33:25,044
So machine or not, right? I could take this report. I could take it further. Or the other thing.
510
00:33:25,084 --> 00:33:29,204
That's what's kind of great, right? Like you don't need to just rely on the,
511
00:33:29,664 --> 00:33:33,281
like it can just be a tool that you can use. It could be a tool to like work together.
512
00:33:33,456 --> 00:33:35,834
You can learn a bunch of how the tools work and drive it yourself.
513
00:33:35,834 --> 00:33:39,454
The Hermes system, this is why I wanted to integrate it. The Hermes system knows what this system is.
514
00:33:39,454 --> 00:33:44,134
It knows what this box's role is. It's important. So it, it knows like in a
515
00:33:44,134 --> 00:33:47,864
way that makes it very useful because it, first of all, before it even scanned
516
00:33:47,864 --> 00:33:51,024
this node, I never told any, it just, Hey, this is an important economic machine.
517
00:33:51,024 --> 00:33:54,514
Do we want to be careful? Like it knew all of that, right? But it also knows
518
00:33:54,514 --> 00:33:59,484
Umbral's on there. So it can use all of this information to inform its attack.
519
00:34:00,122 --> 00:34:03,176
So it's really, if you have an agent system that's managing infrastructure,
520
00:34:03,542 --> 00:34:06,484
you can stand this up alongside of it. It can use that information to essentially
521
00:34:06,484 --> 00:34:08,499
go be a chaos monkey under your control.
522
00:34:08,841 --> 00:34:13,509
And you can turn up the heat depending if you just want port knocking and pinging, you can do that.
523
00:34:13,886 --> 00:34:17,164
But if you want like CVE identification and then go and try to exploit it,
524
00:34:17,164 --> 00:34:18,698
you can do that, right? You can turn it all the way up.
525
00:34:19,744 --> 00:34:22,504
But I do think it is something that's kind of a more advanced tool that people
526
00:34:22,504 --> 00:34:25,589
need to be extremely careful with. But –,
527
00:34:26,814 --> 00:34:30,133
looking at this open ssh situation right like now i could go point this at some
528
00:34:30,133 --> 00:34:31,980
of our github code repos or something like that.
529
00:34:32,149 --> 00:34:34,873
Yeah that'd be the next thing that i was kind of get trying to get set up for
530
00:34:34,873 --> 00:34:37,673
but haven't yet would be would be trying to get the bot tooled up to go see
531
00:34:37,673 --> 00:34:40,217
if it could find things like a zero day or
532
00:34:40,566 --> 00:34:44,053
issue in code or especially if you compare right you have the metadata report
533
00:34:44,053 --> 00:34:48,043
so you know what versions are running on whatever boxes you're trying to check out so then
534
00:34:48,423 --> 00:34:52,901
it can go clone that exact version and then go check through it and run tests or you know set up,
535
00:34:53,459 --> 00:34:56,953
uh that version running locally to hit against as it develops a theory that kind of.
536
00:34:56,953 --> 00:35:00,103
Thing i think if you want to just play with it your setup you know where you
537
00:35:00,103 --> 00:35:04,563
had a cali vm really straightforward got it going probably within an hour i would.
538
00:35:04,563 --> 00:35:06,063
Imagine yeah it was pretty it was pretty easy.
539
00:35:06,063 --> 00:35:09,803
Yeah uh and so that's how i want to try this and see what it tells me see what
540
00:35:09,803 --> 00:35:11,383
i can figure out with this for.
541
00:35:11,383 --> 00:35:14,413
Me obviously it would be a little more work like if i i need to set up like
542
00:35:14,413 --> 00:35:17,143
proper bridge networking or put it like if i was trying to do it proper like
543
00:35:17,143 --> 00:35:19,523
on a land or you know corporate environment or something like that it'd be more
544
00:35:19,523 --> 00:35:22,807
work but because i was doing a pretty minimal test run it made it easy.
545
00:35:22,935 --> 00:35:26,323
Yeah and it's you can do it all the way if you want you could turn up all the
546
00:35:26,323 --> 00:35:29,553
way there's a lot of tools out there to do this kind of thing so if you have
547
00:35:29,553 --> 00:35:32,483
any suggestions boost.jupiterbroadcasting.com and let us know.
548
00:35:32,483 --> 00:35:35,317
Yeah because we could we could only talk about some yeah yeah.
549
00:35:36,224 --> 00:35:37,624
I have a couple questions for you, gents.
550
00:35:37,624 --> 00:35:38,173
Go for it!
551
00:35:38,774 --> 00:35:43,594
You mentioned Kali was an important tool to use as a base for this research.
552
00:35:43,894 --> 00:35:46,154
I actually just pulled as much as I could from Nick's packages,
553
00:35:46,154 --> 00:35:48,084
but Wes, I think, has a nice cheat code there.
554
00:35:48,914 --> 00:35:53,854
Yeah, my curiosity there is Kali was the golden goose for doing this previously
555
00:35:53,854 --> 00:35:57,191
because it sort of collected all these tools in a place that you could use them.
556
00:35:57,690 --> 00:36:02,131
And that sounds a lot like what Hextrike is doing. It's collecting a bunch of
557
00:36:02,467 --> 00:36:03,854
at least tool knowledge.
558
00:36:04,194 --> 00:36:07,024
It's not providing the tools themselves, but that's kind of trivial at this point.
559
00:36:07,599 --> 00:36:12,690
And so is this sort of the new Cali that people are going to go to or these tools at least?
560
00:36:13,350 --> 00:36:16,386
I mean, I think it might be fair. Or the next wave, right? Like how we've seen,
561
00:36:16,996 --> 00:36:20,564
this is a really stretched analogy, right? But we see a whole lot of people
562
00:36:20,564 --> 00:36:24,867
generating songs and pictures that could never make music or take a great picture before, right?
563
00:36:25,349 --> 00:36:27,784
So now I think you're going to see a lot of people. And you see a lot of people
564
00:36:27,784 --> 00:36:32,014
making some good review PRs, some bad PRs.
565
00:36:32,774 --> 00:36:37,854
You see a lot more code getting generated. So what you have now is if you know
566
00:36:37,854 --> 00:36:42,468
just a little bit about your network, you now have a system that can operate the tools for you.
567
00:36:43,252 --> 00:36:48,679
This is both enabling and also risky. It's a double-edged sword.
568
00:36:48,679 --> 00:36:50,926
It has more leverage, so there's more leverage.
569
00:36:51,152 --> 00:36:55,799
So before it took an understanding of how to orchestrate and stack these tools
570
00:36:55,799 --> 00:36:58,799
together, like you needed to have a sense of, oh, there's something like you
571
00:36:58,799 --> 00:36:59,899
would do an end map yourself.
572
00:37:00,213 --> 00:37:03,979
You would see that port 3000 yourself. You would go try to poke at it with Telnet
573
00:37:03,979 --> 00:37:05,582
or throw some curls at it or whatever.
574
00:37:06,121 --> 00:37:08,719
And then you would just have that instinct and you would use additional tools
575
00:37:08,719 --> 00:37:10,779
to drill down and go do the searching you need to do.
576
00:37:10,779 --> 00:37:13,599
There's various workflows you've learned, right? Attack patterns,
577
00:37:13,599 --> 00:37:16,239
processes that human experts have developed over the years.
578
00:37:16,239 --> 00:37:19,129
Now this thing's doing it for you. It can do it dynamically.
579
00:37:19,129 --> 00:37:21,371
It can be updated every single week.
580
00:37:21,528 --> 00:37:24,499
And it can do it at scale.
581
00:37:24,919 --> 00:37:30,718
So the real trick now is the knowledge about it, how to set it up, that kind of knowledge.
582
00:37:31,007 --> 00:37:36,069
And then the budget to spend the tokens on some API or local model.
583
00:37:36,069 --> 00:37:38,399
Like there are distilled models now that can do this locally.
584
00:37:38,399 --> 00:37:42,438
Like there's a Quen model that runs locally. even on laptops that can do this.
585
00:37:42,756 --> 00:37:46,479
And there is that Kimi K3 model that can run on some reasonably powerful local
586
00:37:46,479 --> 00:37:48,161
systems now that's distilled that can do this.
587
00:37:48,445 --> 00:37:52,241
These are open source and local. There's also lots available via the APIs.
588
00:37:52,519 --> 00:37:55,265
So if you have access to hardware or you can pay for API credits,
589
00:37:55,515 --> 00:37:59,079
you essentially have access to this now. That's the barrier now.
590
00:38:00,746 --> 00:38:03,475
Can we talk about your token budget this week?
591
00:38:05,830 --> 00:38:06,119
Really?
592
00:38:07,359 --> 00:38:08,479
I know it's not in the doc.
593
00:38:08,479 --> 00:38:10,119
But like- You're going to shame me like that?
594
00:38:10,119 --> 00:38:11,068
It's important.
595
00:38:11,351 --> 00:38:16,019
So, you know, I have not really had to pay a lot for tokens recently because
596
00:38:16,339 --> 00:38:18,822
I find Minimax to be extremely useful.
597
00:38:19,799 --> 00:38:24,289
And it gets me really, really far. However, to get this over the hump,
598
00:38:24,289 --> 00:38:27,372
I did end up pulling in some Kimi K3 and some Grok.
599
00:38:27,930 --> 00:38:32,939
And so to build this for my system, I spent my budget on this,
600
00:38:32,939 --> 00:38:39,743
I guess you could say, I guess, was $43.90. And that was 716.4 million tokens.
601
00:38:41,027 --> 00:38:48,821
So it's not a cheap thing, but for me, $43, $45 to now to be able to audit JB
602
00:38:48,821 --> 00:38:53,808
infrastructure on demand in a report style that I can share with you guys.
603
00:38:53,971 --> 00:38:58,001
And a lot of that, I imagine, was the setup and tuning that would be amortized
604
00:38:58,001 --> 00:39:00,461
over each individual scan, which would not be that much. And you can probably
605
00:39:00,461 --> 00:39:01,691
drive with not the Premiere model.
606
00:39:02,111 --> 00:39:05,801
100%, because once you have the structure, Minimax is totally capable of handling
607
00:39:05,801 --> 00:39:07,403
it, and I can basically run that forever.
608
00:39:07,885 --> 00:39:13,061
um but yeah you you wanted you wanted something a little more advanced to build
609
00:39:13,061 --> 00:39:16,685
out the structure and get this thing right and so some kimmy in there some grok in there,
610
00:39:17,475 --> 00:39:21,051
probably oh yeah lots of deep seek lots of deep seek but deep seek's pretty
611
00:39:21,051 --> 00:39:24,551
cheap that worked and then mine's all using podman containers that spin up and
612
00:39:24,551 --> 00:39:27,981
then disappear when they're done and stuff like that um and then like with the
613
00:39:27,981 --> 00:39:28,934
different levels of gating.
614
00:39:29,433 --> 00:39:30,291
Oh that's fun.
615
00:39:30,291 --> 00:39:32,452
Mm-hmm. Mm-hmm. Mm-hmm.
616
00:39:33,451 --> 00:39:37,551
I'm curious, what's the next step then? Like, are you going to push this further
617
00:39:37,551 --> 00:39:43,631
and look at all the boxes on the JB network? Are you going to put it aside for
618
00:39:43,631 --> 00:39:47,001
a second until you reassess whether you put enough controls in?
619
00:39:47,011 --> 00:39:50,621
I'm going to tweak the reporting a bit and the timeout issue a little bit so
620
00:39:50,621 --> 00:39:51,941
I can get more information in the report.
621
00:39:51,941 --> 00:39:56,091
But then what I think it's probably best to point at the boxes that are sort
622
00:39:56,091 --> 00:39:59,791
of on the top of our list to retire and kind of just make a priority list based
623
00:39:59,791 --> 00:40:03,621
on these findings and just sort of use that data to derive our decisions to
624
00:40:03,621 --> 00:40:04,767
sort of shore up infrastructure.
625
00:40:05,051 --> 00:40:08,081
Yeah, that and maybe whatever the few maximally exposed things are.
626
00:40:08,081 --> 00:40:13,361
Yeah. And hopefully, you know, find stuff before we get to a point where this
627
00:40:13,361 --> 00:40:16,321
stuff is getting widely exploited. And we, you know, we don't really want to
628
00:40:16,321 --> 00:40:20,061
be in a position where once a week or every few days we're SSHing into these
629
00:40:20,061 --> 00:40:21,031
boxes and updating them.
630
00:40:21,071 --> 00:40:21,311
Right.
631
00:40:21,491 --> 00:40:24,881
And if we do get to that point, we want to have a fleet that's lean enough that it's manageable.
632
00:40:25,119 --> 00:40:30,553
And probably reset up in a declarative, repeatable way so that that becomes a more sane task.
633
00:42:21,281 --> 00:42:24,356
Got a bunch of beautiful feedback this week, and we're going to start with Nathan.
634
00:42:24,834 --> 00:42:29,177
Nathan says, literally just discovered this podcast, and you happen to mention
635
00:42:29,177 --> 00:42:32,443
Trek, which has been my recent obsession.
636
00:42:32,768 --> 00:42:34,947
I'm currently planning my honeymoon with it.
637
00:42:34,947 --> 00:42:35,567
Oh, cool.
638
00:42:35,567 --> 00:42:37,077
Oh, he means the tool.
639
00:42:37,077 --> 00:42:43,319
Not the show. Yeah, not Star Trek. No. The collaborative road trip and travel planning.
640
00:42:44,167 --> 00:42:48,757
Okay. I'm currently planning my honeymoon, congratulations, with it,
641
00:42:48,757 --> 00:42:54,152
and it's been a dream compared to my normal spreadsheet slash calendar workflow for trips.
642
00:42:54,791 --> 00:42:59,427
It comes with a built-in MCP, so I hooked it up to my LOM setup, and I've been doing,
643
00:43:00,007 --> 00:43:04,917
some research that way to try and find some spots off the beaten path and working
644
00:43:04,917 --> 00:43:09,477
them into the trip plan to include travel time, cluster locations,
645
00:43:09,477 --> 00:43:11,149
proximity to our hotels.
646
00:43:11,904 --> 00:43:16,367
It's a super polished app. I haven't tested out the collaborative features yet,
647
00:43:16,367 --> 00:43:18,127
but they all seem quite promising.
648
00:43:18,527 --> 00:43:22,567
figured I'd write in to give the Trek recommendation a plus one.
649
00:43:22,567 --> 00:43:27,142
Now off to download the backlog of the show because, well, it seems super cool.
650
00:43:27,837 --> 00:43:32,737
You know, you can plug on all kinds of like travel APIs to those agents as well.
651
00:43:32,737 --> 00:43:33,907
There's all kinds of stuff with those.
652
00:43:34,267 --> 00:43:36,217
You bring it all together with Trek. I think that's great.
653
00:43:36,217 --> 00:43:40,147
I love how it's just like such a thoughtful thing to spend time crafting.
654
00:43:40,147 --> 00:43:43,447
And thank you, Nathan. Glad you found the show. I'll take the next one.
655
00:43:43,447 --> 00:43:46,917
Peter writes in, I just want to turn you guys on to TopGrade.
656
00:43:47,352 --> 00:43:50,497
if you haven't heard of it yet. It updates all the things in one command so
657
00:43:50,497 --> 00:43:53,327
you don't have to remember what you have installed. Super useful.
658
00:43:53,327 --> 00:43:55,595
Upgrade all the things with top grade.
659
00:43:56,298 --> 00:44:01,041
This may have been an agent pick on the show way back in the day. Um...
660
00:44:02,387 --> 00:44:06,503
It doesn't support every distro, obviously, but it does support quite a few of them.
661
00:44:06,840 --> 00:44:09,726
It also got the coveted Drew plus one behind the scenes.
662
00:44:09,726 --> 00:44:12,586
Oh, did it? Uh-huh, yes, it did. Does he use it?
663
00:44:12,586 --> 00:44:15,556
Yeah. Second this, top grade is super rad, says Drew.
664
00:44:15,556 --> 00:44:18,536
That is nice. That's one of the things I like about the uBlue stack is they
665
00:44:18,536 --> 00:44:21,805
have that uUpdate or whatever. I don't even know. It just runs.
666
00:44:22,089 --> 00:44:23,947
And that updates all your packages and your flat packles.
667
00:44:25,509 --> 00:44:26,656
You want to take that next one there, Mr.
668
00:44:26,656 --> 00:44:30,166
P? Yeah, we got actually two messages from Magnus here.
669
00:44:30,166 --> 00:44:30,486
Okay.
670
00:44:30,486 --> 00:44:34,116
First one here. Hi, guys. thanks for the fantastic content universe you're providing
671
00:44:34,116 --> 00:44:37,956
long-time listener and intermittent member i thought you might find this useful
672
00:44:38,256 --> 00:44:40,577
yes this is completely shameless self-promotion,
673
00:44:41,343 --> 00:44:44,496
paul hibbert even made a video on it and i thought maybe you guys would find
674
00:44:44,496 --> 00:44:45,923
some exciting ways in using this,
675
00:44:46,394 --> 00:44:51,576
home assistant tailored open code app super simple to start using and flexible
676
00:44:51,576 --> 00:44:55,996
and it seems like it's sort of an open code that you add on to home assistant
677
00:44:55,996 --> 00:45:00,099
and then you can sort of have it directly control Home Assistant just from the plug-in.
678
00:45:00,593 --> 00:45:01,226
In open code.
679
00:45:01,226 --> 00:45:04,105
Yeah so that fascinating it can drive everything.
680
00:45:05,080 --> 00:45:08,702
I mean, that makes sense. Home Assistant has an extensive API and an MCP.
681
00:45:08,940 --> 00:45:12,179
So it seems like that should be pretty doable. Very nice.
682
00:45:12,760 --> 00:45:15,468
Yeah, it seems pretty clever. I haven't tried it. I've only checked it a little
683
00:45:15,468 --> 00:45:18,348
bit here when I was gathering the feedback, but it's a smart idea,
684
00:45:18,348 --> 00:45:20,108
especially if you don't already have any of that info set up,
685
00:45:20,108 --> 00:45:21,468
but you want something to help you manage.
686
00:45:21,468 --> 00:45:24,660
Before you get his next one, can I just say I'm surprised I haven't heard a lot of people talking.
687
00:45:25,066 --> 00:45:31,121
Hermes 0.20 added conversational voice support.
688
00:45:31,603 --> 00:45:37,981
So that evening, I set up an Anker USB-C speakerphone that has two microphones and a speaker.
689
00:45:38,988 --> 00:45:44,188
And immediately, it outclasses anything the Alexa units or the HomePods or the
690
00:45:44,188 --> 00:45:45,255
Google Homes have ever done.
691
00:45:45,696 --> 00:45:50,050
And it ties in with my home assistant. And I can even say things like, play Magnum.
692
00:45:50,822 --> 00:45:54,948
And it will activate the Apple TV. It'll launch the Infuse app.
693
00:45:54,948 --> 00:45:58,891
It'll play the most recent episode of Magnum PI. And I don't have to even touch the remote.
694
00:45:59,286 --> 00:46:02,571
and I can turn I control lights temperature it's way better,
695
00:46:03,123 --> 00:46:07,418
than anything from any of the big tech companies and I don't see anybody talking
696
00:46:07,418 --> 00:46:11,428
about it and I even like the thinking music I have thinking music uh when when
697
00:46:11,428 --> 00:46:14,314
I when you like say hey you know hey Laura what's the weather uh,
698
00:46:15,157 --> 00:46:18,948
he's pulling from my local weather station over home assistant and while he's
699
00:46:18,948 --> 00:46:21,948
doing that I have a little thinking music that plays I like to do the thinking music.
700
00:46:21,948 --> 00:46:27,288
I like that so you know what's going on uh magnus goes on listening to the backwards
701
00:46:27,288 --> 00:46:31,132
episode where you dig into the old xeon server yeah you mentioned self-documenting
702
00:46:31,434 --> 00:46:34,508
have you ever thought about running a sherpa type agent on your server's task
703
00:46:34,508 --> 00:46:36,338
with keeping tabs on all the stuff running.
704
00:46:36,338 --> 00:46:36,488
There.
705
00:46:36,948 --> 00:46:41,318
The config containers mappings ports and proxies this could be posted as json
706
00:46:41,318 --> 00:46:43,855
somewhere to keep a centralized documentation repo,
707
00:46:45,040 --> 00:46:48,163
And once it's there, you could build dashboards from it.
708
00:46:48,503 --> 00:46:51,083
And the best part, it could be a set and forget type feature,
709
00:46:51,083 --> 00:46:54,141
just picking up on new stuff being set up or config that changes.
710
00:46:54,420 --> 00:46:59,403
So unofficially, my agent data does sort of manage a lot of the important infra
711
00:46:59,403 --> 00:47:03,123
and has a little index of everything, but that's just on my system.
712
00:47:04,410 --> 00:47:07,383
So yeah, that would be something we should formalize. Hey, how about this?
713
00:47:07,383 --> 00:47:09,837
Thank you, by the way. Appreciate that, Magnus. How about this?
714
00:47:10,296 --> 00:47:19,143
Mike wrote in, you could try running and sharing this, And he links us to something called CBBS Pi.
715
00:47:19,563 --> 00:47:23,663
A vintage CBBS style bulging board system emulator for macOS,
716
00:47:23,663 --> 00:47:25,627
Linux, Docker, and the Raspberry Pi.
717
00:47:26,294 --> 00:47:28,543
Something's happening here. I think we're going to have a BBS.
718
00:47:29,103 --> 00:47:30,143
The energy is building.
719
00:47:30,143 --> 00:47:31,931
The energy is building. I don't know if this is it.
720
00:47:33,323 --> 00:47:39,142
I'm kind of, I hate to be this guy. I just can't even stand sitting at my Raspberry Pi anymore.
721
00:47:39,142 --> 00:47:43,402
It just feels so archaic and slow. And like, it's just this weird platform that
722
00:47:43,402 --> 00:47:47,562
I have to bend over just to get working right. And then like do weird twister
723
00:47:47,562 --> 00:47:53,532
games versus like an x86 SBC that just, just works, dude. Like, I don't know.
724
00:47:53,832 --> 00:47:56,560
I don't know. I'm having a hard time. I got too many pies and I'm having a hard time.
725
00:47:57,652 --> 00:48:00,264
Bretton, you want to wrap us up with Ryan's email?
726
00:48:00,910 --> 00:48:02,812
Ryan sent in a juicy one for the show.
727
00:48:03,152 --> 00:48:04,281
Ooh. All right.
728
00:48:04,944 --> 00:48:09,162
Not sure if you're still in the Apple or iOS ecosystem, but I just stumbled
729
00:48:09,162 --> 00:48:12,489
upon the Mother Hen app in the Apple store.
730
00:48:12,729 --> 00:48:14,572
It's written by Weston Bustron.
731
00:48:15,152 --> 00:48:22,642
Why am I writing you to inform you about this? Well, it's a purpose-built chicken egg hen laying app.
732
00:48:22,712 --> 00:48:22,952
Hey.
733
00:48:22,952 --> 00:48:26,899
And it tracks when eggs are ready by the flock.
734
00:48:29,318 --> 00:48:31,672
I mean, they just lay every morning. I don't understand.
735
00:48:31,672 --> 00:48:32,637
I like this next bit.
736
00:48:32,864 --> 00:48:33,171
Okay.
737
00:48:33,962 --> 00:48:38,892
It's somewhat random, but I know you're the original Chicken Coop Home Assistant guy.
738
00:48:38,892 --> 00:48:42,622
Thank you. So maybe it's worth checking it out as a $3 curiosity.
739
00:48:42,622 --> 00:48:46,576
I'm kind of curious what kind of an app you could use for chickens,
740
00:48:46,896 --> 00:48:50,361
as close as MQTT integration as you can get?
741
00:48:50,586 --> 00:48:56,272
You know, I think close to this line of thinking, Ryan, is I need to be able
742
00:48:56,272 --> 00:49:00,712
to take the camera feed I have of the chickens entering the roost box and coming
743
00:49:00,712 --> 00:49:04,396
out and be able to track that. Because that's the real signal.
744
00:49:04,779 --> 00:49:08,390
And like good little birdies, I'm so proud of them.
745
00:49:08,791 --> 00:49:10,892
They're all laying in the nest box.
746
00:49:11,391 --> 00:49:14,654
So far, they haven't laid anywhere else in the yard or in the run.
747
00:49:15,101 --> 00:49:18,672
So stinking proud of these birds. But, you know, I'm still trying to figure
748
00:49:18,672 --> 00:49:21,585
out which birds lay in the egg. So something like that, I think would be really good.
749
00:49:22,695 --> 00:49:25,233
There's some interesting information in the app description here.
750
00:49:25,233 --> 00:49:25,579
Okay.
751
00:49:26,323 --> 00:49:29,623
I guess there's a couple different parts to the app. There's three parts.
752
00:49:29,943 --> 00:49:33,503
There's the harvest tab, which is designed to be used on a daily basis.
753
00:49:33,805 --> 00:49:37,079
So when you go out and find the latest batch of eggs waiting for you to collect,
754
00:49:37,508 --> 00:49:41,693
you just like punch in some environmental factors such as light and stress and
755
00:49:41,693 --> 00:49:43,303
how they can affect the egg production.
756
00:49:43,823 --> 00:49:48,233
So by tracking all of that and the egg counts specifically, you can watch all
757
00:49:48,233 --> 00:49:50,813
of the trends and make some informed decisions.
758
00:49:50,813 --> 00:49:51,313
Okay.
759
00:49:52,659 --> 00:49:56,853
There's also a flock tab for keeping tabs on the members of your flock.
760
00:49:56,853 --> 00:49:58,923
I mean, you've named them all already, so that makes it pretty easy.
761
00:49:59,584 --> 00:50:03,203
So if you're like the authors here, sometimes it's hard to keep track of who's
762
00:50:03,203 --> 00:50:06,307
in the coop. So adding a picture or name goes a long way.
763
00:50:06,667 --> 00:50:10,083
For the breeders out there, they added a family tree as well.
764
00:50:12,723 --> 00:50:17,473
And there's a last tab here. It's the finances tab that gives you the ability
765
00:50:17,473 --> 00:50:21,883
to see, if you particularly want to, just how much your feathered friends are
766
00:50:21,883 --> 00:50:24,103
costing you in feed and other expenses.
767
00:50:24,103 --> 00:50:24,643
Oh.
768
00:50:25,277 --> 00:50:27,951
Or if you sell your eggs, how much money they're making you.
769
00:50:29,363 --> 00:50:30,893
You just don't open that tab, it's fine.
770
00:50:30,893 --> 00:50:34,162
One of the preview screenshots has my type of chicken in it. I love it.
771
00:50:34,609 --> 00:50:36,903
You know, this is actually, the more I think about it, interesting because I
772
00:50:36,903 --> 00:50:40,503
have particularly controlled the lighting and heating of the hen house to try
773
00:50:40,503 --> 00:50:44,393
to maintain chicken egg production during the winter. It'd be interesting to
774
00:50:44,393 --> 00:50:45,153
see if I can achieve that.
775
00:50:45,153 --> 00:50:46,503
Is data controlling that again?
776
00:50:46,863 --> 00:50:49,553
Well, that's all controlled by Home Assistant, Some potato does operate and
777
00:50:49,553 --> 00:50:54,729
monitor that. That's really good stuff. I like that, Ryan. Thank you very much for sending that in.
778
00:50:55,843 --> 00:50:56,778
There's some good stuff in there.
779
00:50:57,103 --> 00:51:00,459
And we'll put a link if you have some chickens to the Mother Hen app.
780
00:51:01,016 --> 00:51:04,069
And if you do have chickens, boost in and let us know. We want to hear about that.
781
00:51:08,573 --> 00:51:13,163
Gentlemen, it is time for Le Boos, and let's start out with Ol' Bridie,
782
00:51:13,163 --> 00:51:16,893
a.k.a. Kyron, coming in with a row of super McDucks.
783
00:51:16,893 --> 00:51:18,373
Wow, that's mega McDucks?
784
00:51:18,373 --> 00:51:20,265
Mega, mega ultra McDucks?
785
00:51:20,492 --> 00:51:21,473
That's a whole flock.
786
00:51:24,443 --> 00:51:26,736
222,222 Satoshis.
787
00:51:36,923 --> 00:51:37,591
Wow.
788
00:51:38,916 --> 00:51:39,555
Incredible.
789
00:51:39,907 --> 00:51:42,813
Amazing. That is really something. Thank you very, very much,
790
00:51:42,813 --> 00:51:47,003
sir. We appreciate that baller boost. Hey, new member. Hey, hey,
791
00:51:47,003 --> 00:51:49,265
hey. All right. Yes, yes.
792
00:51:51,103 --> 00:51:53,803
Old time lurker. The web boost is the best thing yet. I have previously tried
793
00:51:53,803 --> 00:51:56,253
Fountain, but the hassle of dealing with buying sets, it's just,
794
00:51:56,253 --> 00:51:58,043
well, I like this edition.
795
00:51:58,603 --> 00:52:01,723
It gives us normies a way to support without the eebie-jeebies. Thanks for all the fun.
796
00:52:02,883 --> 00:52:04,381
That's the idea. Make it easy.
797
00:52:04,567 --> 00:52:07,233
Just wait the one day that Fiat will give you the eebie-jeebies.
798
00:52:07,233 --> 00:52:10,183
But in the meantime, we appreciate it very, very much. You know,
799
00:52:10,183 --> 00:52:11,363
and he did it with ZapRite.
800
00:52:12,003 --> 00:52:15,413
So he got the sats. So I'm impressed all around. However you want to do it,
801
00:52:15,413 --> 00:52:18,528
man. We really appreciate it. And we thank you for being our baller.
802
00:52:18,923 --> 00:52:22,883
And look at this. Another Mega McDuck. Lutris.
803
00:52:23,243 --> 00:52:23,863
Lucitropy.
804
00:52:24,243 --> 00:52:26,288
All right. Also coming in with a Mega McDuck.
805
00:52:30,423 --> 00:52:31,895
222,222 sats.
806
00:52:43,355 --> 00:52:45,781
Wow. Thank you, sir. Thank you.
807
00:52:45,967 --> 00:52:50,164
Yeah, sorry guys. Last couple of boosts through Fountain. Splits didn't go right for some reason.
808
00:52:50,484 --> 00:52:52,684
Chris and JB got their splits, but the others didn't go through.
809
00:52:52,684 --> 00:52:54,364
So here's a rectifier boost.
810
00:52:54,724 --> 00:52:55,484
Keep up the good work.
811
00:52:55,964 --> 00:52:57,614
You didn't have to do that, but thank you.
812
00:52:57,624 --> 00:52:58,420
That's very sweet.
813
00:52:58,923 --> 00:52:59,730
Thank you very much.
814
00:53:00,661 --> 00:53:06,074
Well, we've got our Adversary 17 here with 54,321 sets.
815
00:53:06,074 --> 00:53:06,516
All right.
816
00:53:12,317 --> 00:53:17,814
I've gone to dial p get it plaid reversed oh i see because the episode was reversed
817
00:53:17,814 --> 00:53:22,174
last week and so he's gotten also he's gotten clever with.
818
00:53:22,174 --> 00:53:23,675
The numbers is what he's done there,
819
00:53:27,732 --> 00:53:28,194
uh-huh it's.
820
00:53:28,194 --> 00:53:30,754
Backwards i think he actually wanted that backwards.
821
00:53:30,754 --> 00:53:31,619
Yeah yeah well.
822
00:53:31,619 --> 00:53:35,004
Uh yeah i'm sure says I'll just escort myself out.
823
00:53:35,184 --> 00:53:39,264
I kind of liked it. Thank you, Versaries. Appreciate that. The Incredible Mulk
824
00:53:39,264 --> 00:53:42,605
comes in with 32,810 Satoshis.
825
00:53:47,527 --> 00:53:50,804
Hey, another long-time listener Jupiter Party member. Yes!
826
00:53:51,765 --> 00:53:54,264
Awesome. First-time booster. Thank you for all the hard work.
827
00:53:55,164 --> 00:53:58,104
Especially on the last few shows. Here's some help to keep the lights on.
828
00:53:58,104 --> 00:53:59,288
Thank you for the great content.
829
00:53:59,602 --> 00:54:02,974
And also, it's a zip code boost, boys.
830
00:54:02,974 --> 00:54:03,810
Ooh.
831
00:54:03,928 --> 00:54:04,624
Danger.
832
00:54:05,865 --> 00:54:07,572
Now, Wes, did you bring the...
833
00:54:07,682 --> 00:54:09,470
I pack the map every week.
834
00:54:09,749 --> 00:54:14,354
All right. All right. Let's look this up. I'm feeling like you're going to nail this one.
835
00:54:14,354 --> 00:54:17,124
Yeah. I'm feeling Eastern time zone, I think.
836
00:54:17,124 --> 00:54:19,544
Syncing it to the digital map for us. Okay. What do you got?
837
00:54:20,336 --> 00:54:22,794
Oh. Orlando, Florida.
838
00:54:22,794 --> 00:54:30,414
Ha ha. I knew it. I knew it. Hello, Orlando. Thank you for boosting in and for being a member, too.
839
00:54:30,414 --> 00:54:31,254
We appreciate it.
840
00:54:31,254 --> 00:54:32,265
Yeah. We do.
841
00:54:33,624 --> 00:54:37,525
IRU comes in with 11,111 sats.
842
00:54:42,304 --> 00:54:45,784
Now that the dust has settled, I've given BcacheFS a try.
843
00:54:46,104 --> 00:54:46,994
Hey, good job.
844
00:54:46,994 --> 00:54:50,430
I've set it up as the root FS with encryption and secure boot.
845
00:54:50,802 --> 00:54:54,813
Mixing different drives and setting copies on a per file or directory basis,
846
00:54:55,086 --> 00:54:58,244
I can choose to have copies equals one for redownloadable files while keeping
847
00:54:58,244 --> 00:55:01,680
replicas on important data. A godsend in this economy.
848
00:55:02,005 --> 00:55:02,914
No kidding.
849
00:55:02,914 --> 00:55:04,205
Look at you getting clever.
850
00:55:04,374 --> 00:55:06,904
I wouldn't mind a follow-up in a little while to know how it's going.
851
00:55:07,684 --> 00:55:10,904
I mean, we're two years in on one of our systems running BcacheFS.
852
00:55:11,357 --> 00:55:14,404
A couple of major upgrades in there. You're how many years in now on that sucker?
853
00:55:14,404 --> 00:55:15,144
Two and a half, three.
854
00:55:15,144 --> 00:55:18,164
Woo! And that system gets worked out.
855
00:55:18,164 --> 00:55:18,644
It does.
856
00:55:18,644 --> 00:55:20,347
Thank you, IRU. Appreciate you.
857
00:55:22,403 --> 00:55:27,018
Well, Gene Bean sent a collection of Rosa Ducks and Leet Sats.
858
00:55:28,632 --> 00:55:33,514
That's a total of 7,340 sats. Thanks, Gene. Let's go through them.
859
00:55:34,253 --> 00:55:36,416
Number one, this episode was fun.
860
00:55:36,799 --> 00:55:38,223
Well, we appreciate it. That's the goal.
861
00:55:38,223 --> 00:55:41,693
We weren't sure if the Reverso episode would be horrible or not.
862
00:55:42,232 --> 00:55:43,693
It confused us, so we couldn't tell.
863
00:55:43,693 --> 00:55:47,863
Yeah, it was a surprisingly hard episode for us to do just because it took constant
864
00:55:47,863 --> 00:55:51,013
mental effort to remember how to do the show backwards. It was silly.
865
00:55:52,293 --> 00:55:54,133
It was like doing the math every each segment.
866
00:55:54,133 --> 00:55:57,953
Nearly 13 years of doing it one way. It was awesome.
867
00:55:58,053 --> 00:55:58,613
Yeah.
868
00:56:00,060 --> 00:56:03,813
Note how we're not doing this episode backwards. Gene continues,
869
00:56:03,813 --> 00:56:06,973
I really like local send. Yeah. So that's another plus one there.
870
00:56:06,973 --> 00:56:07,473
Thanks, Gene.
871
00:56:07,473 --> 00:56:10,770
I'm really interested to see where buzz goes. Sounds really great.
872
00:56:11,891 --> 00:56:17,773
As a follow-up, it's a paid Slack that I want to connect an agent to.
873
00:56:17,773 --> 00:56:20,504
This is a follow-up to a question from last week.
874
00:56:21,853 --> 00:56:25,033
And then I like this one Brent why in God's name would you want 18 windows of
875
00:56:25,033 --> 00:56:28,834
the same app how the heck do you find anything this is our point Gene.
876
00:56:29,030 --> 00:56:31,213
You're making a presumption that he does find anything.
877
00:56:31,213 --> 00:56:32,033
That's the thing Gene.
878
00:56:32,633 --> 00:56:37,583
That's also quite a strong presumption I would say I have put in tools to try
879
00:56:37,583 --> 00:56:40,392
to help myself here and it has not completely succeeded.
880
00:56:41,551 --> 00:56:43,853
Okay maybe give us a follow up on that down the.
881
00:56:43,853 --> 00:56:47,553
Line we're just gonna leave that one right there we'll do an episode at some
882
00:56:47,553 --> 00:56:52,157
point A Dajabusan with 4,747 cents.
883
00:56:54,403 --> 00:56:57,961
Every time I hear the break song, it scratches my show tune itch.
884
00:56:57,961 --> 00:56:58,381
Oh, thank you.
885
00:56:58,381 --> 00:57:01,409
But then replaces it with another itch of needing JB the musical.
886
00:57:01,537 --> 00:57:04,631
You know, like those old sitcoms that would have a random musical episode.
887
00:57:04,631 --> 00:57:06,291
JB the musical?
888
00:57:06,291 --> 00:57:07,146
No.
889
00:57:07,603 --> 00:57:10,731
I don't know about that. Maybe one day we'll put together an album.
890
00:57:11,251 --> 00:57:16,061
I just, you know, if they're just, you know, I don't know. I guess, I don't know.
891
00:57:16,061 --> 00:57:19,351
Send in your booths to vote for the album being released this year.
892
00:57:19,351 --> 00:57:23,386
Yeah, I don't know about that. All right. Okay. All right. Maybe one day. Maybe one day.
893
00:57:23,949 --> 00:57:27,631
I'm going to say Ensign Nginx. What do you think? Ensign Nginx?
894
00:57:27,631 --> 00:57:28,872
Ensign Nginx. Oh, there you go.
895
00:57:29,110 --> 00:57:32,674
Ensign Nginx comes in with a row of ducks, $2,222.
896
00:57:33,852 --> 00:57:37,475
The Rust project leader has adopted an LLM policy that I completely agree with.
897
00:57:38,291 --> 00:57:41,291
If we were to rely on LLM to write code, it will eventually become dependency,
898
00:57:41,291 --> 00:57:44,754
and we risk not understanding what has been created.
899
00:57:45,531 --> 00:57:47,551
So, did you read the Rust LLM policy?
900
00:57:47,871 --> 00:57:48,751
I have not checked it out yet.
901
00:57:48,751 --> 00:57:49,131
Neither have I.
902
00:57:49,471 --> 00:57:50,351
But I will have to.
903
00:57:50,351 --> 00:57:55,651
The people who review, yeah, I think it's the, I think it, I mean,
904
00:57:55,651 --> 00:57:57,971
the high level here looks like you got to understand what you posted.
905
00:57:57,971 --> 00:58:00,259
You got to be responsible for what you committed, that kind of stuff.
906
00:58:00,642 --> 00:58:01,871
But I will try to read it after the show.
907
00:58:01,871 --> 00:58:02,961
Yeah. Thanks for boosting in.
908
00:58:02,961 --> 00:58:07,097
Yes. Thank you very much. I have that tab open now and I don't have crazy amounts of tabs.
909
00:58:08,126 --> 00:58:08,614
Hey.
910
00:58:08,787 --> 00:58:12,630
Well, I do have a lot of tabs actually. I do have quite a bit of tabs, but I have it open.
911
00:58:12,809 --> 00:58:14,681
And probably a lot of them you can close after the show.
912
00:58:14,681 --> 00:58:15,780
I will, but not that one.
913
00:58:16,171 --> 00:58:17,401
Do you pin some of them?
914
00:58:17,795 --> 00:58:19,229
I have a bunch of pin tabs.
915
00:58:20,291 --> 00:58:20,911
I don't do that.
916
00:58:20,911 --> 00:58:22,880
No you don't you definitely don't pin your tabs,
917
00:58:30,955 --> 00:58:35,250
A Monday comes in with 19,941 Satoshis.
918
00:58:36,092 --> 00:58:40,005
I would absolutely love a security camera deep dive. On the cusp of doing that
919
00:58:40,005 --> 00:58:41,505
myself, just finally got a Reolink
920
00:58:41,505 --> 00:58:44,765
doorbell cam and integrated into Home Assistant, and that's awesome.
921
00:58:44,765 --> 00:58:45,645
Nicely done.
922
00:58:45,645 --> 00:58:49,345
That's amazing. Also very much enjoyed the reverse episode. It was fun. P.S.
923
00:58:49,745 --> 00:58:51,905
X5 for a zip code. Oh, okay.
924
00:58:51,905 --> 00:58:55,825
Whoa, another zip code, and this one. Okay, so Wes, you got to do a little math.
925
00:58:55,825 --> 00:58:57,431
Did I bring my calculator today?
926
00:58:58,665 --> 00:58:59,055
So yes.
927
00:58:59,055 --> 00:59:00,775
So multiplied by five, is that right?
928
00:59:00,775 --> 00:59:03,925
I am very much considering going over my multi-frigate camera setup.
929
00:59:03,925 --> 00:59:07,375
So if people have any questions and I get a few of those, I'll definitely do an episode on it.
930
00:59:08,745 --> 00:59:10,760
Wes, I think you have to solve for X actually on this one.
931
00:59:10,922 --> 00:59:13,423
Oh, well, I was just guessing. I thought.
932
00:59:13,887 --> 00:59:17,945
That's not going to work, Wes. That's not going to. That's not going to.
933
00:59:18,543 --> 00:59:24,429
Okay. So we had 19,941 multiplied by five.
934
00:59:24,592 --> 00:59:27,245
That's 99,705.
935
00:59:27,245 --> 00:59:28,045
Oh, that's a nice boost.
936
00:59:28,045 --> 00:59:33,875
What I'm finding on my map, it's a little old, but it would seem to be the city of North Pole, Alaska.
937
00:59:33,875 --> 00:59:36,045
Oh, really? Hello, Alaska.
938
00:59:36,105 --> 00:59:37,815
Where the county of Fairbanks, North Star Borough.
939
00:59:37,815 --> 00:59:38,373
I love that.
940
00:59:38,971 --> 00:59:43,195
I have questions. It's not actually the North Pole, but they call themselves?
941
00:59:43,195 --> 00:59:44,465
Can we get a history lesson?
942
00:59:45,045 --> 00:59:46,720
Sure. You're right. We need to know more.
943
00:59:46,894 --> 00:59:50,801
Night62 comes in with 12,000. Thank you for the boost. 12,345 sets.
944
00:59:54,655 --> 00:59:57,035
Boost might not always be a clear indicator of a popular topic.
945
00:59:57,035 --> 00:59:59,495
I often boost in just to say something, not because the episode sparked the
946
00:59:59,495 --> 01:00:02,615
topic. I enjoyed the buzz episode. Being ahead of future trends is good.
947
01:00:02,615 --> 01:00:06,295
Many of us are not vocal, but we trust your taste and enjoy quiet listening
948
01:00:06,295 --> 01:00:09,235
and learning. Thanks. Well, that's always good signal to hear too, right?
949
01:00:09,997 --> 01:00:10,415
Yeah.
950
01:00:11,070 --> 01:00:11,845
Thank you. Appreciate that.
951
01:00:11,845 --> 01:00:13,213
Keep doing what you're doing is what I heard.
952
01:00:15,673 --> 01:00:17,873
Yeah, we appreciate that. You want to take MG there?
953
01:00:18,513 --> 01:00:24,545
I'll take MG. GMG sends in a row of sticks, 11,111 sats.
954
01:00:27,975 --> 01:00:32,325
That reverse episode was fun. By the way, I've boosted the previous three shows,
955
01:00:32,325 --> 01:00:33,875
but I haven't heard those messages.
956
01:00:33,875 --> 01:00:34,065
What?
957
01:00:34,125 --> 01:00:39,445
I didn't say much other than appreciate you. So didn't need to make it into
958
01:00:39,445 --> 01:00:41,765
the show. I just wanted to make sure you guys are getting the support you need.
959
01:00:42,065 --> 01:00:45,595
If they're above 2,000 sats, they make it into the show. But if they're below
960
01:00:45,595 --> 01:00:48,515
2,000 sats, they will be included in the doc and we read them,
961
01:00:48,515 --> 01:00:50,550
but we don't read them out loud on the air. That might have been it.
962
01:00:51,107 --> 01:00:52,515
But if not, let us know.
963
01:00:52,515 --> 01:00:52,665
Yes.
964
01:00:52,785 --> 01:00:53,945
Because then something might be broken.
965
01:00:53,945 --> 01:00:57,173
Thank you, MG. That did make it in. So we appreciate you.
966
01:00:58,385 --> 01:00:59,805
Time for some Fiat boosts here.
967
01:00:59,965 --> 01:01:00,205
Let's do it.
968
01:01:00,205 --> 01:01:04,745
Yeah. Covered bridge cookies. A very old listener. 150 Fiat.
969
01:01:05,645 --> 01:01:06,145
Wow.
970
01:01:06,765 --> 01:01:07,384
All right.
971
01:01:08,760 --> 01:01:09,451
Yahoo.
972
01:01:12,660 --> 01:01:14,689
Covered Bridge Cookies, thank you very much.
973
01:01:15,349 --> 01:01:20,569
I was there for Stallman, Dot Cloud, Matt's GTX 960, Bacon, and more.
974
01:01:20,929 --> 01:01:23,300
You helped my IT career more than words convey.
975
01:01:23,719 --> 01:01:28,009
I since nuked that, now I apply DevOps and FOSS principles to our co-op bakery.
976
01:01:28,629 --> 01:01:30,169
Covered Bridge Cookies.
977
01:01:31,189 --> 01:01:32,826
Coveredbridgecookies.com.
978
01:01:33,424 --> 01:01:34,279
They look delicious.
979
01:01:34,279 --> 01:01:37,449
Look at this, wow. That's so cool.
980
01:01:37,449 --> 01:01:41,911
Coveredbridgecookies.com It looks like they probably do shipping too. Ginger Snaps.
981
01:01:42,567 --> 01:01:46,659
All right. Oh, maple shortbread. What's going on here, Brent?
982
01:01:46,659 --> 01:01:47,689
Oh, you got me.
983
01:01:49,469 --> 01:01:51,289
Mind if we mail you free cookies?
984
01:01:51,289 --> 01:01:52,239
No way, really?
985
01:01:52,239 --> 01:01:56,289
That's what it says there. I mean, that sounds awful.
986
01:01:56,289 --> 01:01:57,589
I don't think you should be doing that.
987
01:01:57,809 --> 01:02:00,498
Yeah, we definitely wouldn't want a sampling of some of those delicious cookies.
988
01:02:01,317 --> 01:02:05,171
The .cloud reference is deep and the GTX 960. Thank you very much.
989
01:02:05,566 --> 01:02:06,999
That's amazing. Appreciate that.
990
01:02:06,999 --> 01:02:07,689
Thanks for boosting in.
991
01:02:09,209 --> 01:02:12,929
It's a slight zip code boost because at least the website says they're baked
992
01:02:12,929 --> 01:02:21,529
in Vermont cool alright well the Sithy Penguin boosted well it didn't boost and fiat it in 10 fiats,
993
01:02:24,804 --> 01:02:28,262
This is different from leaving voicemails to the launch. Also,
994
01:02:28,914 --> 01:02:33,124
I'm going to need you to not do a reverse show again. I already questioned my
995
01:02:33,124 --> 01:02:36,153
sanity. I don't need it coming from my favorite Linux podcast.
996
01:02:36,861 --> 01:02:38,914
Just kidding. That was funny as hell.
997
01:02:39,354 --> 01:02:45,045
I mean, it was a little tough on the sanity. Senior Smile comes in with $5.
998
01:02:46,130 --> 01:02:49,306
Oops, I forgot my name on the Kubernetes and the kernels. Here,
999
01:02:49,741 --> 01:02:52,452
have a fiver. All right. Thank you, Smile. Appreciate you.
1000
01:02:52,916 --> 01:02:55,224
We got a free member boost from Anonymous. they're back. Chris,
1001
01:02:55,224 --> 01:02:58,704
I think I heard you do have I think you had a farm with some chickens.
1002
01:02:59,232 --> 01:03:02,194
I'm not sure if it's worth mentioning. I've been working, assisted of course,
1003
01:03:02,194 --> 01:03:05,734
although I am a professional dev, on an egg farm tracking system.
1004
01:03:05,734 --> 01:03:06,134
What?
1005
01:03:06,434 --> 01:03:06,994
Check it out.
1006
01:03:06,994 --> 01:03:08,034
Two in one episode.
1007
01:03:08,034 --> 01:03:08,804
Cluckwork.
1008
01:03:08,804 --> 01:03:10,034
Oh, I like the name.
1009
01:03:10,394 --> 01:03:13,874
This is a thing people are doing, guys. Yeah, I definitely have chickens.
1010
01:03:13,874 --> 01:03:17,052
There's demand. A little short description. Poultry farm management.
1011
01:03:17,824 --> 01:03:18,614
Look at this thing.
1012
01:03:18,614 --> 01:03:20,222
C-sharp type script.
1013
01:03:21,535 --> 01:03:23,740
All right, I got another thing to check out after the show.
1014
01:03:23,740 --> 01:03:24,480
How about that?
1015
01:03:24,480 --> 01:03:28,600
That is really something right there. You mentioned needing a Slack export tool.
1016
01:03:28,600 --> 01:03:31,940
You might try out Slack dump, which we'll put a link in the show notes.
1017
01:03:31,940 --> 01:03:36,210
When the CNCF almost lost its free Slack instance, they recommended this project
1018
01:03:36,210 --> 01:03:37,684
to teams as a way to preserve history.
1019
01:03:38,195 --> 01:03:42,293
I didn't end up using it because Slack backpedaled and kept sponsoring the plans, but it does seem nice.
1020
01:03:42,496 --> 01:03:48,360
Jumping off of Wes's idea, I put a full ButterFS multi-node sync plus load balancer app scheduler.
1021
01:03:48,760 --> 01:03:50,900
I think this is the idea for what to put in the kernel if you could.
1022
01:03:50,900 --> 01:03:55,860
Oh, oh, oh, right. Oh, now this is clever. Actually, let's just pick a must-have
1023
01:03:55,860 --> 01:03:58,750
subset of Kubernetes and put it all. You know, I bet there's a lot of people
1024
01:03:58,750 --> 01:04:00,160
that wouldn't mind some Kubernetes in the kernel.
1025
01:04:01,130 --> 01:04:03,740
K-K-8. No, that's horrible.
1026
01:04:03,740 --> 01:04:04,363
K-8's in your kernel.
1027
01:04:05,106 --> 01:04:07,682
That's horrible. Thank you, Anonymous. Nice to hear from you.
1028
01:04:08,316 --> 01:04:10,510
Paul Mumbabusin to say, back again.
1029
01:04:10,510 --> 01:04:10,980
Hello, Paul.
1030
01:04:11,300 --> 01:04:15,640
Wanted to make it clear that for audiobooks, I mostly buy them digitally from Libro.fm.
1031
01:04:15,640 --> 01:04:16,050
Good one.
1032
01:04:16,050 --> 01:04:18,820
I use their subscription to get a credit every month, which I can use to buy
1033
01:04:18,820 --> 01:04:23,206
an audiobook. you can use their app or download the DRM free mp3 or m4b.
1034
01:04:23,403 --> 01:04:26,990
Yeah that's a good one we should mention Libro FM so thank you for audiobooks.
1035
01:04:26,990 --> 01:04:28,384
Are also way cheaper this way.
1036
01:04:28,564 --> 01:04:33,000
I love audiobooks too for road trips I stack up audiobooks and podcasts unless
1037
01:04:33,000 --> 01:04:37,132
I'm driving with peeps and then these days I'm just going to make West Beat DJ,
1038
01:04:38,763 --> 01:04:43,260
however if you have music assistant you can actually just have your agent create
1039
01:04:43,260 --> 01:04:47,227
playlist for you so that's what I've been doing recently.
1040
01:04:48,893 --> 01:04:54,900
Night 62, member boosted in. Can I get a few more characters in these here? Web boost.
1041
01:04:55,560 --> 01:04:58,980
If not, is it permissible to add a pastebin link or something like that?
1042
01:04:58,980 --> 01:05:04,559
I don't really want to chunk up my comments or split them across multiple boosts.
1043
01:05:05,094 --> 01:05:10,360
I don't need to write a book. But even AI is having trouble reducing my thoughts to 300 characters.
1044
01:05:11,660 --> 01:05:14,800
You can always send us a boost and refer to an email. That's true.
1045
01:05:15,280 --> 01:05:18,200
The thing is, we do try to keep these moving. So that's why the length is an
1046
01:05:18,200 --> 01:05:20,626
issue. there, but you could always email it and let us know.
1047
01:05:21,340 --> 01:05:24,830
All right, Papa John comes in with a member boost. I think the anonymous members
1048
01:05:24,830 --> 01:05:27,130
assume their name will come through when they sign in with Memberful,
1049
01:05:27,130 --> 01:05:28,860
so they don't fill out their username field. Great show, guys.
1050
01:05:29,456 --> 01:05:32,340
Yeah, I don't know if I can bring that in without some additional approval,
1051
01:05:32,340 --> 01:05:35,754
but I do think maybe that is a thing. Good catch, Papa John.
1052
01:05:35,917 --> 01:05:40,140
Space Warlock comes in. The Reverso format wasn't for me.
1053
01:05:40,660 --> 01:05:41,190
I understand.
1054
01:05:41,190 --> 01:05:46,220
It wasn't bad content-wise. It felt like change for the sake of change rather than positive impact.
1055
01:05:47,056 --> 01:05:50,789
I like the idea of a SSH in the kernel. I can see a use for it.
1056
01:05:51,300 --> 01:05:54,690
I think it was, was it Brent's idea? How did it come up? It came up.
1057
01:05:54,690 --> 01:05:59,790
Are you blaming me now? Yeah. It came up from like, we were having a discussion
1058
01:05:59,790 --> 01:06:05,400
somehow of, on a topic and then it just sort of popped in my head. So I will take the blame.
1059
01:06:05,720 --> 01:06:09,630
And then we tried it. And I, it was surprisingly difficult to be honest.
1060
01:06:09,630 --> 01:06:12,220
It might be good. It might've been a good exercise for us to do just to put
1061
01:06:12,220 --> 01:06:14,490
us out of our comfort zone and push it a little bit.
1062
01:06:14,700 --> 01:06:15,772
Thank you for your patience.
1063
01:06:16,086 --> 01:06:19,440
Adversary 17's back with a member boost love the reverse episode i think it
1064
01:06:19,440 --> 01:06:22,500
broke all your brains a little except chris which just straight up broke entirely
1065
01:06:22,500 --> 01:06:29,153
i it was bad it was bad momentum thank you adversaries appreciate you.
1066
01:06:29,408 --> 01:06:35,289
Mohan comes in to say this episode started off with outro and ended with the intro it was backwards.
1067
01:06:35,713 --> 01:06:38,320
Yeah it was all leading up to that observation it was all.
1068
01:06:40,044 --> 01:06:43,439
Well, Gene Bean sent in a member's booth saying, give this a read.
1069
01:06:43,439 --> 01:06:47,323
Open Claw with Clawed Opus 4.6. Hacked a gym.
1070
01:06:47,600 --> 01:06:50,569
Oh, yeah. I heard about this. Yeah. Well, he found like the schedule.
1071
01:06:50,569 --> 01:06:54,699
He found like a way to kick people off the reservation list and bump their operator
1072
01:06:54,699 --> 01:06:55,949
up on the reservation list.
1073
01:06:56,289 --> 01:06:59,813
Those reservation systems are often not really well controlled at all.
1074
01:06:59,940 --> 01:07:03,058
Yeah. It's just beginning. Clanker versus clanker. Tell you what.
1075
01:07:03,429 --> 01:07:06,319
All right. Thank you, everybody who supported the show. When you hear a dynamic
1076
01:07:06,319 --> 01:07:08,879
ad, you know, that means we didn't make an ad deal. That means we're barely,
1077
01:07:08,879 --> 01:07:11,859
barely, barely, barely getting by. And if it wasn't for our members and our
1078
01:07:11,859 --> 01:07:13,263
boosters, we just wouldn't be making it.
1079
01:07:13,692 --> 01:07:15,639
And I want to say thank you to everybody who also streamed stats.
1080
01:07:15,639 --> 01:07:18,255
We didn't get as many this last episode for some reason.
1081
01:07:18,551 --> 01:07:23,541
Twelve of you streamed stats, and collectively you stacked 11,789 Satoshis.
1082
01:07:23,541 --> 01:07:25,999
Sometimes you're too confused to stream, and that's our fault.
1083
01:07:25,999 --> 01:07:29,929
That might happen, yeah. Maybe the stats stream reversed that episode and went to them. Who knows?
1084
01:07:30,306 --> 01:07:33,289
When you bring that together with our fiat boosts, and if we just price them
1085
01:07:33,289 --> 01:07:34,312
at the current stats value.
1086
01:07:34,666 --> 01:07:41,034
That brings our total for this episode, it's pretty great, to 847,041 satoshis.
1087
01:07:47,711 --> 01:07:50,568
Thank you, everybody who supported the show with a membership or a boost.
1088
01:07:50,568 --> 01:07:52,616
Boost.JupiterBroadcasting.com.
1089
01:07:52,970 --> 01:07:57,698
You know, we might even be at the 13-year mark, and it just feels like in so
1090
01:07:57,698 --> 01:08:02,748
many ways a massive future ahead of the show and so much we can dig into and
1091
01:08:02,748 --> 01:08:05,338
new shows we could launch and all kinds of stuff.
1092
01:08:05,338 --> 01:08:08,678
So we really do appreciate the support. Even if the ad market doesn't think
1093
01:08:08,678 --> 01:08:12,008
a little old Linux podcast is worth supporting, we appreciate that you do,
1094
01:08:12,008 --> 01:08:16,119
and you keep us going. And it means the world to us. It's all the difference.
1095
01:08:17,871 --> 01:08:23,891
All right, we got a couple of picks, as we do. I was surprised to see that you picked iDescriptor.
1096
01:08:24,095 --> 01:08:28,828
Well, I picked it for you. Because I know you have some iDevices around.
1097
01:08:28,828 --> 01:08:30,078
I do have some iDevices around.
1098
01:08:30,078 --> 01:08:34,398
So I thought maybe you would like an AGPL 3.0 free open source cross-platform
1099
01:08:34,398 --> 01:08:38,558
iDevice management tool. And it just stood out because it's not all the time
1100
01:08:38,558 --> 01:08:40,226
that things like this run on Linux.
1101
01:08:40,458 --> 01:08:43,318
That is true. And also, it's cross-platform. So if you're on Windows,
1102
01:08:43,978 --> 01:08:46,595
you could do that. It's developed with Qt and...
1103
01:08:48,279 --> 01:08:48,883
A little bit of rust.
1104
01:08:48,883 --> 01:08:52,267
Oh, look at that. And C++, look at that.
1105
01:08:52,476 --> 01:08:56,983
Too. I guess I would say if you're familiar with iPhone management that you
1106
01:08:56,983 --> 01:08:59,903
used to get on Macs for a while that was built into iTunes and then later built
1107
01:08:59,903 --> 01:09:01,953
into Finder, it's kind of like that.
1108
01:09:01,953 --> 01:09:05,883
You get the information about your iPhone, the storage information.
1109
01:09:05,883 --> 01:09:09,958
You can browse the files, the apps that are on there, and you can do it over USB or Wi-Fi.
1110
01:09:10,132 --> 01:09:11,613
It has AirPlay. Wow.
1111
01:09:11,613 --> 01:09:18,343
Yeah. iDispatcher. iDispatcher. It really is the missing piece of iPhone management.
1112
01:09:19,823 --> 01:09:23,793
If you like to do this kind of stuff from the desktop, I think it's really cool.
1113
01:09:23,793 --> 01:09:27,063
Also, if you go the jailbroken route, it also gives you a few extra options.
1114
01:09:28,145 --> 01:09:34,072
If you did that kind of thing. iDescriptor, yeah. And like you said, it's AGPL 3.0.
1115
01:09:35,559 --> 01:09:39,323
All right, boys. Now, I would like to present you something that I think is
1116
01:09:39,323 --> 01:09:41,189
particularly interesting. And Brentley.
1117
01:09:43,987 --> 01:09:50,533
This might be worth the consideration of a pivot if i were not two three years
1118
01:09:50,533 --> 01:09:56,147
however long four years into obsidian i may consider kiwi fs,
1119
01:09:57,413 --> 01:10:00,313
and so i want to mention it and i'd also like to know if anybody could take
1120
01:10:00,313 --> 01:10:04,233
a peek at it and tell us if it's something we should review kiwi fs is a searchable
1121
01:10:04,233 --> 01:10:06,108
structured version markdown system,
1122
01:10:06,724 --> 01:10:11,603
and you can plug an agent into it in 30 seconds KiwiFS makes Markdown files
1123
01:10:11,603 --> 01:10:14,563
writeable, searchable, queryable, versioned, and human readable.
1124
01:10:14,563 --> 01:10:18,413
They are the source of truth, and everything else is a derivative index of your
1125
01:10:18,413 --> 01:10:20,191
Markdown files that you can build.
1126
01:10:20,615 --> 01:10:25,933
And KiwiFS basically becomes a file system and a wiki for your AI agents as well.
1127
01:10:26,536 --> 01:10:29,293
AI agents can read and write the same knowledge base humans use.
1128
01:10:29,293 --> 01:10:34,147
You can use an MCP, an API, WebDAV, Fuse, all kinds of options.
1129
01:10:34,861 --> 01:10:37,963
It's Obsidian-style Markdown knowledge management but designed to be shared
1130
01:10:37,963 --> 01:10:41,322
with agents and automation. It's self-hostable. It's a single Go binary.
1131
01:10:43,626 --> 01:10:47,457
And they pitch it as a Markdown file system for you and your agents working together.
1132
01:10:49,442 --> 01:10:49,883
Huh.
1133
01:10:49,998 --> 01:10:52,749
And I've thought about this, too. Like, say you get a document,
1134
01:10:52,749 --> 01:10:56,609
say you get like a PDF for the van or you get a receipt like you want to be
1135
01:10:56,609 --> 01:10:59,399
able to just give it to the agent. And then two years later,
1136
01:10:59,399 --> 01:11:04,783
say, hey, I need that receipt from O'Reilly's that was in August of 2026. Right.
1137
01:11:05,189 --> 01:11:09,009
That's what I want. And that's what this is. This is that's one of the things
1138
01:11:09,009 --> 01:11:14,109
along with notes, because it uses three tiers of indexing. So it can be really light.
1139
01:11:14,869 --> 01:11:18,279
You can just use grep. Then you can graduate up to something that's called like
1140
01:11:18,279 --> 01:11:23,579
the BM25 algorithm. You might know more. I don't know what. And then you can also go to vector.
1141
01:11:23,579 --> 01:11:27,019
Yep. Full text plus vector. And then you can kind of have it combined across
1142
01:11:27,019 --> 01:11:29,861
different methods to sort of do a ranked final delivery.
1143
01:11:30,737 --> 01:11:35,389
And you can have a pretty advanced backend that's using object storage and NFS and all this stuff.
1144
01:11:35,769 --> 01:11:37,209
Get versioning built in. I like that.
1145
01:11:38,794 --> 01:11:41,883
Yeah. Yeah, so I think if I hadn't gone down the Obsidian path,
1146
01:11:42,649 --> 01:11:44,269
I'd probably have deployed this this week.
1147
01:11:44,425 --> 01:11:48,859
The other thing that is nice to see is they clearly have a concept of importers
1148
01:11:48,859 --> 01:11:51,429
because they say they have 19 data importers, including Pay,
1149
01:11:51,429 --> 01:11:57,845
Postgres, Notions, Obsidian, CSV, which perhaps also tells you you could wire in your own converter.
1150
01:11:58,037 --> 01:12:01,793
There's an interface for it. It's set up to have multiple of those already, which could be handy.
1151
01:12:02,158 --> 01:12:06,049
I like the versioning built in. That's really nice. The search stuff looks really
1152
01:12:06,049 --> 01:12:10,216
good. The MCP, a lot of these things have that now, but they built that from the very beginning.
1153
01:12:11,626 --> 01:12:14,869
Yeah, I don't know. I mean, I think KiwiFS looks really good.
1154
01:12:14,869 --> 01:12:17,977
I don't know if it's worth replacing something you already have.
1155
01:12:18,401 --> 01:12:21,869
It also could be a bit of a memory system for your agent. So you and your agents
1156
01:12:21,869 --> 01:12:26,479
are kind of working from the same memory system. Think about that for a moment. And it's...
1157
01:12:26,669 --> 01:12:26,964
How did...
1158
01:12:28,219 --> 01:12:31,527
How did you know I was, like, diving into these tools and I wasn't happy with
1159
01:12:31,527 --> 01:12:33,125
anything that I've been finding recently?
1160
01:12:33,627 --> 01:12:35,782
Because you've been doing that since we met you?
1161
01:12:36,587 --> 01:12:37,327
Yeah, that's true.
1162
01:12:37,327 --> 01:12:39,917
That's true. That's true, yeah. The project is new, I should warn you.
1163
01:12:39,917 --> 01:12:44,667
It is new. It started in April of 2026, but it's already, I mean,
1164
01:12:45,007 --> 01:12:48,717
it's got 600 GitHub stars. It's under Active Contributors in Development.
1165
01:12:48,717 --> 01:12:50,995
They've really got, they've moved something. They got something quick, so.
1166
01:12:51,350 --> 01:12:53,717
It is apparently a business source license.
1167
01:12:53,717 --> 01:12:54,067
Yeah.
1168
01:12:54,067 --> 01:12:57,407
So it's free to use, self-host, and modify. the only restriction you can't offer
1169
01:12:57,407 --> 01:12:59,567
QEFS as a commercial hosted service.
1170
01:12:59,567 --> 01:12:59,813
Right.
1171
01:13:00,091 --> 01:13:03,007
Each release does convert to Apache 2 after four years.
1172
01:13:03,007 --> 01:13:04,067
Oh, interesting.
1173
01:13:04,067 --> 01:13:05,367
Just know that going on if you are going to use it.
1174
01:13:05,367 --> 01:13:09,793
Okay. See, there's a lot to like, right? And Markdown is always the source of truth.
1175
01:13:10,999 --> 01:13:16,479
I've been looking at, um, well, many of the suggestions from listeners recently,
1176
01:13:16,984 --> 01:13:21,275
but, uh, Joplin made it into my list as well.
1177
01:13:21,275 --> 01:13:26,265
And they have, uh, seemingly quite, um, you said you're shaking your head,
1178
01:13:26,265 --> 01:13:28,805
but I, I, I'm only mentioning it. I'm not using it.
1179
01:13:28,825 --> 01:13:31,975
It's just, I've been down the same path too. I've been, it's like.
1180
01:13:31,975 --> 01:13:33,885
And I was thinking you would say that exactly.
1181
01:13:35,665 --> 01:13:36,055
The reason.
1182
01:13:36,055 --> 01:13:39,095
I bring it up is only because they seem to have a.
1183
01:13:39,095 --> 01:13:40,025
Lot of like.
1184
01:13:40,325 --> 01:13:41,625
Some of the agent tools as well.
1185
01:13:41,945 --> 01:13:42,795
So it's curious.
1186
01:13:42,795 --> 01:13:44,585
To see these note-taking apps go in that.
1187
01:13:44,585 --> 01:13:47,105
Direction you're either going to fall back from you're either going to fall
1188
01:13:47,105 --> 01:13:50,815
back to obsidian or you're going to try to give qo notes an earnest try that's
1189
01:13:50,815 --> 01:13:56,015
your next no i did that a long time i'm never no you'll you'll think about it
1190
01:13:56,015 --> 01:13:59,365
you'll be like actually no no no qo notes is just the way i should go here.
1191
01:13:59,365 --> 01:14:01,535
We go uh he's a big git guy.
1192
01:14:01,535 --> 01:14:02,835
Right well so brian.
1193
01:14:02,835 --> 01:14:07,949
In matrix is saying i've just been using my forgeo repo to store all my documentation for my agents.
1194
01:14:08,529 --> 01:14:12,725
There you go simple although you know if it ever gets too big that you know
1195
01:14:12,725 --> 01:14:15,985
there it would be nice to be able to vector that or something like that all
1196
01:14:15,985 --> 01:14:20,447
right you know what we do we put links to all this stuff linuxunplugged.com slash 680,
1197
01:14:21,097 --> 01:14:24,595
and then there's the whole network over jupiterbroadcasting.com as long as that
1198
01:14:24,595 --> 01:14:27,585
uh It steals on going. You can find the links over there for all the other shows.
1199
01:14:27,585 --> 01:14:29,575
Yeah, the incredible community-powered website.
1200
01:14:29,575 --> 01:14:32,445
Where are they going? Nowhere? As far as I know. Yeah, that is true.
1201
01:14:32,445 --> 01:14:34,106
That is still a great community-powered website.
1202
01:14:34,710 --> 01:14:37,775
And, of course, we've got boost.jupiterbroadcasting.com as well.
1203
01:14:38,263 --> 01:14:41,355
So here's the thing. If you want to really have some fun, you've got to show
1204
01:14:41,355 --> 01:14:45,095
up on a Sunday. You make it a Tuesday on a Sunday. You hang out with the boys.
1205
01:14:45,095 --> 01:14:47,799
You listen to or watch a little Linux Unplugged live.
1206
01:14:51,236 --> 01:14:54,682
Sundays, 10 a.m. Pacific, 1 p.m. Eastern, your time at jibiterbroadcasting.com
1207
01:14:54,682 --> 01:14:59,012
slash calendar. Now, for the download itself, in your RSS feed, we got some extra stuff.
1208
01:14:59,012 --> 01:15:01,722
We do, including, you're familiar with the MP3?
1209
01:15:01,722 --> 01:15:02,042
Yeah.
1210
01:15:02,042 --> 01:15:03,693
We provide an upgraded MP4.
1211
01:15:04,382 --> 01:15:05,872
You mean there's one extra MP? In the feed?
1212
01:15:05,872 --> 01:15:06,402
That's right, yes.
1213
01:15:06,402 --> 01:15:07,322
Just sitting there in the feed?
1214
01:15:07,322 --> 01:15:08,072
Right in the feed.
1215
01:15:08,072 --> 01:15:08,502
Wow.
1216
01:15:08,502 --> 01:15:10,512
Right next to the e-transcription files.
1217
01:15:10,512 --> 01:15:10,662
What?
1218
01:15:10,662 --> 01:15:13,196
Including, you know, ones that say who's talking to who.
1219
01:15:13,347 --> 01:15:15,712
Do you have any kind of, like, structured data my agent could use?
1220
01:15:15,712 --> 01:15:19,412
Oh, yeah. Like a JSON file that has cloud chapters in it.
1221
01:15:19,412 --> 01:15:21,787
Maybe you have years worth of episodes that have all of that.
1222
01:15:22,008 --> 01:15:25,922
Yeah, not every episode, and different ones got different parts at different times.
1223
01:15:25,922 --> 01:15:26,594
Getting better and better.
1224
01:15:27,202 --> 01:15:28,382
Getting better and richer all the time.
1225
01:15:28,382 --> 01:15:32,312
There you have it. All right. Thank you very much. I could tell you more.
1226
01:15:32,614 --> 01:15:35,122
I'll just leave it with this. Thank you to our mumble room for hanging out with
1227
01:15:35,122 --> 01:15:39,040
us. Thank you to the folks in the live chat, our members, our boosters,
1228
01:15:39,295 --> 01:15:41,564
and thank you for downloading and listening to this episode.
1229
01:15:41,953 --> 01:15:43,872
And I don't say it enough, but for those of you who have been listening for
1230
01:15:43,872 --> 01:15:47,073
a long time, we deeply appreciate you. We really do.
1231
01:15:47,427 --> 01:15:50,132
Thank you for hanging with us through all the ups and downs and changes.
1232
01:15:50,132 --> 01:15:52,952
Well, it's all ups, of course. Through all the ups and ups.
1233
01:15:52,952 --> 01:15:54,474
The ups and slightly less ups.
1234
01:15:54,660 --> 01:15:57,353
Yeah, that's it right there. Thank you.
1235
01:15:58,601 --> 01:16:01,167
And also, thank you for joining us on this particular episode.
1236
01:16:01,649 --> 01:16:04,092
And we'll see you back here for next week's particular episode,
1237
01:16:04,092 --> 01:16:06,775
which will not be in reverse, all right? We're done with that.
1238
01:16:07,564 --> 01:16:09,509
It's going to be in regular order. We'll see you next week.