WEBVTT

00:00.000 --> 00:09.460
This is dedicated to all the hackers and the crackers, to the hackers and the crackers.

00:09.860 --> 00:15.520
I see in binary, I speak source code, step on my toes, I'll post a million jpegs of you

00:15.520 --> 00:16.460
in a fag pose.

00:16.720 --> 00:21.640
In your digital stance, getting firewalled ho, cause I'm riding the net in my six-fold.

00:21.900 --> 00:26.440
I was a dick with my 56, now with my cable I'm able to get that stable.

00:26.440 --> 00:32.460
On the out, my name is Ace and I'm a Leo. On the digital highway, my name is Neo and I'm a hero.

00:32.680 --> 00:38.360
In a flash, I'll sue you on burning Dreamcast. You need some ISO? Let me through my hard drive rifle.

00:38.700 --> 00:43.520
Our exchange you could never stifle. In a digital hug, you just caught the love bug.

00:43.840 --> 00:47.540
I bootlegged your CD, I caused a fight between Un and Jay-Z.

00:47.880 --> 00:52.100
Your CG, it's all gonna be free, whether we take it by force or we take it nicely.

00:52.200 --> 00:56.280
You feel that rattling your bones when I tell you we just hacked out Jones?

00:56.440 --> 01:00.720
And NASDAQ leaves your fight on your back, cause I am he who loves to hack and crack.

01:00.960 --> 01:03.500
Cause I am he who loves to hack and crack.

01:03.920 --> 01:06.600
This is dedicated to the hackers and the crickets.

01:07.060 --> 01:11.700
Serial codes, source codes, ISOs, RAMs, SIPs, SISs.

01:11.940 --> 01:14.200
This is dedicated to the hackers and crack.

01:14.200 --> 01:23.500
Hello everybody and welcome to Binary Revolution Radio episode number 183, I think.

01:23.660 --> 01:28.740
I have to actually check here and make sure because I have been away from the show for a little while.

01:28.840 --> 01:34.900
But I am back this week joining a co-host who's been on more frequently than me, I think, this season.

01:35.220 --> 01:37.000
Savant is with us on the show again this week.

01:37.560 --> 01:38.040
How you doing?

01:38.580 --> 01:42.720
And let's see, today's date is January 23rd, 2007.

01:43.320 --> 01:45.920
Hey, I think this is the first show I've done for 2007.

01:46.800 --> 01:47.120
You're welcome.

01:47.120 --> 01:51.340
So, we are going to jump right into some housekeeping.

01:51.700 --> 01:55.920
Not gonna mess around or any of that kind of good stuff, cause we got a lot of housekeeping to do.

01:56.340 --> 01:57.600
A little bit of email to do.

01:57.760 --> 02:00.880
And we have a pretty long topic to talk about later on.

02:00.880 --> 02:04.060
So, let's take care of some housekeeping.

02:05.300 --> 02:09.140
I'll go ahead and knock a few things out first, cause I've got quite a few little things to talk about.

02:09.220 --> 02:10.320
I'll try to keep them brief.

02:11.720 --> 02:16.860
First of all, I have to announce that I owned myself in IRC earlier this week.

02:17.880 --> 02:20.720
So, in front of only one witness, but you know what?

02:20.840 --> 02:21.700
Doesn't really matter.

02:21.960 --> 02:23.220
Next Gen busted me.

02:23.300 --> 02:24.680
He was the only other person in the channel.

02:24.680 --> 02:30.320
I accidentally did a cut and paste of the old slash identify, or slash chan serve identify.

02:30.680 --> 02:32.440
So, the password was thrown right out there.

02:32.620 --> 02:33.420
So, yeah.

02:34.140 --> 02:35.520
Kind of fucked that one up a little bit.

02:36.380 --> 02:36.920
You know what?

02:36.940 --> 02:37.440
Did you recover?

02:38.020 --> 02:38.280
Huh?

02:38.340 --> 02:38.660
Oh, yeah.

02:38.680 --> 02:40.440
I immediately changed the passwords, of course.

02:40.560 --> 02:41.420
But it was pretty stupid.

02:41.520 --> 02:42.700
I could have gotten owned even worse.

02:42.880 --> 02:43.540
But, you know.

02:44.160 --> 02:44.920
Shit happens.

02:44.960 --> 02:45.460
What are you gonna do?

02:45.520 --> 02:47.380
Everybody has a little finger fuck once in a while.

02:47.500 --> 02:47.900
Oh, wait a minute.

02:47.940 --> 02:48.780
That sounded...

02:48.780 --> 02:51.160
That's gonna end up in a remix somewhere, too, isn't it?

02:51.800 --> 02:54.080
We really ought to formalize a remix contest.

02:54.080 --> 02:54.480
Yeah.

02:54.480 --> 02:55.420
If you guys are up for it.

02:55.540 --> 02:56.500
Maybe at some point.

02:56.600 --> 02:57.360
I just...

02:57.360 --> 02:58.620
There's just so much material.

02:58.760 --> 03:00.000
I keep screwing everything up.

03:00.520 --> 03:02.740
So many out of context comments.

03:03.900 --> 03:04.820
Oh, it's all good.

03:05.560 --> 03:06.340
So, yeah.

03:06.440 --> 03:07.480
I kind of screwed that up.

03:07.500 --> 03:07.780
But, hey.

03:07.820 --> 03:08.340
What are you gonna do?

03:08.420 --> 03:09.320
Move on with life.

03:09.620 --> 03:10.700
And, of course, everybody...

03:10.700 --> 03:14.620
Well, actually, only one person actually got my password.

03:14.740 --> 03:21.740
So, I gotta give some initial shouts out to Eyeball, who actually got the joke that one of my passwords was,

03:21.740 --> 03:26.160
or the reference to what one of my passwords was referring to.

03:26.240 --> 03:27.080
That made no sense.

03:27.760 --> 03:28.160
But, anyway.

03:29.240 --> 03:34.200
And my Uber IRC password, which was literally Uber IRC password.

03:34.200 --> 03:37.040
So, that was pretty funny, too.

03:37.640 --> 03:39.280
One, two, three, four, five.

03:39.440 --> 03:41.220
That's the same combination I have in my luggage.

03:41.920 --> 03:42.280
Exactly.

03:44.480 --> 03:48.460
Well, because they kept breaking into it when I had my birthday on it, so...

03:48.460 --> 03:49.220
Well, let's see.

03:49.320 --> 03:51.160
What else for housekeeping?

03:51.660 --> 03:52.420
I'm not...

03:52.420 --> 03:55.400
I've talked about this off and on over the past few weeks.

03:55.460 --> 04:00.980
I'm sure Ratchet has passed a little information on as well about the server and its stability.

04:01.800 --> 04:03.300
That's a tough word to say on the radio.

04:03.440 --> 04:04.260
Server stability.

04:05.600 --> 04:09.500
We seem to have it under control now, as far as we can tell.

04:09.500 --> 04:17.440
Well, I'm not going to rehash it over and over again because, well, it was just a really tricky situation.

04:18.260 --> 04:22.500
I appreciate everybody's help and a lot of people offering suggestions and ideas and whatnot,

04:22.700 --> 04:26.220
but it's really hard to do when you're not actually seeing what we're seeing.

04:26.220 --> 04:31.080
A lot of the suggestions coming in are just not appropriate because they just don't fit,

04:31.200 --> 04:35.120
or they're things we've already done, or they're things that just are irrelevant to what's going on.

04:35.720 --> 04:39.020
But just to dispel a couple of myths or rumors that I saw quite a bit,

04:39.500 --> 04:41.520
it doesn't really help.

04:42.360 --> 04:43.540
A few people suggested...

04:43.540 --> 04:44.720
Hold on, I've got to have some iced tea here.

04:45.040 --> 04:46.620
I'm new to this radio thing, apparently.

04:48.340 --> 04:50.840
I've got a few suggestions of people saying,

04:50.840 --> 04:53.280
why don't we delete some of the older posts out of the forum

04:53.280 --> 04:58.540
or remove some of the users who haven't finished authenticating yet.

04:59.300 --> 05:01.440
It doesn't really matter how many users are there

05:01.440 --> 05:05.400
or how many records there are in the database or any of that kind of stuff.

05:05.400 --> 05:07.740
Not on this small of a scale that we are right now.

05:07.740 --> 05:13.920
So we can delete all the old threads or migrate them off to a backup or something like that.

05:14.200 --> 05:16.000
It's going to make a negligible difference.

05:16.460 --> 05:20.440
If the indexes are created properly, it's going to find everything just as fast

05:20.440 --> 05:25.120
with such a small number of records and the hundreds of thousands of posts and stuff that we have.

05:25.420 --> 05:26.960
It's just not going to make a difference at all.

05:27.020 --> 05:28.000
That's not the way to go.

05:28.100 --> 05:29.680
That's really not the solution.

05:29.680 --> 05:37.180
The suggestion some people made of changing from Apache to some other,

05:37.360 --> 05:41.600
it was one I saw quite a bit, tiny web server.

05:41.740 --> 05:43.220
I don't remember what it was exactly.

05:44.280 --> 05:46.960
Switching web servers is not exactly something that's easy to do.

05:47.060 --> 05:48.420
There's a whole lot of reconfiguring.

05:48.520 --> 05:49.500
It would take us more time.

05:50.060 --> 05:52.920
Again, it wasn't really Apache that was the problem per se.

05:53.540 --> 05:56.660
The long and short of it was that we didn't have enough memory anymore.

05:57.180 --> 05:58.900
We simply had outgrown the box.

05:59.520 --> 06:02.700
And we kind of sort of knew that and suspected that and we did see it coming.

06:03.020 --> 06:04.840
It seemed to happen real suddenly, though.

06:04.900 --> 06:05.700
That's the thing.

06:05.840 --> 06:08.840
I guess it just finally hit its breaking point where it started giving up.

06:09.640 --> 06:13.260
And we were trying to tweak it to make it work a little better.

06:13.260 --> 06:17.860
So we were trying to optimize MySQL in the way that it handles and uses memory.

06:18.160 --> 06:20.560
So that's really where the detail was getting down into.

06:20.660 --> 06:24.760
So we're talking about going in and tweaking a lot of the MySQL settings,

06:24.860 --> 06:27.320
a lot of the PHP settings and PHP INI,

06:27.420 --> 06:30.020
a lot of the Apache settings and HTTP CONF.

06:30.440 --> 06:34.440
So we're going through all of these things trying to tweak minuscule little things

06:34.440 --> 06:37.340
just to try to make it use our memory a little bit more efficiently

06:37.340 --> 06:39.860
so that we would not have to upgrade.

06:39.860 --> 06:44.180
And no matter what we came up with and no matter how we tried to tweak it,

06:44.240 --> 06:47.700
the bottom line was it needed more memory than we were able to give it.

06:47.880 --> 06:48.320
That's it.

06:48.380 --> 06:49.020
End of story.

06:50.020 --> 06:52.840
So, you know, again, we appreciate the help.

06:52.920 --> 06:56.120
I know somebody had sent me a, I don't remember if it was an email or what it was,

06:56.160 --> 07:00.100
about how they admin 50 to 100 servers a day or something

07:00.100 --> 07:03.260
and how there's no reason six of us couldn't figure out or do this

07:03.260 --> 07:04.760
and we didn't know what we were doing or something.

07:05.080 --> 07:06.520
That's not the case at all.

07:06.520 --> 07:11.040
Well, I can admin 50 to 100 servers a day if they're all running smoothly

07:11.040 --> 07:12.160
and there's not really any problems.

07:12.260 --> 07:14.600
But when you get down to the point where you're trying to milk

07:14.600 --> 07:17.300
every last bit of performance out of your box,

07:17.660 --> 07:20.540
that's when you've got to spend time to try to get that thing under control.

07:20.860 --> 07:23.820
And we have, frankly, couldn't do that.

07:23.900 --> 07:26.740
We had to get more memory because that was the only thing that would solve the problem.

07:26.840 --> 07:28.800
So we've done that as a temporary solution.

07:29.480 --> 07:31.860
There will be a longer-term solution coming up.

07:31.860 --> 07:35.580
So we'll announce that when it happens or if and when it happens.

07:35.780 --> 07:38.620
But we've already alluded to it in the forums

07:38.620 --> 07:41.700
about how we're going to have to upgrade boxes to something more powerful

07:41.700 --> 07:44.620
because we're just outgrowing what we have.

07:44.740 --> 07:47.620
So we're trying to keep BinRev alive every way that we can.

07:47.840 --> 07:51.520
I'm trying not to completely turn into a beggar on the air.

07:51.880 --> 07:55.280
I know that's the running joke in IRC, the whole we'll hack for food

07:55.280 --> 08:01.100
or, you know, begging BinRev Photoshop with me holding a cardboard sign

08:01.100 --> 08:02.320
and that's all good and everything.

08:02.540 --> 08:03.120
I'm trying to avoid...

08:03.120 --> 08:03.880
That's so funny.

08:04.000 --> 08:04.900
I know, it was good.

08:05.960 --> 08:08.320
Honestly, I am trying to avoid going that far,

08:08.400 --> 08:11.760
but we're going to have to do something because, I mean, it's going to cost...

08:11.760 --> 08:15.360
Quite frankly, it's going to be about $300 out of my pocket more.

08:16.400 --> 08:18.180
And that adds up.

08:18.360 --> 08:20.980
You know, that's going to be about, what, $10 a day?

08:22.300 --> 08:23.140
Yeah, about that.

08:23.140 --> 08:25.600
That, just to give anybody listening, if you've ever wondered,

08:25.900 --> 08:29.060
it's going to cost about $10 a day to keep BinRev up and running.

08:29.720 --> 08:31.100
Just to give you a ballpark.

08:31.280 --> 08:32.900
So, you know, we're going to have...

08:32.900 --> 08:36.380
We'll try to put up some donation links or something from people who have offered to help,

08:36.440 --> 08:38.240
which we very, very much appreciate.

08:38.780 --> 08:41.460
Even if it's just a few bucks here and there, any little bit will help.

08:41.500 --> 08:43.220
And I'm doing exactly what I said I wasn't going to do,

08:43.260 --> 08:47.480
so I'm going to move on to the next topic, which is our forums upgrade.

08:48.380 --> 08:51.880
We finally got the server stable, so stable enough that we could actually go in

08:51.880 --> 08:55.860
and do some upgrading to the server, upgrading to the forums, I should say.

08:56.280 --> 08:59.520
So we have updated the forums as of a couple days ago.

08:59.600 --> 09:02.700
I think it was Sunday evening we did that, Sunday night.

09:02.900 --> 09:06.040
So forums are in place, so go check them out.

09:06.220 --> 09:08.460
And we are in the progress of skinning them.

09:09.620 --> 09:11.140
They changed the way...

09:11.140 --> 09:13.540
See, this is the one thing that kind of annoys me about Envision is

09:13.540 --> 09:16.840
even when they make their point upgrades,

09:16.840 --> 09:20.500
upgrades, they're changing the skins, the way the skins work and the design works.

09:20.560 --> 09:22.460
So the old skins that worked on the old versions

09:22.460 --> 09:25.520
do not migrate over and work successfully in the new version.

09:25.620 --> 09:28.720
So they all have to be tweaked, modified, rewritten, whatever the case may be.

09:29.340 --> 09:31.340
So that's kind of sucky on a point release,

09:31.540 --> 09:34.460
but they did add a lot of cool features in it,

09:34.520 --> 09:37.860
so at the same time it was really a bigger release than it may appear.

09:37.860 --> 09:41.480
So we are in the process of trying to tweak the graphics a little bit,

09:41.520 --> 09:43.900
make them look a little bit more hacker-ish, a little bit nicer,

09:44.340 --> 09:46.300
put the BinRev logo at the top of some of them.

09:46.980 --> 09:49.500
And we are doing that as we speak,

09:49.560 --> 09:53.880
and hopefully in the future we will get another custom theme back up and running,

09:53.960 --> 09:56.140
maybe fix our old custom theme and get it working.

09:57.560 --> 09:59.740
And finally in housekeeping this week,

09:59.920 --> 10:05.400
we have been working on one of our sites that was, I guess, neglected.

10:05.400 --> 10:07.840
It had fallen on hard times because there was no one to administer it.

10:08.460 --> 10:10.020
That was HackerEvents.org,

10:10.680 --> 10:13.780
which in my mind is really our first success story

10:13.780 --> 10:18.380
from the new projects forum that we created about a month or two ago.

10:19.020 --> 10:22.260
Got some volunteers, some people together who are willing to work on this.

10:22.760 --> 10:25.380
We've been meeting in IRC, which has worked out really well.

10:25.480 --> 10:27.360
We've had all five people be very active.

10:27.520 --> 10:29.340
We meet, talk about, discuss things.

10:29.440 --> 10:33.220
It's truly a group project, which is exactly what I love seeing

10:33.220 --> 10:35.320
and which is exactly what this community is about

10:35.320 --> 10:40.340
and exactly what I hoped would come out of creating that forum in the first place.

10:40.420 --> 10:42.900
So I'm very excited and happy to see something like this.

10:44.240 --> 10:49.320
We are in the process of adding lots of events to it day by day.

10:49.420 --> 10:51.260
Anybody who has any that they want to submit,

10:51.360 --> 10:54.860
like local events, Linux user groups, security groups,

10:54.980 --> 10:58.700
anything even remotely related that somebody might find interesting to the hacker community,

10:58.700 --> 11:03.560
add it there, and one of the admins will add it to the list and approve it.

11:04.680 --> 11:08.080
And I think they're going to be skinning it and making that look a little bit nicer as well.

11:08.160 --> 11:11.020
But for now, it's just running the calendar itself,

11:11.080 --> 11:14.300
and the content is, of course, most important.

11:14.300 --> 11:17.280
So that's it for my housekeeping.

11:17.540 --> 11:20.020
Now, Savant, while I take a breath here,

11:20.380 --> 11:24.380
I know you had a West Coast BINREV event you were going to talk about, right?

11:24.980 --> 11:25.260
Yep.

11:25.420 --> 11:26.220
Sip your iced tea, man.

11:26.240 --> 11:26.700
You've heard it.

11:27.040 --> 11:28.900
So West Coast BINREV,

11:28.960 --> 11:33.840
or the loosely collected affiliated BINREVers of us in California

11:33.840 --> 11:35.740
and other parts of the adjoining area,

11:36.000 --> 11:38.280
we're planning a trip to Disneyland in February.

11:38.680 --> 11:39.240
Hit your pens.

11:39.420 --> 11:39.840
I'll wait.

11:40.760 --> 11:41.140
All right.

11:41.140 --> 11:45.800
February 20, I want to say 24th and 25th,

11:46.040 --> 11:47.500
we're going to the Anaheim Disneyland.

11:48.520 --> 11:50.040
It's going to be pretty much an all-day thing.

11:50.400 --> 11:53.640
So far, confirmed are myself and Verbal and our lady friends

11:53.640 --> 11:56.800
and Strom and Generic and a couple other babies.

11:57.240 --> 11:58.280
So sign up.

11:58.400 --> 11:58.940
Come on in.

12:00.100 --> 12:01.360
I mean, if there's enough people together,

12:01.440 --> 12:03.200
then maybe we can find out about a group discount.

12:03.760 --> 12:05.600
Otherwise, yeah, try to make it down.

12:05.600 --> 12:10.220
We're also working on a special hotel afterparty, BYOL.

12:11.520 --> 12:13.240
Which is, of course, bring your own loop.

12:14.000 --> 12:14.820
Oh, okay.

12:14.980 --> 12:16.420
I had to ask about that one.

12:16.480 --> 12:18.380
I'm not into those, uh...

12:18.380 --> 12:19.740
I'm not sure about those kind of parties.

12:22.040 --> 12:23.960
You know, I've got to tell you,

12:23.980 --> 12:24.920
I'm kind of worried right now

12:24.920 --> 12:26.620
because the box that we're recording on,

12:26.740 --> 12:29.080
the fans kicked in pretty awful loud.

12:29.180 --> 12:31.020
It might even be picked up by the microphone.

12:31.140 --> 12:31.700
I'm not sure.

12:31.800 --> 12:34.540
So hopefully this thing doesn't die halfway through the recording here.

12:35.040 --> 12:36.560
No, it would be the lost episode.

12:36.680 --> 12:37.200
It might be sweet.

12:37.280 --> 12:37.880
Well, you know what?

12:38.000 --> 12:39.140
I'm such an ass,

12:39.140 --> 12:40.580
I'd probably just release it anyway.

12:42.380 --> 12:42.800
At this stage...

12:42.800 --> 12:43.940
Like, I don't know what you get, bitches.

12:44.020 --> 12:44.440
That's right.

12:44.460 --> 12:45.420
That's where you don't complain.

12:47.360 --> 12:48.160
Oh, man.

12:48.600 --> 12:49.140
Yeah, actually,

12:49.240 --> 12:51.120
we were going to try to get something together

12:51.120 --> 12:53.600
similar here at the BR-407,

12:53.680 --> 12:54.480
the Orlando meeting,

12:54.980 --> 12:56.880
because we also have a Disney X,

12:57.020 --> 12:58.360
Disney World down here,

12:58.960 --> 12:59.660
Disney blank.

13:00.380 --> 13:02.920
So we were thinking of at least getting together.

13:02.920 --> 13:05.540
Do you have something called a Downtown Disney

13:05.540 --> 13:06.420
or a Disney...

13:06.420 --> 13:07.100
What is it called?

13:08.560 --> 13:09.200
Disney Quest?

13:09.220 --> 13:10.020
Yeah, they've got the shops and shit.

13:10.480 --> 13:10.980
Yeah, yeah.

13:11.020 --> 13:11.960
It's just like a big kind of...

13:11.960 --> 13:13.100
It's like what Disney does,

13:13.140 --> 13:13.720
a strip mall.

13:14.400 --> 13:15.540
Yeah, totally a Disney mall.

13:15.740 --> 13:16.260
Absolutely, yeah.

13:16.260 --> 13:16.880
We've got those, too.

13:17.240 --> 13:18.980
And it's actually...

13:18.980 --> 13:21.020
It was an article that you had written a while back

13:21.020 --> 13:22.380
that actually inspired me to think,

13:22.440 --> 13:23.440
yeah, we should get a bunch of hackers

13:23.440 --> 13:24.080
to get a Disneyland.

13:24.440 --> 13:26.120
Was your War Driving with Mickey article.

13:26.660 --> 13:27.600
Yeah, that was nice.

13:27.600 --> 13:30.160
I thought that the spin of the Disneyland trip

13:30.160 --> 13:31.380
would be Hack Disneyland

13:31.380 --> 13:34.200
will have a bounty hunting contest

13:34.200 --> 13:36.180
where everybody there could come up

13:36.180 --> 13:36.980
with some sort of hack,

13:37.100 --> 13:38.600
like in the Carousel of Progress,

13:38.680 --> 13:39.800
there's all sorts of computers there

13:39.800 --> 13:40.440
that you can use.

13:41.340 --> 13:43.020
Some sort of hack that would be voted on

13:43.020 --> 13:44.840
and then depending on who executed it,

13:44.880 --> 13:46.200
it would be like a game of Hacker Horse

13:46.200 --> 13:48.980
or a scapger hunt of sorts.

13:49.440 --> 13:50.340
Hacker Horse?

13:50.880 --> 13:51.240
Yeah.

13:52.720 --> 13:53.080
Oh.

13:53.360 --> 13:54.640
Well, one of the things I wanted to do

13:54.640 --> 13:55.980
was go around and enumerate

13:55.980 --> 13:57.840
all of the payphones there for Yapple.

13:58.460 --> 13:58.820
Definitely.

13:59.100 --> 14:00.180
So that's another cool thing

14:00.180 --> 14:00.840
you might be able to do

14:00.840 --> 14:01.980
because you know there's always...

14:01.980 --> 14:02.680
At least for ours,

14:02.740 --> 14:03.940
there's always people there,

14:04.000 --> 14:05.120
even late into the evening.

14:05.660 --> 14:06.580
There's always people around,

14:06.700 --> 14:08.380
so if they accept incoming calls,

14:08.460 --> 14:09.960
you're always going to get somebody on there.

14:10.600 --> 14:10.900
Yep.

14:11.040 --> 14:12.040
So that could be fun.

14:12.620 --> 14:14.120
You could even do it in character voices

14:14.120 --> 14:14.720
or something like,

14:14.820 --> 14:15.620
Oh, Mickey!

14:15.920 --> 14:16.980
I'm going to kick your ass!

14:17.100 --> 14:17.700
Oh, boy!

14:18.900 --> 14:20.160
That was actually pretty good,

14:20.240 --> 14:20.920
I must say.

14:21.600 --> 14:22.380
Oh, thank you.

14:22.580 --> 14:23.140
That was almost...

14:23.140 --> 14:24.780
I've got the mouse hostage.

14:24.780 --> 14:27.000
That was almost as good as...

14:27.000 --> 14:30.420
almost as good as Rax's Kermit the Frog.

14:31.140 --> 14:31.980
Oh, shit.

14:32.040 --> 14:32.560
I hear that.

14:32.740 --> 14:33.440
Put those together.

14:33.820 --> 14:35.400
It's also a great place to social engineer

14:35.400 --> 14:37.020
because you've got all the employees working there

14:37.020 --> 14:38.000
and they're all Disney-fied.

14:38.060 --> 14:39.720
They have to smile and whatever,

14:39.900 --> 14:40.920
but you can kind of go in there

14:40.920 --> 14:42.260
and I won't say fuck with them,

14:42.280 --> 14:42.800
but you can go in there

14:42.800 --> 14:44.360
and try to weasel information out of them

14:44.360 --> 14:46.680
and they're trying to walk that tightrope

14:46.680 --> 14:47.440
into being nice

14:47.440 --> 14:48.760
and always answer your questions

14:48.760 --> 14:50.100
and the customer's always right.

14:50.420 --> 14:51.160
You might give them to get up,

14:51.160 --> 14:53.640
give up a little bit of information, yeah.

14:53.640 --> 14:55.080
Well, here's something.

14:55.660 --> 14:56.480
To get...

14:56.480 --> 14:57.460
Now, disabled people

14:57.460 --> 14:59.240
and sometimes special guests

14:59.240 --> 15:00.840
have what's called a Tinkerbell Pass

15:00.840 --> 15:02.200
that they give out in the guest services.

15:02.600 --> 15:03.660
If you have a Tinkerbell Pass,

15:03.740 --> 15:05.540
it's an automatic front to the line

15:05.540 --> 15:06.520
for you and your party.

15:07.140 --> 15:09.020
Now, if you hurt yourself on the park property,

15:09.080 --> 15:09.940
usually they'll give you one

15:09.940 --> 15:11.880
or something of that nature,

15:12.280 --> 15:13.260
you know, vis-a-vis,

15:13.440 --> 15:14.060
buyer-view-wear,

15:14.320 --> 15:15.520
hideous corpus and all that shit.

15:15.640 --> 15:16.820
If you get bitch slapped by chicken?

15:17.620 --> 15:19.020
You might get kicked out of the park

15:19.020 --> 15:20.400
if you're kind of trying to defraud them,

15:20.400 --> 15:22.100
but I'll just plant that seed.

15:22.100 --> 15:24.660
Or you might get bitch slapped by Tigger.

15:25.380 --> 15:25.740
Right.

15:26.060 --> 15:26.560
You might get...

15:26.560 --> 15:28.680
You might get Tigger slapped.

15:29.200 --> 15:29.660
You're right.

15:31.180 --> 15:32.320
But yeah, so that's it for me.

15:32.540 --> 15:32.940
Housekeeping.

15:33.640 --> 15:35.000
All right, cool, cool.

15:35.140 --> 15:35.820
You know what else I...

15:35.820 --> 15:36.480
Here's a...

15:36.480 --> 15:37.960
I don't know why we're talking

15:37.960 --> 15:38.940
and promoting Disney here,

15:39.000 --> 15:40.020
but actually I learned something

15:40.020 --> 15:42.180
kind of bizarre about Disney.

15:42.280 --> 15:43.040
My friend,

15:43.560 --> 15:44.180
a good friend of mine

15:44.180 --> 15:45.120
I went to college with actually,

15:45.200 --> 15:47.600
was down here for his vacation,

15:47.700 --> 15:48.440
brought his family down.

15:48.500 --> 15:49.580
He's got an eight-year-old son.

15:49.580 --> 15:52.580
And this is probably not interesting

15:52.580 --> 15:53.300
to any of my listeners,

15:53.440 --> 15:54.140
but it was just weird

15:54.140 --> 15:54.960
because I never knew it.

15:56.240 --> 15:57.580
All of the employees,

15:58.380 --> 15:59.500
Imagineers, associates,

16:00.060 --> 16:01.120
whatever they're called,

16:01.760 --> 16:04.900
in every store around there,

16:05.000 --> 16:05.980
walking around the park,

16:06.140 --> 16:06.440
anything,

16:06.640 --> 16:08.100
any of the ones that you see,

16:08.180 --> 16:09.360
I don't think the food people,

16:09.480 --> 16:10.600
but any of the other employees

16:10.600 --> 16:11.120
that you see,

16:11.800 --> 16:12.760
they have...

16:12.760 --> 16:13.780
And they sell at the parks,

16:13.860 --> 16:14.900
they sell all these different

16:14.900 --> 16:15.900
Disney World pins

16:15.900 --> 16:17.780
that you can put on your hat,

16:17.780 --> 16:18.560
these hat pins,

16:18.700 --> 16:19.760
or like in the Boy Scouts,

16:19.880 --> 16:20.780
we used to trade pins

16:20.780 --> 16:21.540
and stuff all the time.

16:21.580 --> 16:22.140
Yeah, you can get them

16:22.140 --> 16:22.720
in kiosks.

16:22.800 --> 16:23.100
Right.

16:23.320 --> 16:24.580
They have them all over

16:24.580 --> 16:25.260
the place down here,

16:25.360 --> 16:26.780
but I didn't realize this.

16:26.840 --> 16:28.120
I know that people collect them

16:28.120 --> 16:29.040
and whatever, fine.

16:29.340 --> 16:30.040
I didn't realize

16:30.040 --> 16:31.260
that all of the employees,

16:32.000 --> 16:33.220
their shirts are covered with them.

16:33.260 --> 16:34.360
And I thought it was just flair,

16:34.480 --> 16:34.760
you know?

16:35.040 --> 16:35.660
It's just flair.

16:35.840 --> 16:36.900
I didn't think anything of it.

16:37.320 --> 16:38.420
But my friend,

16:38.540 --> 16:39.320
his eight-year-old son,

16:39.420 --> 16:40.640
I find out now

16:40.640 --> 16:43.600
that those Disney employees

16:43.600 --> 16:44.860
that have the flair on there,

16:44.860 --> 16:46.040
they have to trade you

16:46.040 --> 16:47.600
those pins anytime you want.

16:48.360 --> 16:49.760
So he was going around

16:49.760 --> 16:50.900
to all of these people

16:50.900 --> 16:52.300
with these little pins

16:52.300 --> 16:52.820
he's collected.

16:52.960 --> 16:54.680
And he knows all this stuff.

16:55.160 --> 16:55.500
He's like,

16:55.540 --> 16:56.480
oh, well, this one's a rare.

16:56.580 --> 16:57.940
There's only 2,000 made

16:57.940 --> 16:58.500
of this one.

16:58.560 --> 16:59.600
And this one is only released

16:59.600 --> 17:01.360
in like Switzo Disney

17:01.360 --> 17:02.780
in Switzerland or some shit.

17:03.380 --> 17:04.280
And he's going around

17:04.280 --> 17:05.320
looking and eyeballing

17:05.320 --> 17:05.940
all the employees

17:05.940 --> 17:07.280
and like making them trade him

17:07.280 --> 17:08.140
all the cool pins

17:08.140 --> 17:08.640
that he wanted.

17:09.580 --> 17:10.140
I don't know.

17:10.160 --> 17:10.880
I just thought it was cool

17:10.880 --> 17:12.000
because that's like a weird thing

17:12.000 --> 17:12.500
that nobody,

17:12.500 --> 17:13.760
at least I didn't know.

17:13.760 --> 17:16.400
So that falls kind of

17:16.400 --> 17:17.080
in the hacker sphere.

17:17.160 --> 17:18.040
It's stuff that we weren't

17:18.040 --> 17:18.840
supposed to know

17:18.840 --> 17:19.680
or that's not all that public.

17:19.760 --> 17:20.340
Did you know that?

17:21.020 --> 17:21.560
Yeah, you know,

17:21.620 --> 17:22.480
I'd heard something about it

17:22.480 --> 17:23.700
when I was in school.

17:23.900 --> 17:24.480
There were these girls

17:24.480 --> 17:25.380
that I used to hang out with.

17:25.480 --> 17:26.540
They were Disney super freaks.

17:27.440 --> 17:28.540
And they had mentioned

17:28.540 --> 17:29.320
something about that,

17:29.400 --> 17:29.840
but I didn't know

17:29.840 --> 17:31.100
that they were required to trade.

17:31.200 --> 17:31.860
I thought it was

17:31.860 --> 17:33.500
that they were allowed to.

17:33.920 --> 17:36.440
No, I think if a kid

17:36.440 --> 17:37.360
offers them, they have to.

17:38.040 --> 17:40.600
Now, I'm going to put on my

17:40.600 --> 17:41.440
this could be

17:41.440 --> 17:42.520
complete bullshit hat,

17:42.520 --> 17:44.000
but I've seen pictures

17:44.000 --> 17:45.020
and I'm pretty sure

17:45.020 --> 17:45.760
that it's confirmed

17:45.760 --> 17:47.280
that there is an actual

17:47.280 --> 17:49.540
pseudo half-court basketball hoop

17:49.540 --> 17:50.740
in the top of the Matterhorn

17:50.740 --> 17:51.740
in the Anaheim Disneyland.

17:52.920 --> 17:54.820
And as legend goes

17:54.820 --> 17:56.060
that this is because

17:56.060 --> 17:56.640
in the days

17:56.640 --> 17:57.100
when they were getting

17:57.100 --> 17:57.940
the zoning permits

17:57.940 --> 17:58.820
for Disneyland

17:58.820 --> 18:00.760
that they couldn't have

18:00.760 --> 18:01.580
on the eyesore

18:01.580 --> 18:02.680
that was the Matterhorn

18:02.680 --> 18:04.560
unless it was deemed

18:04.560 --> 18:05.580
like a sporting piece

18:05.580 --> 18:06.400
of sporting equipment

18:06.400 --> 18:07.420
or something along those lines.

18:07.540 --> 18:08.280
Correct me if I'm wrong.

18:08.380 --> 18:08.780
I know you guys

18:08.780 --> 18:10.140
are all going to blast me

18:10.140 --> 18:10.520
in emails

18:10.520 --> 18:11.440
if I fuck this up.

18:12.180 --> 18:13.700
But if you Google it,

18:13.720 --> 18:14.600
there is a picture of it.

18:14.660 --> 18:16.200
Just Google for Matterhorn basketball

18:16.200 --> 18:17.360
or something like that.

18:17.720 --> 18:18.860
Oh, that's a new one.

18:18.880 --> 18:19.520
This is turning into

18:19.520 --> 18:21.100
like a Disney Secrets episode

18:21.100 --> 18:21.660
or something.

18:22.080 --> 18:22.800
See, look at this.

18:22.800 --> 18:23.540
There's all kinds of shit

18:23.540 --> 18:24.320
that you'll have to look forward

18:24.320 --> 18:26.380
if you come on the 24th and 25th.

18:26.440 --> 18:26.820
Yeah, seriously.

18:27.020 --> 18:27.560
It really is.

18:27.800 --> 18:28.920
Disney is, listen,

18:29.040 --> 18:30.060
Disney is a fun place

18:30.060 --> 18:31.000
and a cool place to hang out.

18:31.060 --> 18:32.400
There's lots of stuff like that.

18:32.480 --> 18:33.140
It is, what is it?

18:33.180 --> 18:33.880
It's magical.

18:34.220 --> 18:35.760
It's, yeah,

18:35.840 --> 18:36.780
have a magical day.

18:36.840 --> 18:37.500
That was their slogan

18:37.500 --> 18:38.600
they were all talking about.

18:38.600 --> 18:40.280
I went to a seminar there one time

18:40.280 --> 18:42.360
presented by some of the Disney

18:42.360 --> 18:44.180
speech therapists,

18:44.340 --> 18:44.880
speech givers

18:44.880 --> 18:45.300
or whatever,

18:45.480 --> 18:46.080
speech therapists.

18:46.620 --> 18:48.460
And they were emphasized

18:48.460 --> 18:49.640
how, you know,

18:49.800 --> 18:51.320
they're imagineers

18:51.320 --> 18:53.020
and everything is about imagination

18:53.020 --> 18:54.680
and have a magical day

18:54.680 --> 18:55.600
and all this kind of stuff.

18:55.740 --> 18:56.960
So they do all kinds of stuff.

18:56.960 --> 18:57.400
And of course,

18:57.540 --> 18:58.300
I'm sure you've heard

18:58.300 --> 18:59.160
of the hidden Mickeys.

18:59.880 --> 19:00.440
Oh, yeah.

19:00.520 --> 19:01.700
They have all these hidden Mickeys.

19:01.800 --> 19:02.340
And I got to say,

19:02.400 --> 19:03.120
that's kind of fun

19:03.120 --> 19:03.820
as you're walking around.

19:03.940 --> 19:04.480
Like, as a hacker,

19:04.560 --> 19:06.060
I'm always noticing odd things

19:06.060 --> 19:07.540
or looking for computers

19:07.540 --> 19:09.180
or things that catch my eye.

19:09.240 --> 19:10.260
Like, I joked about my,

19:10.860 --> 19:12.060
how I always see numbers

19:12.060 --> 19:12.700
and I always see

19:12.700 --> 19:13.920
some hidden meaning in them

19:13.920 --> 19:14.840
and patterns

19:14.840 --> 19:15.800
and stuff like that.

19:16.040 --> 19:18.120
And always notice

19:18.120 --> 19:18.560
little things

19:18.560 --> 19:19.060
that are out of the way.

19:19.160 --> 19:19.680
And hidden Mickeys

19:19.680 --> 19:20.620
are just little pictures

19:20.620 --> 19:21.820
of Mickey Mouse ears,

19:21.940 --> 19:22.620
a little standard

19:22.620 --> 19:23.400
Mickey Mouse logo

19:23.400 --> 19:24.300
that they hide

19:24.300 --> 19:25.040
in the rocks

19:25.040 --> 19:25.860
or in the sidewalk

19:25.860 --> 19:28.100
or in any number of places,

19:28.260 --> 19:28.980
swirls of paint

19:28.980 --> 19:29.960
that they've intentionally made

19:29.960 --> 19:30.680
look like the logo.

19:31.240 --> 19:31.560
I don't know.

19:31.640 --> 19:32.540
I guess we've promoted

19:32.540 --> 19:33.140
Disney enough.

19:33.140 --> 19:34.000
We should probably move on

19:34.000 --> 19:35.820
to some e-mail.

19:56.460 --> 19:57.920
Alright, e-mail time.

19:57.980 --> 19:58.220
You ready?

19:59.020 --> 19:59.680
Let's do it.

20:00.100 --> 20:00.740
I'm ready.

20:00.740 --> 20:01.500
I've got my

20:01.500 --> 20:03.600
my lashing pants on.

20:04.340 --> 20:04.400
Alright.

20:04.820 --> 20:05.820
Hey, you've got pants on?

20:06.360 --> 20:07.240
Yeah, for once.

20:07.560 --> 20:07.920
Damn.

20:08.820 --> 20:10.240
Well, I'm already pants-less

20:10.240 --> 20:10.840
so I guess I'm going to

20:10.840 --> 20:11.680
have to continue here.

20:12.100 --> 20:12.560
Don't you hate

20:12.560 --> 20:13.040
when you're sitting

20:13.040 --> 20:13.800
without pants

20:13.800 --> 20:14.440
and your butt

20:14.440 --> 20:15.460
sticks to the leather chair?

20:15.560 --> 20:16.000
That's just,

20:16.180 --> 20:17.620
that's just rough.

20:17.980 --> 20:18.560
You've got to put down

20:18.560 --> 20:19.120
wax paper.

20:19.780 --> 20:20.080
Really?

20:20.620 --> 20:21.340
Yeah, it does.

20:21.340 --> 20:23.040
Even if that solves

20:23.040 --> 20:23.680
one problem

20:23.680 --> 20:24.060
but you know

20:24.060 --> 20:24.740
I have a freshly

20:24.740 --> 20:26.060
shaven sack

20:26.060 --> 20:27.520
so when I get up

20:27.520 --> 20:28.020
I have the whole

20:28.020 --> 20:28.620
bat wings

20:28.620 --> 20:29.540
so you know

20:29.540 --> 20:30.660
I've got that problem

20:30.660 --> 20:32.160
to deal with too.

20:32.760 --> 20:33.360
I thought that was

20:33.360 --> 20:34.020
photoshopped

20:34.020 --> 20:34.680
but I guess not.

20:35.000 --> 20:36.060
No, that was

20:36.060 --> 20:37.020
completely real.

20:37.600 --> 20:38.000
Oh.

20:39.160 --> 20:40.220
Yeah, are we going

20:40.220 --> 20:40.680
to get e-mails

20:40.680 --> 20:41.440
asking me what

20:41.440 --> 20:42.040
bat wings are?

20:42.120 --> 20:42.940
We'll move on.

20:43.020 --> 20:43.520
E-mails,

20:43.780 --> 20:44.420
actually let's,

20:44.660 --> 20:45.560
I'll encapsulate

20:45.560 --> 20:46.400
several of the e-mails

20:46.400 --> 20:46.900
quickly

20:46.900 --> 20:48.700
because quite a few

20:48.700 --> 20:49.540
e-mails of people

20:49.540 --> 20:50.180
talking about

20:50.180 --> 20:51.200
the audio quality

20:51.200 --> 20:52.900
Ratchet was having

20:52.900 --> 20:54.260
some asterisk problem

20:54.260 --> 20:55.240
some VoIP issues

20:55.240 --> 20:56.320
I believe on his end

20:56.320 --> 20:56.880
where the timing

20:56.880 --> 20:57.780
was coming through weird.

20:58.920 --> 21:00.780
I don't know exactly

21:00.780 --> 21:01.580
how or what

21:01.580 --> 21:02.060
he could change

21:02.060 --> 21:02.480
to fix it

21:02.480 --> 21:03.300
and I guess he hadn't

21:03.300 --> 21:03.840
gotten around

21:03.840 --> 21:04.440
to doing it either

21:04.440 --> 21:05.960
but it was a weird thing

21:05.960 --> 21:07.040
that the longer we talked

21:07.040 --> 21:07.660
the more and more

21:07.660 --> 21:08.240
out of sync

21:08.240 --> 21:09.060
we were getting

21:09.060 --> 21:10.840
as far as him

21:10.840 --> 21:12.180
and I having the conversation

21:12.180 --> 21:12.980
when we recorded

21:12.980 --> 21:13.840
and I guess other people

21:13.840 --> 21:14.600
had this as well

21:14.600 --> 21:16.480
everything sounded fine

21:16.480 --> 21:16.960
to us

21:16.960 --> 21:18.320
there was no delay

21:18.320 --> 21:19.360
we were talking normally

21:19.360 --> 21:20.000
of course

21:20.000 --> 21:20.840
obviously I can't

21:20.840 --> 21:21.960
answer a question

21:21.960 --> 21:22.800
that hasn't been asked yet

21:22.800 --> 21:23.860
but for some reason

21:23.860 --> 21:25.080
the way the separate lines

21:25.080 --> 21:26.200
or whatever the separate

21:26.200 --> 21:27.380
voices were getting recorded

21:27.380 --> 21:28.800
it was causing

21:28.800 --> 21:29.460
some kind of lag

21:29.460 --> 21:30.560
to writing maybe

21:30.560 --> 21:31.440
maybe one was writing

21:31.440 --> 21:32.280
faster than the other

21:32.280 --> 21:33.100
I'm not exactly sure

21:33.100 --> 21:33.620
how the writing

21:33.620 --> 21:34.580
to disc works

21:34.580 --> 21:35.600
but it was getting

21:35.600 --> 21:36.260
out of sync

21:36.260 --> 21:36.840
when it was actually

21:36.840 --> 21:38.260
getting written to disc

21:38.260 --> 21:39.260
I think is what was happening

21:39.260 --> 21:41.580
but that's all

21:41.580 --> 21:42.440
water under the bridge

21:42.440 --> 21:43.200
it's irrelevant now

21:43.200 --> 21:43.980
because I am back

21:43.980 --> 21:44.820
on the mic

21:44.820 --> 21:47.160
so you'll have to deal

21:47.160 --> 21:48.220
with my wonderful

21:48.220 --> 21:49.940
wonderful radio voice

21:49.940 --> 21:51.880
he said sarcastically

21:51.880 --> 21:55.540
so our first actual email

21:55.540 --> 21:56.280
this week

21:56.280 --> 21:58.160
letter number one

21:58.160 --> 22:01.000
is from

22:01.000 --> 22:02.820
Redbox Chili Pepper

22:02.820 --> 22:04.640
Redbox Chili Pepper

22:04.640 --> 22:05.280
says

22:05.280 --> 22:06.500
in the last episode

22:06.500 --> 22:07.160
Savant

22:07.160 --> 22:07.780
that's you

22:07.780 --> 22:09.760
quoted Mike Myers

22:09.760 --> 22:10.840
from Wayne's World

22:10.840 --> 22:11.860
then he says

22:11.860 --> 22:13.120
that it's a quote

22:13.120 --> 22:13.800
from the movie

22:13.800 --> 22:15.540
Ferris Bueller's Day Off

22:15.540 --> 22:18.200
a movie from an entirely

22:18.200 --> 22:19.840
different decade

22:19.840 --> 22:21.580
than Wayne's World

22:21.580 --> 22:24.060
how can I trust

22:24.060 --> 22:24.800
your supposedly

22:24.800 --> 22:26.460
extensive hacker knowledge

22:26.460 --> 22:27.680
if you can't even

22:27.680 --> 22:29.420
cite movies properly

22:29.420 --> 22:31.080
my faith in BinRev

22:31.080 --> 22:32.280
is completely shaken

22:32.280 --> 22:34.080
I can't go on like this

22:34.080 --> 22:35.520
thanks for all the good years

22:35.520 --> 22:36.680
but goodbye

22:36.680 --> 22:38.120
a former listener

22:38.120 --> 22:40.460
Redbox Chili Pepper

22:40.460 --> 22:42.240
now Savant

22:42.240 --> 22:45.140
I got fucking pwned

22:45.140 --> 22:45.960
it's true

22:45.960 --> 22:47.200
on a scale of one to ten

22:47.200 --> 22:48.260
exactly how retarded

22:48.260 --> 22:49.240
are you?

22:49.240 --> 22:50.120
at least eleven

22:50.120 --> 22:51.280
at least eleven

22:51.280 --> 22:51.960
Ferris Bueller

22:51.960 --> 22:52.580
and Wayne's World

22:52.580 --> 22:53.440
come on

22:53.440 --> 22:54.260
you know what

22:54.260 --> 22:54.580
okay

22:54.580 --> 22:55.840
and there is no

22:55.840 --> 22:56.600
excuse for that

22:56.600 --> 22:57.600
but that movie

22:57.600 --> 22:58.660
both of them

22:58.660 --> 22:59.200
are excellent

22:59.200 --> 22:59.920
excellent movies

22:59.920 --> 23:03.160
so in favor

23:03.160 --> 23:04.260
of killing myself

23:04.260 --> 23:04.800
which is what

23:04.800 --> 23:05.320
I recommended

23:05.320 --> 23:05.880
that people do

23:05.880 --> 23:06.400
if they hadn't

23:06.400 --> 23:07.080
seen that movie

23:07.080 --> 23:08.320
I'm going to be

23:08.320 --> 23:09.060
taking lashes

23:09.060 --> 23:10.380
for the next two weeks

23:10.380 --> 23:11.360
and I'm giving up

23:11.360 --> 23:12.000
my op status

23:12.000 --> 23:12.600
for a week

23:12.600 --> 23:14.940
but he's right

23:14.940 --> 23:16.320
he's absolutely right

23:16.320 --> 23:17.700
now it's funny

23:17.700 --> 23:18.540
a couple things

23:18.540 --> 23:18.980
number one

23:18.980 --> 23:19.760
his last episode

23:19.760 --> 23:20.400
I went on air

23:20.400 --> 23:21.220
is officially stating

23:21.220 --> 23:22.160
that it was the first episode

23:22.160 --> 23:22.980
I'd ever done

23:22.980 --> 23:23.720
without drinking

23:23.720 --> 23:24.620
any sort of alcohol

23:24.620 --> 23:25.600
while recording

23:25.600 --> 23:26.660
well actually

23:26.660 --> 23:28.780
and you have

23:28.780 --> 23:30.080
another unique

23:30.080 --> 23:31.640
lifestyle change

23:31.640 --> 23:32.080
this week

23:32.080 --> 23:32.600
to announce

23:32.600 --> 23:34.100
well first of all

23:34.100 --> 23:35.680
that I am drinking

23:35.680 --> 23:36.540
on the air today

23:36.540 --> 23:37.920
so everything

23:37.920 --> 23:38.580
should be accurate

23:38.580 --> 23:39.380
again but if not

23:39.380 --> 23:40.480
feel free to flame me

23:40.480 --> 23:42.500
and yeah

23:42.500 --> 23:43.300
like Stank was saying

23:43.300 --> 23:44.400
this is day four

23:44.400 --> 23:45.080
of no cigarette

23:45.080 --> 23:45.920
smoking for me

23:45.920 --> 23:46.960
four days

23:46.960 --> 23:47.520
and you're already

23:47.520 --> 23:48.680
freaked out this bad

23:48.680 --> 23:50.620
it was worse man

23:50.620 --> 23:51.380
it was a lot worse

23:51.380 --> 23:52.840
you got the patch

23:52.840 --> 23:54.720
no the patch

23:54.720 --> 23:55.440
gives me crazy

23:55.440 --> 23:56.140
fever dreams

23:56.140 --> 23:56.940
I'm trying the

23:56.940 --> 23:57.560
nicotine gum

23:57.560 --> 23:58.240
this time around

23:58.240 --> 24:00.080
and I gotta say

24:00.080 --> 24:01.020
it's working pretty

24:01.020 --> 24:01.520
well for my

24:01.520 --> 24:01.920
Nick Fit

24:01.920 --> 24:04.620
okay see I've always

24:04.620 --> 24:05.000
wondered

24:05.000 --> 24:06.320
that gum

24:06.320 --> 24:06.860
is it just

24:06.860 --> 24:07.800
is it nasty

24:07.800 --> 24:10.620
now the original

24:10.620 --> 24:11.720
formula for Nicorette

24:11.720 --> 24:12.420
was complete

24:12.420 --> 24:13.260
ass nasty

24:13.260 --> 24:14.460
you had to sort of

24:14.460 --> 24:15.100
put it up in your

24:15.100 --> 24:16.100
cheek and bite down

24:16.100 --> 24:16.780
on it like it was

24:16.780 --> 24:17.440
a piece of chewing

24:17.440 --> 24:18.320
tobacco or something

24:18.320 --> 24:19.280
however

24:19.280 --> 24:21.060
and that's why

24:21.060 --> 24:21.720
I always avoided it

24:21.720 --> 24:22.560
but they've done

24:22.560 --> 24:23.200
something with it

24:23.200 --> 24:24.020
redesigned the formula

24:24.020 --> 24:24.980
this is the fruit

24:24.980 --> 24:25.800
chill version

24:25.800 --> 24:27.120
it tastes like

24:27.120 --> 24:27.820
Wrigley's

24:27.820 --> 24:29.580
and you can chew

24:29.580 --> 24:30.060
it and the more

24:30.060 --> 24:30.640
you chew it

24:30.640 --> 24:31.120
then the more

24:31.120 --> 24:31.680
nicotine is

24:31.680 --> 24:32.020
distributed

24:32.020 --> 24:32.640
so like if I'm

24:32.640 --> 24:33.180
freaking out

24:33.180 --> 24:33.500
and I'm chewing

24:33.500 --> 24:34.040
real fast

24:34.040 --> 24:34.780
like a maniac

24:34.780 --> 24:35.680
on speed or

24:35.680 --> 24:36.020
something

24:36.020 --> 24:37.240
then I get more

24:37.240 --> 24:37.940
nicotine and I

24:37.940 --> 24:38.800
calm down faster

24:38.800 --> 24:39.440
because I'm like

24:39.440 --> 24:39.920
the little monkey

24:39.920 --> 24:40.520
who pushes the

24:40.520 --> 24:41.000
red button

24:41.000 --> 24:42.160
or do you just

24:42.160 --> 24:42.800
do you pop like

24:42.800 --> 24:43.520
five or six of

24:43.520 --> 24:44.020
them at a time

24:44.020 --> 24:44.540
does that help

24:44.540 --> 24:45.640
well what I've

24:45.640 --> 24:45.920
been doing

24:45.920 --> 24:46.880
I'm not that bad

24:46.880 --> 24:47.180
yet

24:47.180 --> 24:47.880
what I've been

24:47.880 --> 24:49.180
doing is sort of

24:49.180 --> 24:50.100
tricking myself

24:50.100 --> 24:50.720
and then I'll take

24:50.720 --> 24:51.700
regular gum like

24:51.700 --> 24:52.840
a spirit man or

24:52.840 --> 24:53.340
whatever the fuck

24:53.340 --> 24:54.860
and pop a bunch

24:54.860 --> 24:55.280
of them in my

24:55.280 --> 24:55.940
pocket with the

24:55.940 --> 24:56.720
regular nicotine

24:56.720 --> 24:57.820
and so

24:57.820 --> 24:58.820
you're trying to

24:58.820 --> 24:59.380
hack yourself

24:59.380 --> 25:00.880
you're trying to

25:00.880 --> 25:01.380
hack your own

25:01.380 --> 25:02.220
brain into thinking

25:02.220 --> 25:04.320
I have to do

25:04.320 --> 25:05.000
something if I'm

25:05.000 --> 25:05.360
going to quit

25:05.360 --> 25:06.120
because I've been

25:06.120 --> 25:06.900
smoking a pack a day

25:06.900 --> 25:07.580
for five years

25:07.580 --> 25:08.920
oh man

25:08.920 --> 25:09.740
yeah

25:09.740 --> 25:10.840
you got a lot of

25:10.840 --> 25:12.280
damage to undo

25:12.280 --> 25:13.960
yeah well

25:13.960 --> 25:15.040
four days is the

25:15.040 --> 25:15.740
longest I've made

25:15.740 --> 25:16.520
it without anything

25:16.520 --> 25:16.900
so

25:16.900 --> 25:17.420
well

25:17.420 --> 25:20.340
next week on the

25:20.340 --> 25:20.900
show we'll let

25:20.900 --> 25:21.520
you know if he's

25:21.520 --> 25:22.660
relapsed or not

25:22.660 --> 25:23.900
well you'll know

25:23.900 --> 25:24.580
in the newspapers

25:24.580 --> 25:25.100
when they talk

25:25.100 --> 25:25.800
about local hacker

25:25.800 --> 25:26.760
being arrested for

25:26.760 --> 25:27.180
homicide

25:27.180 --> 25:27.980
uh oh

25:27.980 --> 25:29.800
well and

25:29.800 --> 25:30.920
back to this email

25:30.920 --> 25:31.740
the other thing I

25:31.740 --> 25:32.280
got to say is

25:32.280 --> 25:33.260
come on RBCP

25:33.260 --> 25:34.240
let's get real here

25:34.240 --> 25:34.600
I mean

25:34.600 --> 25:36.160
faith in Binrev

25:36.160 --> 25:36.900
are you kidding me

25:36.900 --> 25:37.300
with that

25:37.300 --> 25:38.100
I mean seriously

25:38.100 --> 25:39.100
do you really think

25:39.100 --> 25:39.820
I'm buying that

25:39.820 --> 25:41.480
yeah

25:41.480 --> 25:42.160
he went out to

25:42.160 --> 25:43.140
say my supposedly

25:43.140 --> 25:43.940
extensive hacker

25:43.940 --> 25:44.620
knowledge but I

25:44.620 --> 25:45.060
want to know

25:45.060 --> 25:46.120
who sold you

25:46.120 --> 25:46.700
that line of

25:46.700 --> 25:47.000
bullshit

25:47.000 --> 25:47.880
I have never

25:47.880 --> 25:48.800
ever claimed to

25:48.800 --> 25:49.700
be lead or to

25:49.700 --> 25:50.080
know what the

25:50.080 --> 25:50.480
fuck I was

25:50.480 --> 25:51.120
talking about

25:51.120 --> 25:52.080
but um

25:52.080 --> 25:53.020
you know

25:53.020 --> 25:53.600
in another

25:53.600 --> 25:54.440
chance of

25:54.440 --> 25:54.740
coincidence

25:54.740 --> 25:55.480
I fished out

25:55.480 --> 25:56.320
my PLA

25:56.320 --> 25:57.320
best of radio

25:57.320 --> 25:58.200
mix a couple

25:58.200 --> 25:58.820
days ago from

25:58.820 --> 25:59.380
Hope 5

25:59.380 --> 26:00.260
or excuse me

26:00.260 --> 26:00.580
6

26:00.580 --> 26:01.360
see there I go

26:01.360 --> 26:01.880
again fucking

26:01.880 --> 26:02.140
up

26:02.140 --> 26:02.880
I need to

26:02.880 --> 26:03.320
take a sip

26:03.320 --> 26:03.880
hold on

26:03.880 --> 26:06.820
anyway

26:06.820 --> 26:08.020
and so yeah

26:08.020 --> 26:08.360
I was just

26:08.360 --> 26:08.860
listening to that

26:08.860 --> 26:09.520
again I had no

26:09.520 --> 26:10.260
idea that he was

26:10.260 --> 26:10.700
a fan of the

26:10.700 --> 26:10.920
show

26:10.920 --> 26:12.020
emphasis on was

26:12.020 --> 26:12.800
he's yeah

26:12.800 --> 26:13.880
we lost him

26:13.880 --> 26:14.400
we blew it

26:14.400 --> 26:14.960
because of you

26:14.960 --> 26:16.260
you cost us a

26:16.260 --> 26:16.900
listener and it's

26:16.900 --> 26:17.500
right there in

26:17.500 --> 26:18.020
writing it's

26:18.020 --> 26:18.880
directly attributed

26:18.880 --> 26:20.120
to you I blame

26:20.120 --> 26:20.780
that one for you

26:20.780 --> 26:21.680
you owe me

26:21.680 --> 26:24.140
okay for losing

26:24.140 --> 26:26.060
RBCP I demand

26:26.060 --> 26:27.860
in return a big

26:27.860 --> 26:28.760
titty blonde

26:28.760 --> 26:29.460
listener big

26:29.460 --> 26:30.060
titty blonde

26:30.060 --> 26:30.780
chick listener

26:30.780 --> 26:32.920
so okay

26:32.920 --> 26:34.180
that that I'll

26:34.180 --> 26:35.420
consider that even

26:35.420 --> 26:36.800
sorry RBCP but

26:36.800 --> 26:38.020
you know tits are

26:38.020 --> 26:39.040
greater than PLA

26:39.040 --> 26:39.680
that's sorry

26:39.680 --> 26:40.400
so you want me to

26:40.400 --> 26:41.660
like get said

26:41.660 --> 26:42.940
said listener to

26:42.940 --> 26:44.360
write BRR on her

26:44.360 --> 26:44.900
tits or something

26:44.900 --> 26:45.200
and take a

26:45.200 --> 26:45.440
picture

26:45.440 --> 26:46.660
oh dude that

26:46.660 --> 26:47.300
would be I

26:47.300 --> 26:48.020
would so put

26:48.020 --> 26:48.500
that on the

26:48.500 --> 26:49.180
radio's page

26:49.180 --> 26:49.700
right up at the

26:49.700 --> 26:50.200
top at the

26:50.200 --> 26:51.440
beginning of the

26:51.440 --> 26:53.060
radio archive page

26:53.060 --> 26:54.160
alright well I

26:54.160 --> 26:54.960
know I actually

26:54.960 --> 26:55.760
know a listener

26:55.760 --> 26:56.560
that might do it

26:56.560 --> 26:57.480
but probably

26:57.480 --> 26:58.220
under the pretense

26:58.220 --> 26:58.720
of her face

26:58.720 --> 26:59.300
not being it

26:59.300 --> 26:59.660
so you just

26:59.660 --> 27:00.160
have to take

27:00.160 --> 27:00.640
my word that

27:00.640 --> 27:01.100
she's blonde

27:01.100 --> 27:03.040
or that she's a

27:03.040 --> 27:03.300
chick

27:03.300 --> 27:04.280
yes

27:04.280 --> 27:05.840
are we gonna

27:05.840 --> 27:06.240
have like

27:06.240 --> 27:07.380
are we gonna

27:07.380 --> 27:08.020
have dudes

27:08.020 --> 27:09.360
sending in

27:09.360 --> 27:09.840
pictures of

27:09.840 --> 27:09.960
them

27:09.960 --> 27:10.880
their chest

27:10.880 --> 27:11.560
with BRR

27:11.560 --> 27:12.200
across it

27:12.200 --> 27:13.380
hey whatever

27:13.380 --> 27:13.920
what you

27:13.920 --> 27:14.520
request in the

27:14.520 --> 27:15.280
IRC channel

27:15.280 --> 27:16.260
is none of

27:16.260 --> 27:16.720
my business

27:16.720 --> 27:17.120
on the air

27:17.120 --> 27:17.580
right now

27:17.580 --> 27:18.540
I guess we

27:18.540 --> 27:19.060
just put out

27:19.060 --> 27:19.580
a call to

27:19.580 --> 27:20.020
anybody that

27:20.020 --> 27:20.320
wants to

27:20.320 --> 27:20.820
submit their

27:20.820 --> 27:21.440
boobies with

27:21.440 --> 27:22.320
BRR on them

27:22.320 --> 27:23.080
but I don't

27:23.080 --> 27:23.560
have a whole lot

27:23.560 --> 27:23.960
of faith that

27:23.960 --> 27:24.320
we're gonna get

27:24.320 --> 27:25.160
any real boobies

27:25.160 --> 27:25.580
because we don't

27:25.580 --> 27:26.120
have any real

27:26.120 --> 27:26.880
female listeners

27:26.880 --> 27:27.380
I think we've

27:27.380 --> 27:28.220
established that

27:28.220 --> 27:28.760
right

27:28.760 --> 27:29.320
they're all the

27:29.320 --> 27:29.800
same guy

27:29.800 --> 27:30.340
yeah maybe

27:30.340 --> 27:31.000
one or two

27:31.000 --> 27:32.840
so I tell you

27:32.840 --> 27:33.260
what we'll put

27:33.260 --> 27:34.060
them all up in

27:34.060 --> 27:36.180
the bin rev gallery

27:36.180 --> 27:36.860
somewhere anybody

27:36.860 --> 27:37.460
that submits

27:37.460 --> 27:38.300
anything we'll put

27:38.300 --> 27:38.700
it up for the

27:38.700 --> 27:39.040
hell of it

27:39.040 --> 27:39.480
why not

27:39.480 --> 27:43.180
alright let's

27:43.180 --> 27:44.500
see next email

27:44.500 --> 27:46.740
next email comes

27:46.740 --> 27:48.700
from jukebox

27:48.700 --> 27:50.420
or juke80x

27:50.420 --> 27:50.820
we're gonna go

27:50.820 --> 27:51.480
with jukebox

27:51.480 --> 27:52.120
I'm pretty sure

27:52.120 --> 27:53.620
jukebox says

27:53.620 --> 27:54.700
black rachet

27:54.700 --> 27:56.180
I guess that's

27:56.180 --> 27:56.940
probably ratchet

27:56.940 --> 27:57.360
there

27:57.360 --> 27:58.560
it's french

27:58.560 --> 27:59.100
yeah

27:59.100 --> 27:59.960
here's a list

27:59.960 --> 28:00.500
of mistakes

28:00.500 --> 28:01.420
made during the

28:01.420 --> 28:01.860
show with

28:01.860 --> 28:02.300
corrections

28:02.300 --> 28:02.860
Dan he doesn't

28:02.860 --> 28:03.240
fuck around

28:03.240 --> 28:03.720
he just goes

28:03.720 --> 28:04.300
right in

28:04.300 --> 28:05.020
he's like

28:05.020 --> 28:05.380
here's where

28:05.380 --> 28:05.900
you fucked up

28:05.900 --> 28:06.600
number one

28:06.600 --> 28:08.140
let's see

28:08.140 --> 28:09.280
made during the

28:09.280 --> 28:09.580
show with

28:09.580 --> 28:09.920
corrections

28:09.920 --> 28:10.660
one the show

28:10.660 --> 28:11.220
aired on

28:11.220 --> 28:12.180
January 16th

28:12.180 --> 28:13.540
not 17th

28:13.540 --> 28:14.460
wah wah

28:14.460 --> 28:17.320
the SAT

28:17.320 --> 28:18.420
changed a couple

28:18.420 --> 28:19.040
of years ago

28:19.040 --> 28:19.640
so the highest

28:19.640 --> 28:20.360
score available

28:20.360 --> 28:21.260
is now a

28:21.260 --> 28:22.300
2400

28:22.300 --> 28:24.220
I've never

28:24.220 --> 28:24.840
actually taken

28:24.840 --> 28:25.380
the SAT

28:25.380 --> 28:26.000
just for the

28:26.000 --> 28:26.260
record

28:26.260 --> 28:27.220
nor have I

28:27.220 --> 28:27.700
isn't that

28:27.700 --> 28:28.360
interesting enough

28:28.360 --> 28:28.980
hackers never

28:28.980 --> 28:29.540
seemed to

28:29.540 --> 28:30.520
to take the

28:30.520 --> 28:30.820
SAT

28:30.820 --> 28:31.780
there was a

28:31.780 --> 28:33.140
quote unquote

28:33.140 --> 28:33.900
computer glitch

28:33.900 --> 28:34.360
I'm doing the

28:34.360 --> 28:35.120
little fingers in

28:35.120 --> 28:35.800
the air sign

28:35.800 --> 28:36.020
for

28:36.020 --> 28:36.380
yeah

28:36.380 --> 28:37.420
there was a

28:37.420 --> 28:38.200
computer glitch

28:38.200 --> 28:39.460
that happened

28:39.460 --> 28:40.100
and I never

28:40.100 --> 28:40.600
took the

28:40.600 --> 28:41.600
SATs either

28:41.600 --> 28:43.060
but I do have

28:43.060 --> 28:43.760
two degrees

28:43.760 --> 28:44.140
so

28:44.140 --> 28:46.720
and number

28:46.720 --> 28:47.140
three

28:47.140 --> 28:47.720
oh here it

28:47.720 --> 28:48.060
goes

28:48.060 --> 28:48.880
the joke

28:48.880 --> 28:49.640
made about

28:49.640 --> 28:50.400
quote having

28:50.400 --> 28:51.100
mono for a

28:51.100 --> 28:51.440
year

28:51.440 --> 28:52.480
was a reference

28:52.480 --> 28:53.140
from Wayne's

28:53.140 --> 28:53.380
world

28:53.380 --> 28:53.960
not

28:53.960 --> 28:55.340
Ferris Bueller's

28:55.340 --> 28:55.660
day

28:55.660 --> 28:56.360
off

28:56.360 --> 28:57.300
Savant

28:57.300 --> 28:57.640
dude

28:57.640 --> 28:58.280
you're so

28:58.280 --> 28:58.860
getting roasted

28:58.860 --> 28:59.440
for this

28:59.440 --> 29:00.460
yeah

29:00.460 --> 29:00.920
you know

29:00.920 --> 29:01.080
but

29:01.080 --> 29:01.620
you know

29:01.620 --> 29:01.740
who

29:01.740 --> 29:02.620
Black Rache

29:02.620 --> 29:03.120
should have

29:03.120 --> 29:03.660
also caught

29:03.660 --> 29:04.220
this as well

29:04.220 --> 29:04.500
though

29:04.500 --> 29:05.260
he should have

29:05.260 --> 29:05.620
known better

29:05.620 --> 29:05.900
he didn't

29:05.900 --> 29:06.440
correct you

29:06.440 --> 29:07.400
no

29:07.400 --> 29:07.940
but he should

29:07.940 --> 29:08.140
have known

29:08.140 --> 29:08.620
better than

29:08.620 --> 29:09.180
having me on

29:09.180 --> 29:09.480
the show

29:09.480 --> 29:09.800
again

29:09.800 --> 29:11.020
well that too

29:11.020 --> 29:11.620
but you know

29:11.620 --> 29:12.300
what are you

29:12.300 --> 29:12.640
going to do

29:12.640 --> 29:13.080
we got to have

29:13.080 --> 29:13.520
somebody from

29:13.520 --> 29:14.040
the west coast

29:14.040 --> 29:14.540
to represent

29:14.540 --> 29:15.620
and lord knows

29:15.620 --> 29:16.200
Verbal's not

29:16.200 --> 29:17.040
around these days

29:17.040 --> 29:19.440
anyway

29:19.440 --> 29:22.280
let's see

29:22.280 --> 29:23.240
next email

29:23.240 --> 29:24.760
next email

29:24.760 --> 29:25.080
is

29:25.080 --> 29:25.460
let me see

29:25.460 --> 29:25.720
here

29:25.720 --> 29:26.540
let your cock

29:26.540 --> 29:27.340
be your master

29:27.340 --> 29:28.120
okay I'm sorry

29:28.120 --> 29:28.580
that one's

29:28.580 --> 29:29.120
that one's

29:29.120 --> 29:29.620
I got to read

29:29.620 --> 29:30.060
that later

29:30.060 --> 29:30.600
okay

29:30.600 --> 29:33.380
that one is

29:33.380 --> 29:33.780
yeah

29:33.780 --> 29:34.300
okay

29:34.300 --> 29:35.380
actually you know

29:35.380 --> 29:36.140
what funny story

29:36.140 --> 29:37.040
I'll interject here

29:37.040 --> 29:39.360
I have a

29:39.360 --> 29:40.300
trio

29:40.300 --> 29:41.580
700w

29:41.580 --> 29:42.480
smartphone

29:42.480 --> 29:43.220
whatever the hell

29:43.220 --> 29:44.000
the official terms

29:44.000 --> 29:44.540
are these days

29:44.540 --> 29:45.080
where I have my

29:45.080 --> 29:45.820
email sent

29:45.820 --> 29:47.360
one of my

29:47.360 --> 29:47.980
accounts anyway

29:47.980 --> 29:49.940
and it's kind of

29:49.940 --> 29:50.580
a funny thing

29:50.580 --> 29:51.560
here speaking of

29:51.560 --> 29:52.160
your cock

29:52.160 --> 29:52.720
will be your

29:52.720 --> 29:53.240
master

29:53.240 --> 29:56.140
unfortunately the

29:56.140 --> 29:56.600
way this thing

29:56.600 --> 29:57.140
works is it

29:57.140 --> 29:57.780
also forwards

29:57.780 --> 29:58.860
my spam to me

29:58.860 --> 30:00.180
so yeah

30:00.180 --> 30:00.580
there's some

30:00.580 --> 30:01.640
spam slipping

30:01.640 --> 30:02.040
through there

30:02.040 --> 30:02.520
always is

30:02.520 --> 30:03.000
you can't get

30:03.000 --> 30:03.340
it all

30:03.340 --> 30:04.640
and occasionally

30:04.640 --> 30:05.620
I will get

30:05.620 --> 30:07.300
a nasty message

30:07.300 --> 30:07.780
like that

30:07.780 --> 30:08.100
which is

30:08.100 --> 30:08.540
potentially

30:08.540 --> 30:09.080
embarrassing

30:09.080 --> 30:09.460
if you're

30:09.460 --> 30:09.700
ever

30:09.700 --> 30:10.880
like I was

30:10.880 --> 30:11.400
showing a

30:11.400 --> 30:11.980
friend the

30:11.980 --> 30:13.100
cell phone

30:13.100 --> 30:13.580
one time

30:13.580 --> 30:14.000
and he's

30:14.000 --> 30:14.900
showing him

30:14.900 --> 30:15.240
how the

30:15.240 --> 30:15.640
pocket

30:15.640 --> 30:15.960
outlook

30:15.960 --> 30:16.240
and how

30:16.240 --> 30:16.600
the email

30:16.600 --> 30:17.080
works

30:17.080 --> 30:17.720
and he

30:17.720 --> 30:17.980
started

30:17.980 --> 30:18.440
scrolling

30:18.440 --> 30:19.000
through there

30:19.000 --> 30:19.200
and there

30:19.200 --> 30:19.560
was a couple

30:19.560 --> 30:20.240
old spams

30:20.240 --> 30:20.660
on there

30:20.660 --> 30:21.000
and it was

30:21.000 --> 30:21.620
it was a

30:21.620 --> 30:21.900
friend of

30:21.900 --> 30:22.020
mine

30:22.020 --> 30:22.340
so it was

30:22.340 --> 30:22.680
just kind

30:22.680 --> 30:23.100
of funny

30:23.100 --> 30:24.460
but one

30:24.460 --> 30:25.040
other time

30:25.040 --> 30:25.680
I was actually

30:25.680 --> 30:26.440
sitting in a

30:26.440 --> 30:27.280
meeting with a

30:27.280 --> 30:27.800
room full of

30:27.800 --> 30:28.380
people about a

30:28.380 --> 30:29.020
conference room

30:29.020 --> 30:29.500
we had a

30:29.500 --> 30:30.160
conference call

30:30.160 --> 30:30.660
going on

30:30.660 --> 30:31.140
I got a

30:31.140 --> 30:32.400
phone vibrated

30:32.400 --> 30:32.840
that had an

30:32.840 --> 30:33.420
email so I

30:33.420 --> 30:34.440
look at it

30:34.440 --> 30:36.080
and right there

30:36.080 --> 30:36.800
big letters in the

30:36.800 --> 30:37.560
headline was

30:37.560 --> 30:39.400
something I don't

30:39.400 --> 30:39.860
remember exact

30:39.860 --> 30:40.400
something like

30:40.400 --> 30:41.180
we can help you

30:41.180 --> 30:42.260
come bucket loads

30:42.260 --> 30:43.020
or something like

30:43.020 --> 30:43.180
that

30:43.180 --> 30:44.140
and I

30:44.140 --> 30:44.820
literally

30:44.820 --> 30:46.260
I had to put my

30:46.260 --> 30:46.860
hand over my

30:46.860 --> 30:47.480
mouth because I

30:47.480 --> 30:48.100
laughed and people

30:48.100 --> 30:48.720
looked up and I

30:48.720 --> 30:49.360
wondered what the

30:49.360 --> 30:51.000
hell I laughed when I

30:51.000 --> 30:51.680
read it because it was

30:51.680 --> 30:53.080
just so bizarrely funny

30:53.080 --> 30:55.180
so you got to be

30:55.180 --> 30:56.180
careful with what

30:56.180 --> 30:56.920
comes across there

30:56.920 --> 30:57.740
especially if you're

30:57.740 --> 30:58.660
giving it to your boss

30:58.660 --> 31:00.220
or a female co-worker

31:00.220 --> 31:01.360
and that happens to

31:01.360 --> 31:03.120
jump right on the

31:03.120 --> 31:03.600
screen you just

31:03.600 --> 31:04.440
happen to receive that

31:04.440 --> 31:05.180
email right then

31:05.180 --> 31:06.620
that's pretty awkward

31:06.620 --> 31:07.120
timing

31:07.120 --> 31:09.460
besides I already

31:09.460 --> 31:10.340
come bucket load so

31:10.340 --> 31:10.880
I don't really need

31:10.880 --> 31:11.240
that

31:11.240 --> 31:12.440
yeah so can you

31:12.440 --> 31:13.060
forward that to me

31:13.060 --> 31:14.680
yeah actually actually

31:14.680 --> 31:16.100
I will I well you

31:16.100 --> 31:17.120
mean forward you the

31:17.120 --> 31:18.580
email or forward you

31:18.580 --> 31:19.520
a sample of the

31:19.520 --> 31:20.640
actual product

31:20.640 --> 31:21.720
no no I've got

31:21.720 --> 31:22.340
plenty to provide

31:22.340 --> 31:22.740
I'm talking about

31:22.740 --> 31:23.020
the email

31:23.020 --> 31:24.160
got it no problem

31:24.160 --> 31:26.400
all right let's see

31:26.400 --> 31:28.200
last email this week

31:28.200 --> 31:31.020
is from replica

31:31.020 --> 31:32.340
replica says dear

31:32.340 --> 31:33.400
black ratchet and

31:33.400 --> 31:34.120
co-host

31:34.120 --> 31:35.900
all right well

31:35.900 --> 31:37.500
black ratchet is

31:37.500 --> 31:38.220
going to be played

31:38.220 --> 31:39.200
in this email by

31:39.200 --> 31:40.260
savant savant you're

31:40.260 --> 31:40.700
going to be black

31:40.700 --> 31:41.420
ratchet for this

31:41.420 --> 31:42.220
hello

31:42.220 --> 31:47.440
oh let's see

31:47.440 --> 31:49.800
debian gen 2 no

31:49.800 --> 31:51.700
gen 2 linux no

31:51.700 --> 31:52.900
gen 2 asterisk and

31:52.900 --> 31:53.660
ipods is that the

31:53.660 --> 31:53.900
joke

31:53.900 --> 31:55.240
yeah that's one

31:55.240 --> 31:56.220
all right dear

31:56.220 --> 31:56.840
black ratchet and

31:56.840 --> 31:58.380
co-host hey guys I

31:58.380 --> 31:59.260
just recently entered

31:59.260 --> 32:00.580
the t-shirt business

32:00.580 --> 32:01.800
and soon I'll be

32:01.800 --> 32:02.520
coming up with my

32:02.520 --> 32:03.560
own line of t-shirts

32:03.560 --> 32:04.260
once I get better

32:04.260 --> 32:05.600
with photoshop I

32:05.600 --> 32:06.220
was wondering if you

32:06.220 --> 32:06.820
guys know if it

32:06.820 --> 32:07.540
would be legal to

32:07.540 --> 32:09.800
make and sale sell

32:09.800 --> 32:11.380
my own linux slash

32:11.380 --> 32:13.160
unix t-shirts am I

32:13.160 --> 32:13.980
allowed to make a

32:13.980 --> 32:16.680
profit also has

32:16.680 --> 32:17.400
stank dog found

32:17.400 --> 32:18.220
someone to make the

32:18.220 --> 32:19.120
binary revolution

32:19.120 --> 32:20.840
t binary revolution

32:20.840 --> 32:22.060
shirts if he hasn't

32:22.060 --> 32:22.520
please have him

32:22.520 --> 32:23.300
shoot me an email and

32:23.300 --> 32:24.020
we can see if we can

32:24.020 --> 32:25.400
figure something out

32:25.400 --> 32:29.320
replica yes thank you

32:29.320 --> 32:30.300
for the offer but we

32:30.300 --> 32:32.060
do have the t-shirt

32:32.060 --> 32:34.080
hookup here locally

32:34.080 --> 32:34.980
with me because it's

32:34.980 --> 32:35.560
all going to have to

32:35.560 --> 32:36.100
go through me

32:36.100 --> 32:36.960
unfortunately because I

32:36.960 --> 32:37.700
come out of pocket

32:37.700 --> 32:38.400
with this like I do

32:38.400 --> 32:39.100
with every freaking

32:39.100 --> 32:40.740
thing else we do the

32:40.740 --> 32:41.360
only thing we really

32:41.360 --> 32:42.340
need is to get the art

32:42.340 --> 32:43.600
finalized so I am

32:43.600 --> 32:44.740
hopefully working with

32:44.740 --> 32:45.400
some people on that

32:45.400 --> 32:47.920
right now as far as

32:47.920 --> 32:49.880
can you sell linux

32:49.880 --> 32:52.800
shirts or are you

32:52.800 --> 32:53.500
allowed to make a

32:53.500 --> 32:57.420
profit I guess the long

32:57.420 --> 32:58.200
answer to this and

32:58.200 --> 32:59.200
tell me what you think

32:59.200 --> 32:59.940
about this the long

32:59.940 --> 33:01.080
answer is that

33:01.080 --> 33:02.220
technically you have to

33:02.220 --> 33:03.280
be careful that you

33:03.280 --> 33:03.800
don't use any

33:03.800 --> 33:04.880
copyrighted phrases

33:04.880 --> 33:06.260
logos images that

33:06.260 --> 33:08.560
sort of thing as you

33:08.560 --> 33:09.180
get a little bling

33:09.180 --> 33:10.200
bling message there

33:10.200 --> 33:11.960
yeah sorry about that

33:11.960 --> 33:13.460
get be careful that

33:13.460 --> 33:13.960
you don't use them

33:13.960 --> 33:14.760
you can't go out there

33:14.760 --> 33:15.720
and use one of the

33:15.720 --> 33:17.280
slogans that like you

33:17.280 --> 33:18.300
can't just go steal one

33:18.300 --> 33:20.400
from Jinx hackware or

33:20.400 --> 33:21.680
or hacker threads or

33:21.680 --> 33:22.440
one of you can't go out

33:22.440 --> 33:24.300
there and steal one at

33:24.300 --> 33:25.340
least not a copy written

33:25.340 --> 33:26.140
one if it's something

33:26.140 --> 33:27.760
that's like a command or

33:27.760 --> 33:28.400
something I don't I

33:28.400 --> 33:28.840
don't know what the

33:28.840 --> 33:29.820
answer that but the

33:29.820 --> 33:31.980
official answer that I'm

33:31.980 --> 33:32.640
going to give you is

33:32.640 --> 33:33.300
that you have to get a

33:33.300 --> 33:34.060
lawyer and do a proper

33:34.060 --> 33:35.260
copyright search on it

33:35.260 --> 33:36.380
to make sure you're free

33:36.380 --> 33:37.420
and clear that's the

33:37.420 --> 33:39.180
official answer now I

33:39.180 --> 33:39.780
know you're not going to

33:39.780 --> 33:42.440
do that I wouldn't I

33:42.440 --> 33:43.620
mean I would I wouldn't

33:43.620 --> 33:45.240
recommend otherwise but

33:45.240 --> 33:46.740
unofficially the stanks

33:46.740 --> 33:48.120
unofficial advice or

33:48.120 --> 33:49.060
unofficial opinion is

33:49.060 --> 33:50.380
that I would just do a

33:50.380 --> 33:51.540
cursory search make sure

33:51.540 --> 33:52.440
that there isn't already

33:52.440 --> 33:53.540
somebody out there making

33:53.540 --> 33:54.480
t-shirts with the same

33:54.480 --> 33:56.120
thing and make sure you're

33:56.120 --> 33:57.140
not ripping anybody else

33:57.140 --> 33:58.440
off I think that's that's

33:58.440 --> 33:59.440
good enough that in my

33:59.440 --> 34:00.360
that's what I would do if

34:00.360 --> 34:02.500
it were me so well he

34:02.500 --> 34:03.960
he specifically stated

34:03.960 --> 34:05.340
linux and unix shirts so

34:05.340 --> 34:06.980
I mean I would argue

34:06.980 --> 34:08.140
that since they're open

34:08.140 --> 34:09.860
source you should be able

34:09.860 --> 34:11.980
to reproduce them I mean

34:11.980 --> 34:13.720
but like tux for example

34:13.720 --> 34:15.100
I had I've heard conflicting

34:15.100 --> 34:16.220
stories some people saying

34:16.220 --> 34:17.520
that tux is copyrighted and

34:17.520 --> 34:18.380
other people say that it's

34:18.380 --> 34:20.800
not copyrighted I think it's

34:20.800 --> 34:24.080
under gpl the tux logo I'm

34:24.080 --> 34:25.280
not even going to venture a

34:25.280 --> 34:27.360
yeah so it's you have to do

34:27.360 --> 34:28.400
you have to go look it up I

34:28.400 --> 34:29.840
mean it sounds nice to say it

34:29.840 --> 34:33.500
was open source but I mean if

34:33.500 --> 34:34.720
you've got a linux joke

34:34.720 --> 34:36.680
wouldn't putting the words of

34:36.680 --> 34:38.320
a joke in print be disclosing

34:38.320 --> 34:38.760
the source

34:38.760 --> 34:43.180
yeah but you can copyright or

34:43.180 --> 34:44.780
at least trademark slogans and

34:44.780 --> 34:46.880
stuff like that so yeah that's

34:46.880 --> 34:47.080
true

34:47.080 --> 34:49.520
it's it's more than likely you're

34:49.520 --> 34:51.980
going to be fine but you just

34:51.980 --> 34:53.640
you just never know you never

34:53.640 --> 34:54.980
know some company may have

34:54.980 --> 34:57.760
their you know what is it does

34:57.760 --> 35:00.100
does Oracle have a trademark or

35:00.100 --> 35:03.960
on unbreakable or something like

35:03.960 --> 35:05.720
that unbreakable Linux or

35:05.720 --> 35:08.000
something no idea yeah I mean you

35:08.000 --> 35:09.020
just you just got to be careful

35:09.020 --> 35:10.300
because you may think that

35:10.300 --> 35:11.640
unbreakable Linux would be a cool

35:11.640 --> 35:13.680
shirt it sounds pretty cool but you

35:13.680 --> 35:15.040
may get some weird shit from

35:15.040 --> 35:16.520
Oracle I don't know I'm just

35:16.520 --> 35:18.620
making up an example I don't know

35:18.620 --> 35:20.060
if that's true or not the bottom

35:20.060 --> 35:21.800
line is just be careful and you

35:21.800 --> 35:22.740
should be okay if you're making

35:22.740 --> 35:24.160
up your own unique things your

35:24.160 --> 35:26.360
own clever slogans or whatever

35:26.360 --> 35:27.740
you should be okay for the most

35:27.740 --> 35:29.460
part but I would spend a good

35:29.460 --> 35:31.220
amount of time searching on your

35:31.220 --> 35:32.600
own just to make sure it's not

35:32.600 --> 35:33.440
already out there

35:33.440 --> 35:36.100
in worst case scenario even if

35:36.100 --> 35:37.100
someone does get pissed you're

35:37.100 --> 35:37.980
probably just going to see you

35:37.980 --> 35:39.280
from their lawyers I doubt very

35:39.280 --> 35:41.120
much that they would take you to

35:41.120 --> 35:42.180
court without at least telling you

35:42.180 --> 35:43.640
to stop what you're doing yeah

35:43.640 --> 35:46.740
you get a C&D and and we've

35:46.740 --> 35:49.540
gotten those before and usually

35:49.540 --> 35:51.080
just cooperate for the most part

35:51.080 --> 35:53.180
it's not a problem there you know

35:53.180 --> 35:54.800
if they've got a valid claim that

35:54.800 --> 35:55.840
is some people are basically

35:55.840 --> 35:57.680
ignored and told to fuck off but

35:57.680 --> 35:59.960
other people they've and you can

35:59.960 --> 36:01.420
we're not going to go any detail

36:01.420 --> 36:02.540
but you've seen some of the stuff

36:02.540 --> 36:04.200
that we get and how we respond to

36:04.200 --> 36:05.920
it and hey sometimes they're right

36:05.920 --> 36:07.320
we've done something or there's a

36:07.320 --> 36:09.400
copyright violation that we we have

36:09.400 --> 36:11.020
to just suck it up and deal with it

36:11.020 --> 36:13.740
whether we like it or not so be

36:13.740 --> 36:15.360
careful but for the most part yeah

36:15.360 --> 36:16.440
you're going to be safe and if you

36:16.440 --> 36:18.000
do get it you know they're going

36:18.000 --> 36:18.940
to it's going to be a cease and

36:18.940 --> 36:20.180
desist first of all and and then

36:20.180 --> 36:22.120
again unless you become any kind of

36:22.120 --> 36:23.560
larger scale you're not you're not

36:23.560 --> 36:24.660
a blip on the radar no one's even

36:24.660 --> 36:25.660
going to notice you for the most

36:25.660 --> 36:28.360
part unless you blatantly steal

36:28.360 --> 36:29.440
something that's well obviously

36:29.440 --> 36:31.860
well known yeah and scalp it it's

36:31.860 --> 36:34.600
outside of the Oracle Oracle con or

36:34.600 --> 36:35.760
something yeah if you're selling

36:35.760 --> 36:37.900
bootleg copies of Oracle 10g on

36:37.900 --> 36:39.860
burn to DVD out inside of the Oracle

36:39.860 --> 36:42.580
conference annual event you know

36:42.580 --> 36:45.040
yeah you might not get away with

36:45.040 --> 36:49.020
that well okay so that was quite a

36:49.020 --> 36:50.760
bit of stuff I had to catch up with

36:50.760 --> 36:53.200
emails and housekeeping and whatnot so

36:53.200 --> 36:54.620
let's jump into some main topic while

36:54.620 --> 36:55.960
we still got a decent amount of

36:55.960 --> 36:58.800
showtime left and my main topic for

36:58.800 --> 37:01.920
this week is inspired by let's see

37:01.920 --> 37:04.080
this is an article that I ripped out

37:04.080 --> 37:05.420
of a magazine it's a few months old

37:05.420 --> 37:09.160
now this is from September 06 but it's

37:09.160 --> 37:10.840
pretty much not something that's

37:10.840 --> 37:14.500
exactly timely it's called top 14

37:14.500 --> 37:17.600
security tactics or the online version

37:17.600 --> 37:19.480
of it oh my gosh what you're going to

37:19.480 --> 37:21.420
have to save me here is it tiny URL

37:21.420 --> 37:28.220
okay it's a tiny URL slash three seven

37:28.220 --> 37:34.740
lima kilo lima eight that's l-k-l-8

37:34.740 --> 37:38.460
37 l-k-l-8 yeah got it got it got it I

37:38.460 --> 37:39.720
was trying to I was trying to do my

37:39.720 --> 37:41.640
black graduate phonetic oh yeah no you're

37:41.640 --> 37:43.420
not you're only him for that email you're

37:43.420 --> 37:45.880
not him anymore now can't I just pretend

37:45.880 --> 37:49.840
yes you can pretend okay I don't want

37:49.840 --> 37:50.940
to hear any more Boy Scout stories

37:50.940 --> 37:53.620
though all right fair enough well the

37:53.620 --> 37:55.140
online version is just called the 14

37:55.140 --> 37:57.060
best ways to protect your computers

37:57.060 --> 37:58.820
same exact article two different

37:58.820 --> 38:01.260
titles because the one I pulled out was

38:01.260 --> 38:03.660
from Info World magazine so that's

38:03.660 --> 38:05.300
where the tiny URL will take you

38:05.300 --> 38:09.200
infoworld.com so I thought it'd be kind

38:09.200 --> 38:10.520
of interesting I've reason I pulled this

38:10.520 --> 38:13.700
article out is it's well 14 ways to

38:13.700 --> 38:14.800
protect your computer I guess we don't

38:14.800 --> 38:16.600
do top 10 lists anymore anything it's

38:16.600 --> 38:19.080
14 which seems like a strange number

38:19.080 --> 38:23.240
but whatever and let's see I guess the

38:23.240 --> 38:25.940
all it says at the beginning it goes

38:25.940 --> 38:27.120
down it goes into the list pretty

38:27.120 --> 38:28.940
quickly it just says no need for

38:28.940 --> 38:31.720
pricey complex complex security systems

38:31.720 --> 38:33.260
a few simple checks and management

38:33.260 --> 38:35.800
policies will have major impact forget

38:35.800 --> 38:38.280
expensive IDS is host space and unified

38:38.280 --> 38:39.900
threat management appliances here's how to

38:39.900 --> 38:41.560
really get the best security bang for

38:41.560 --> 38:44.200
your buck well we'll be the judge of

38:44.200 --> 38:46.320
that we'll decide that are you ready for

38:46.320 --> 38:51.640
this well do it do it do it all right

38:51.640 --> 38:53.440
actually I have to stop doing on there

38:53.440 --> 38:55.340
yeah Fred Lackey would be the actually

38:55.340 --> 38:57.280
the final say-so on this so we're just

38:57.280 --> 38:58.760
going to try to do our best to live up to

38:58.760 --> 39:00.980
the Lackey expertise it is absolutely

39:00.980 --> 39:05.420
okay number one prevent the installation or

39:05.420 --> 39:08.440
execution of unauthorized software or

39:08.440 --> 39:10.760
content learn what is running on your

39:10.760 --> 39:12.400
computers and why if you don't know

39:12.400 --> 39:14.980
what's on your systems you can't protect

39:14.980 --> 39:23.120
them adequately well duh yeah look up in

39:23.120 --> 39:25.680
the sky do you see the duh signal some of

39:25.680 --> 39:27.500
these some of these are going to be like

39:27.500 --> 39:28.560
that some of these are going to be really

39:28.560 --> 39:30.240
simple and straightforward that are common

39:30.240 --> 39:33.080
sense but people still aren't doing to

39:33.080 --> 39:34.840
be quite honest I mean people are still

39:34.840 --> 39:37.560
blindly running stuff no you're right

39:37.560 --> 39:39.580
well you know all right but see here's

39:39.580 --> 39:42.200
the thing like I know I get frustrated

39:42.200 --> 39:44.360
like I went off one time when we were

39:44.360 --> 39:46.200
doing the malware about how stupid people

39:46.200 --> 39:47.660
are for clicking and falling for this

39:47.660 --> 39:50.800
shit and I do believe that but let's be

39:50.800 --> 39:53.220
honest there's always even as saturated

39:53.220 --> 39:54.800
as the internet is and how many people

39:54.800 --> 39:57.760
have access there's there's always new

39:57.760 --> 40:01.080
people coming online there's always people

40:01.080 --> 40:02.520
who are learning it for the first time

40:02.520 --> 40:04.960
young people older people anybody there's

40:04.960 --> 40:07.520
always people coming online that don't

40:07.520 --> 40:09.100
know this stuff that have never done

40:09.100 --> 40:10.720
this stuff before they're just learning

40:10.720 --> 40:11.820
it so there's always going to be a

40:11.820 --> 40:14.840
constant influx of noobs to the

40:14.840 --> 40:18.480
interweb as a whole so who will get

40:18.480 --> 40:20.440
owned by the wallet inspector at least

40:20.440 --> 40:25.260
once exactly exactly but they'll get

40:25.260 --> 40:26.960
they'll be able to come load buckets if

40:26.960 --> 40:29.360
they order the proper medication yeah

40:29.360 --> 40:30.720
don't forget to forward that to me yeah

40:30.720 --> 40:32.360
yeah let me I should okay let me write

40:32.360 --> 40:36.460
that down forward buckets of come to

40:36.460 --> 40:40.300
savant there's another out of context

40:40.300 --> 40:43.940
one so yeah present prevent insulation

40:43.940 --> 40:45.760
or execution of authorize well I'll tell

40:45.760 --> 40:47.760
you what else oh actually this is going

40:47.760 --> 40:49.920
to segue or sidetrack into another topic

40:49.920 --> 40:52.700
I've been using Vista now for the past

40:52.700 --> 40:54.260
couple months since I've been on the

40:54.260 --> 40:58.140
show regularly so a little more Vista

40:58.140 --> 41:01.420
experience and that's one of the things

41:01.420 --> 41:03.600
that Vista does is it pops up for every

41:03.600 --> 41:05.480
little thing that wants to run or wants

41:05.480 --> 41:07.140
to execute saying are you sure do you

41:07.140 --> 41:08.520
want to do this do you authorize this

41:08.520 --> 41:10.640
application to run this application wants

41:10.640 --> 41:11.700
to connect to the internet this

41:11.700 --> 41:13.180
application wants to launch this other

41:13.180 --> 41:15.760
application it's a little bit annoying

41:15.760 --> 41:18.900
but it is better security so you know

41:18.900 --> 41:20.560
that's the thing about Microsoft is I

41:20.560 --> 41:22.480
got to you got to admit a little bit

41:22.480 --> 41:23.360
that they're in a catch-22 situation

41:23.360 --> 41:25.500
you know they're damned if they do and

41:25.500 --> 41:27.260
they're damned if they don't if they

41:27.260 --> 41:28.880
don't implement the security measures

41:28.880 --> 41:30.400
people talk about how insecure they are

41:30.400 --> 41:32.840
but when they do people bitch about

41:32.840 --> 41:34.500
what a hassle and how annoying it is

41:34.500 --> 41:37.300
well I just do you really think that

41:37.300 --> 41:39.380
that's gonna gonna do the trick I mean

41:39.380 --> 41:41.320
it's the same problem as the ULA right

41:41.320 --> 41:43.000
it's true people are gonna click through

41:43.000 --> 41:46.240
people are gonna click through but the

41:46.240 --> 41:48.860
ULA is like pages and pages of stuff

41:48.860 --> 41:51.480
this is a quick message so yes it will

41:51.480 --> 41:53.000
certainly still happen there's no debate

41:53.000 --> 41:54.880
there but hopefully not as bad because

41:54.880 --> 41:59.600
come on nobody reads ULA's I mean at

41:59.600 --> 42:01.600
some point it's going to come up in

42:01.600 --> 42:03.220
court a situation and maybe it already

42:03.220 --> 42:05.640
has it's going to come up in court where

42:05.640 --> 42:08.520
they're going to stop enforcing ULA's

42:08.520 --> 42:12.120
because they're becoming so ignored that

42:12.120 --> 42:14.840
they're no longer a true effective and

42:14.840 --> 42:20.040
reasonable way to enforce your license

42:20.040 --> 42:22.960
because they're so blatantly ignored that

42:22.960 --> 42:24.940
they could not possibly be upheld in

42:24.940 --> 42:26.680
court I see that day coming eventually

42:26.680 --> 42:30.740
it's probably not too far off yeah well

42:30.740 --> 42:32.320
then again our legal system you never

42:32.320 --> 42:35.440
know these days I guess but yeah

42:35.440 --> 42:37.100
actually you know what since I mentioned

42:37.100 --> 42:40.100
Vista I'll briefly sidetrack here one of

42:40.100 --> 42:42.260
the things I've noticed about Vista is

42:42.260 --> 42:46.280
it is incredibly self-healing like I've

42:46.280 --> 42:48.440
had a lot of little things happen with

42:48.440 --> 42:52.060
Vista like I had I had it power off one

42:52.060 --> 42:53.980
actually my power to the house went off

42:53.980 --> 42:55.400
for a second while I was installing

42:55.400 --> 42:58.900
something which is usually a clusterfuck

42:58.900 --> 43:02.000
right there but when it came back up it

43:02.000 --> 43:03.860
recognized it and uninstalled the

43:03.860 --> 43:05.720
previous version half what everything

43:05.720 --> 43:09.040
that it had done so far and then picked

43:09.040 --> 43:11.740
up and reinstalled from scratch what I was

43:11.740 --> 43:13.920
trying to do so it's got a lot of health

43:13.920 --> 43:15.560
self-healing in there there was one time

43:15.560 --> 43:17.520
where I had changed some network settings

43:17.520 --> 43:21.520
and it redetected and reset all of my

43:21.520 --> 43:25.520
network stuff up correctly without me

43:25.520 --> 43:27.840
really doing anything and there was

43:27.840 --> 43:29.400
something else similar to that as well

43:29.400 --> 43:30.620
where I think an application had

43:30.620 --> 43:33.520
crashed and it was able to detect why

43:33.520 --> 43:36.560
and offer an actual useful solution to

43:36.560 --> 43:38.720
solve it like running it in legacy mode

43:38.720 --> 43:40.460
or some other such nonsense I don't know

43:40.460 --> 43:42.860
but it worked so it's actually very

43:42.860 --> 43:44.600
self-healing which is one of the things I

43:44.600 --> 43:47.160
had not really seen so well in my

43:47.160 --> 43:49.960
testing running of the beta version so

43:49.960 --> 43:51.380
that's one cool thing about Vista I've

43:51.380 --> 43:55.000
been impressed with lately it's got lots

43:55.000 --> 43:58.120
of flair though I got to tell you it is

43:58.120 --> 44:01.720
loaded with flair unnecessary flair

44:01.720 --> 44:04.800
certainly there's no way in hell anybody

44:04.800 --> 44:07.160
should upgrade from Windows XP to Vista

44:07.160 --> 44:10.320
no way if it wasn't free I wouldn't have

44:10.320 --> 44:11.780
uploaded I wouldn't have upgraded either

44:11.780 --> 44:13.300
if I didn't already have a free license

44:13.300 --> 44:16.000
do you think that the flair is a direct

44:16.000 --> 44:18.640
response to those shitty ass Mac versus

44:18.640 --> 44:20.440
PC commercials that that Jimmy Fallon

44:20.440 --> 44:23.820
wannabe is doing you know it's um it's

44:23.820 --> 44:26.300
it's so so obvious that they've ripped

44:26.300 --> 44:30.360
off a lot of stuff from Mac so so obvious

44:30.360 --> 44:33.120
that they've copied a lot of stuff but um

44:33.120 --> 44:38.220
I don't think the flair necessarily is

44:38.220 --> 44:43.300
I think it's just I think they finally

44:43.300 --> 44:48.740
adopted video accelerators for use in an

44:48.740 --> 44:50.440
operating system now video accelerators

44:50.440 --> 44:52.740
are for gaming and maybe some video

44:52.740 --> 44:56.500
editing but do you really need a video

44:56.500 --> 44:59.020
accelerator for your operating system I

44:59.020 --> 45:00.800
mean come on is it really that important

45:00.800 --> 45:02.460
I mean it's don't get me wrong it's cool I

45:02.460 --> 45:03.760
like dragging Windows around that are

45:03.760 --> 45:06.760
transparent or watching my video play as

45:06.760 --> 45:08.540
I alt tab through them it's playing

45:08.540 --> 45:10.260
while it's sideways in the alt tab or

45:10.260 --> 45:11.920
Windows tab or whatever it's called which

45:11.920 --> 45:14.620
is kind of cool um they're they're neat

45:14.620 --> 45:15.660
and pretty and all but they're not

45:15.660 --> 45:18.320
exactly enhancing I'm not getting any

45:18.320 --> 45:21.320
additional um productivity or anything

45:21.320 --> 45:24.220
like that from them and if you don't

45:24.220 --> 45:26.260
have a video accelerator then it just

45:26.260 --> 45:28.540
basically runs like Windows XP with a

45:28.540 --> 45:30.760
little bit different shell I mean it's

45:30.760 --> 45:32.860
yeah there's certainly no reason to

45:32.860 --> 45:35.240
upgrade well real quick while we're

45:35.240 --> 45:36.480
talking about any user license

45:36.480 --> 45:38.060
agreements um if you ever read the

45:38.060 --> 45:42.120
generic Microsoft uh EULA for their

45:42.120 --> 45:44.220
software there's a section in there

45:44.220 --> 45:46.740
about Java support that says you know

45:46.740 --> 45:48.960
do not use Microsoft or Java products in

45:48.960 --> 45:50.740
life support machines or aircraft or

45:50.740 --> 45:52.660
anything that basically your life is on

45:52.660 --> 45:54.280
the line and then it goes on to say that

45:54.280 --> 45:56.060
they are not responsible for death or

45:56.060 --> 45:57.380
injuries as a result of their operating

45:57.380 --> 46:00.160
system well that should be I got a tiny

46:00.160 --> 46:02.880
roll on that um if you guys if you're

46:02.880 --> 46:04.840
ready is 30 that tiny earl dot com slash

46:04.840 --> 46:09.020
32 U is an uvula 86 and V is a vagina

46:09.020 --> 46:14.400
all right um well I would say don't use

46:14.400 --> 46:16.520
Java would be on this top 14 security

46:16.520 --> 46:19.680
tips if you ask me but we all know my

46:19.680 --> 46:23.260
my thoughts of Java so yeah all right

46:23.260 --> 46:25.520
let's see uh back to our list here as

46:25.520 --> 46:29.120
we sidetracked um number two don't let

46:29.120 --> 46:31.540
non-admin users be logged in as

46:31.540 --> 46:34.960
administrators or root what gee you

46:34.960 --> 46:40.780
think what no um this changes

46:40.780 --> 46:43.080
everything yeah I know man I that

46:43.080 --> 46:44.860
messes up completely how I admin my

46:44.860 --> 46:47.880
boxing I let my babysitter you know

46:47.880 --> 46:49.840
make herself a slash home when I'm

46:49.840 --> 46:51.640
not when I'm gone I let your babysitter

46:51.640 --> 46:54.120
make herself at home too slash home yeah

46:54.120 --> 46:58.240
oh okay uh let's see so that was pretty

46:58.240 --> 46:59.740
obvious there's not much to elaborate

46:59.740 --> 47:01.920
there you don't let non-admin users be

47:01.920 --> 47:04.760
yeah that's pretty dumb uh number three

47:04.760 --> 47:07.580
secure your email convert all incoming

47:07.580 --> 47:10.120
HTML content to plain text and block all

47:10.120 --> 47:12.600
file extensions by default except the

47:12.600 --> 47:16.380
handful or two you want to allow now

47:16.380 --> 47:21.020
this one I don't know um that's easier

47:21.020 --> 47:22.880
said than done in my opinion like one of

47:22.880 --> 47:24.320
the things that annoys the hell out of

47:24.320 --> 47:26.500
me with Microsoft Outlook is the fact

47:26.500 --> 47:27.900
that it does block every freaking

47:27.900 --> 47:29.920
extension known to mankind you have to

47:29.920 --> 47:31.780
trick your own Microsoft Outlook your

47:31.780 --> 47:34.320
own exchange server to pass a zip file

47:34.320 --> 47:36.520
across to a co-worker or something like

47:36.520 --> 47:39.840
you have to rename it dot jizz or

47:39.840 --> 47:41.580
something just to fool the damn thing

47:41.580 --> 47:43.720
into allowing you to move to send the

47:43.720 --> 47:45.020
file to somebody else because if God

47:45.020 --> 47:46.420
forbid you send a zip file that means

47:46.420 --> 47:49.180
it's a virus or something so it's

47:49.180 --> 47:51.320
annoying as all hell to do what this

47:51.320 --> 47:53.840
guy's suggesting secure yes no debate

47:53.840 --> 47:55.940
there but it's kind of one of those

47:55.940 --> 47:58.500
things about yeah your computer's

47:58.500 --> 48:02.640
secure if it's coded in a block of

48:02.640 --> 48:05.220
concrete yeah it's secure but there's a

48:05.220 --> 48:07.260
usability trade-off there and to me

48:07.260 --> 48:10.440
blocking every file extension I would

48:10.440 --> 48:12.680
say block things like VBS stuff like

48:12.680 --> 48:14.140
that some scripting languages that could

48:14.140 --> 48:16.640
execute on command on demand and maybe

48:16.640 --> 48:20.800
that's all he's referring to here but I

48:20.800 --> 48:22.160
don't know what do you think and the

48:22.160 --> 48:25.220
incoming HTML you can sanitize the HTML

48:25.220 --> 48:27.080
there are algorithms and applications

48:27.080 --> 48:29.680
that will do that as well I mean

48:29.680 --> 48:32.020
security it shouldn't be completely

48:32.020 --> 48:34.220
transparent I suppose I tend to agree

48:34.220 --> 48:36.800
with him I definitely use text only

48:36.800 --> 48:38.660
email but as far as locking out all

48:38.660 --> 48:40.660
extensions that's definitely best

48:40.660 --> 48:43.180
policy but I think you're right it

48:43.180 --> 48:46.300
could be a little restrictive well and

48:46.300 --> 48:49.780
again although I'm sorry go ahead 90% of

48:49.780 --> 48:52.480
people who use email in the corporate

48:52.480 --> 48:54.460
environment or at home or you know

48:54.460 --> 48:56.020
grandma sending pictures of her kittens

48:56.020 --> 48:58.420
who are kids or whatever I think that's

48:58.420 --> 49:01.060
probably a good policy or her titties I

49:01.060 --> 49:02.200
mean I wouldn't worry about running

49:02.200 --> 49:05.420
extensions like .text or you know unless

49:05.420 --> 49:06.980
there's another jpeg of death pictures or

49:06.980 --> 49:09.300
something I would say that they just be

49:09.300 --> 49:11.600
more diligent about which extensions are

49:11.600 --> 49:13.280
allowed but maybe there should be a

49:13.280 --> 49:14.920
wizard or something I don't know I don't

49:14.920 --> 49:17.040
know well and you know what else it is

49:17.040 --> 49:19.840
also it's it's about the audience too I

49:19.840 --> 49:21.620
mean yeah it depends on what you're

49:21.620 --> 49:24.760
doing and this comes back to you know

49:24.760 --> 49:27.080
we got to do the new 2600 came out this

49:27.080 --> 49:30.220
this week or two weeks ago I don't know

49:30.220 --> 49:32.340
and there was another article in there

49:32.340 --> 49:34.040
again I'm getting kind of tired of these

49:34.040 --> 49:37.900
articles there was one of three issues

49:37.900 --> 49:40.980
ago called what was it something about

49:40.980 --> 49:43.640
why administrators make policies or

49:43.640 --> 49:45.120
something like that and it lists all their

49:45.120 --> 49:48.620
policies and reasons behind them well he

49:48.620 --> 49:50.020
has some very good points in some of

49:50.020 --> 49:51.020
those things and if you're an

49:51.020 --> 49:52.300
administrator at a company and you're

49:52.300 --> 49:53.800
trying to protect your system then yeah

49:53.800 --> 49:56.560
you are going to be pretty harsh on what

49:56.560 --> 49:58.080
you allow and don't allow and I could see

49:58.080 --> 50:00.940
blocking a lot of this stuff but it also

50:00.940 --> 50:02.560
depends on what your business does if

50:02.560 --> 50:05.420
your business is of sending Excel

50:05.420 --> 50:07.720
spreadsheet information back and forth you

50:07.720 --> 50:09.340
don't want to block XLS so you're going to

50:09.340 --> 50:13.600
have to make some allowances I guess

50:13.600 --> 50:16.100
depending on your business use and what's

50:16.100 --> 50:17.720
going to be useful to you you can't block

50:17.720 --> 50:21.300
everything blindly you have I see I guess

50:21.300 --> 50:23.180
I'm I understand what he's saying and I

50:23.180 --> 50:24.580
agree with both you that it's certainly

50:24.580 --> 50:26.780
best case scenario you can't get any

50:26.780 --> 50:28.800
better than blocking everything but at

50:28.800 --> 50:31.060
the same time I've just always been a

50:31.060 --> 50:33.540
firm believer that education is the way to

50:33.540 --> 50:36.060
solve these things not rigid restrictions

50:36.060 --> 50:38.920
that make that unusable for the high

50:38.920 --> 50:40.480
percentage of users who do know what

50:40.480 --> 50:41.700
the fuck they're doing just to cover

50:41.700 --> 50:43.300
that three percent of fucktards that

50:43.300 --> 50:44.400
work at the company you know what I

50:44.400 --> 50:47.900
mean right so I understand why they

50:47.900 --> 50:50.000
make them in that article in 2600 which

50:50.000 --> 50:52.360
had a response the episode the issue

50:52.360 --> 50:54.300
after that about why we break rules and

50:54.300 --> 50:55.400
now there's another one in the current

50:55.400 --> 50:59.200
one I guess responding to the response

50:59.200 --> 51:01.760
and countering the counter I don't know

51:01.760 --> 51:04.880
what the hell it's about but anyway I

51:04.880 --> 51:06.380
certainly don't disagree that there are

51:06.380 --> 51:07.700
reasons that people make all these

51:07.700 --> 51:09.940
rules and actually this list kind of is

51:09.940 --> 51:11.180
those rules I guess if you want to

51:11.180 --> 51:12.800
think of it like that blocking

51:12.800 --> 51:15.500
attachments and sanitizing incoming

51:15.500 --> 51:17.880
HDL but what about sometimes you want

51:17.880 --> 51:20.080
HTML coming in sometimes you need HTML

51:20.080 --> 51:24.340
coming in that's true you know there's

51:24.340 --> 51:25.840
again there's solutions out there you

51:25.840 --> 51:27.960
can have things that that block it

51:27.960 --> 51:30.240
initially and says this contains HTML do

51:30.240 --> 51:31.900
you want to view it and if you know it's

51:31.900 --> 51:34.700
safe like you're expecting your I don't

51:34.700 --> 51:39.520
know your email yeah or email of your

51:39.520 --> 51:41.680
your cell phone bill or something is

51:41.680 --> 51:42.780
what I was going to say or something

51:42.780 --> 51:45.880
that you know is safe HTML from a

51:45.880 --> 51:49.600
company or a person you know so alright

51:49.600 --> 51:51.980
so that one's I think a little bit

51:51.980 --> 51:54.560
idealistic an unrealistic but it's it's

51:54.560 --> 51:58.400
certainly valid and valuable number four

51:58.400 --> 52:00.900
oh it's important to remember that

52:00.900 --> 52:02.780
they're talking about how to not spend

52:02.780 --> 52:05.700
$10,000 on a hardware appliance when

52:05.700 --> 52:06.840
this is something you should be doing

52:06.840 --> 52:08.140
first and I think that that still

52:08.140 --> 52:11.280
applies well that's true but I guess

52:11.280 --> 52:12.760
if you're a smaller businesses but

52:12.760 --> 52:14.680
large businesses should spring the

52:14.680 --> 52:16.520
money forward obviously on the on that

52:16.520 --> 52:19.920
and the real small ones probably aren't

52:19.920 --> 52:21.180
so there's not you know there's I don't

52:21.180 --> 52:22.740
think there is much in between you're

52:22.740 --> 52:24.080
either a small business who you're

52:24.080 --> 52:25.760
going to let it all go or you're a big

52:25.760 --> 52:26.720
business and you're going to block

52:26.720 --> 52:28.940
everything with your appliances I don't

52:28.940 --> 52:30.140
know how many people fall into that

52:30.140 --> 52:31.580
middle ground probably more than I'm

52:31.580 --> 52:34.580
giving credit for I don't know anyway

52:34.580 --> 52:38.720
number four secure your passwords no

52:38.720 --> 52:42.520
shit Sherlock no require long passwords

52:42.520 --> 52:45.360
10 character or longer for normal users

52:45.360 --> 52:47.860
15 characters or longer for admin

52:47.860 --> 52:50.920
accounts implement account lockout if

52:50.920 --> 52:55.400
even if even with only wow that's an

52:55.400 --> 52:58.980
awful sentence if even only with only a

52:58.980 --> 53:01.520
one-minute lockout on Windows disable

53:01.520 --> 53:03.940
LM password hashes on Unix Linux use

53:03.940 --> 53:06.260
the newer crypt three hashes MD five

53:06.260 --> 53:08.420
style hashes or even better be crypt

53:08.420 --> 53:11.060
hashes if your OS supports it well

53:11.060 --> 53:16.120
MD five is nothing so again ideally sure

53:16.120 --> 53:18.120
longer passwords stronger passwords are

53:18.120 --> 53:20.060
better but Betty in accounting wants to

53:20.060 --> 53:21.620
make her password whatever her cat's

53:21.620 --> 53:25.000
name is or her grandchild you know what I

53:25.000 --> 53:27.840
mean well then Betty in accounting

53:27.840 --> 53:29.560
should use the past phrase instead of a

53:29.560 --> 53:31.840
password like mitten is the cutest

53:31.840 --> 53:34.320
fucking cat ever I hear really strong

53:34.320 --> 53:36.280
password and it'd be easy to remember

53:36.280 --> 53:41.040
absolutely agree on this 100% 100% it's

53:41.040 --> 53:43.540
kind of um I don't think I have to admit I

53:43.540 --> 53:44.840
don't think I've ever seen in practice

53:44.840 --> 53:47.880
though password requirements that differ

53:47.880 --> 53:50.340
based on use 10 characters for normal

53:50.340 --> 53:52.740
users 15 for admin accounts you can

53:52.740 --> 53:55.160
state that as a policy but I don't

53:55.160 --> 53:56.460
think I've ever seen that technically

53:56.460 --> 53:57.960
enforced I don't think I've ever seen

53:57.960 --> 54:00.460
an error that says warning you're an

54:00.460 --> 54:02.940
admin and your password must be 15

54:02.940 --> 54:05.080
characters where it's smart enough to

54:05.080 --> 54:06.420
tell one from the other have you ever

54:06.420 --> 54:09.040
seen that before I mean I think it's

54:09.040 --> 54:10.880
doable some third-party web application

54:11.420 --> 54:13.980
installing some form or something maybe

54:13.980 --> 54:17.040
but even then that was a big if the

54:17.040 --> 54:18.840
developers were that security minded but

54:18.840 --> 54:20.900
even then I don't think in sort of any

54:20.900 --> 54:22.400
sort of general distribution software

54:22.400 --> 54:24.680
you know what though that that is not

54:24.680 --> 54:28.040
that's damn easy actually to implement

54:28.040 --> 54:29.400
technically I mean there's nothing to

54:29.400 --> 54:31.640
that designate what's an admin account

54:31.640 --> 54:34.000
or not and when you accept the password

54:34.000 --> 54:36.060
check is it admin then say it has

54:36.060 --> 54:37.760
different criteria actually I think

54:37.760 --> 54:38.860
that's something that should be done

54:38.860 --> 54:40.620
more often I think I like that a lot

54:40.620 --> 54:43.860
again Betty in accounting is going to

54:43.860 --> 54:45.320
be a little miffed at it but she's

54:45.320 --> 54:46.720
going to have to adapt and once again

54:46.720 --> 54:48.020
it comes back to what I said earlier

54:48.020 --> 54:50.660
it's education people need to know

54:50.660 --> 54:53.300
this now there's also and this is the

54:53.300 --> 54:55.400
biggest example for that delicate

54:55.400 --> 54:57.240
balance if you make them change their

54:57.240 --> 54:58.980
password every week with those

54:58.980 --> 55:00.760
policies of making it they're going to

55:00.760 --> 55:01.920
run out of ideas they're going to

55:01.920 --> 55:03.360
start reusing passwords they're going

55:03.360 --> 55:05.700
to start making easier passwords out of

55:05.700 --> 55:08.300
frustration agree completely you got

55:08.300 --> 55:10.100
to have that balance so I think like

55:10.100 --> 55:12.260
what common what I've seen very

55:12.260 --> 55:16.180
commonly is myself for an example is

55:16.180 --> 55:18.500
we change every I think four months

55:18.500 --> 55:23.320
and we require mixed case numbers and

55:23.320 --> 55:24.980
special at least one number at least one

55:24.980 --> 55:27.800
special character and mixed case and

55:27.800 --> 55:29.620
all the passwords with a minimum of

55:29.620 --> 55:31.660
eight characters I think it is I prefer

55:31.660 --> 55:33.620
longer but we go with eight for the most

55:33.620 --> 55:36.260
part and I think that's a pretty good

55:36.260 --> 55:38.480
balance I'll tell you what most of those

55:38.480 --> 55:40.220
passwords are though they're fives

55:40.220 --> 55:42.560
instead of s's threes instead of e's

55:42.560 --> 55:44.160
and an exclamation point at the end

55:44.160 --> 55:46.260
actually I do not fall into the I

55:46.260 --> 55:48.100
sometimes I will mix them up but I

55:48.100 --> 55:50.060
don't have any regular I don't always

55:50.060 --> 55:52.660
change my e's to threes I don't always

55:52.660 --> 55:55.200
change my one eyes to ones but I will

55:55.200 --> 55:56.360
occasionally you got to keep that

55:56.360 --> 55:58.620
mixed up too because yes you you don't

55:58.620 --> 55:59.940
want to make a pattern it's funny you

55:59.940 --> 56:01.300
mentioned because that's actually an

56:01.300 --> 56:02.600
article that I'm finally getting around

56:02.600 --> 56:04.560
to writing again now that I have some

56:04.560 --> 56:06.000
time and that's one of the articles I

56:06.000 --> 56:09.300
was working on but anyway let's kind of

56:09.300 --> 56:10.400
catch up here because we're running

56:10.400 --> 56:12.540
not short yet but we're starting to run

56:12.540 --> 56:15.280
out of time remember number five is

56:15.280 --> 56:16.560
actually I think one of the other best

56:16.560 --> 56:20.380
ones it's called well it says number

56:20.380 --> 56:23.660
five practice deny by default and least

56:23.660 --> 56:26.260
privilege whenever possible when

56:26.260 --> 56:27.860
developing least privileged security

56:27.860 --> 56:29.860
policies use role-based security instead

56:29.860 --> 56:31.760
of one such as instead of one IT

56:31.760 --> 56:33.320
security group you should have a group

56:33.320 --> 56:36.800
for each IT role yeah that's a little

56:36.800 --> 56:38.460
overkill but the bottom line of least

56:38.460 --> 56:39.920
privilege whenever possible least

56:39.920 --> 56:42.380
privilege is I think absolutely on

56:42.380 --> 56:44.780
point don't give anybody any more

56:44.780 --> 56:47.480
access than they need absolutely need

56:47.480 --> 56:49.380
yeah yeah and and especially like

56:49.380 --> 56:50.600
there's a really good example of that

56:50.600 --> 56:53.020
is any type of EAP software any type of

56:53.020 --> 56:57.120
enterprise level system of any kind

56:57.120 --> 56:58.020
where you're rolling it out

56:58.020 --> 57:00.320
accountants only need to access what

57:00.320 --> 57:02.440
accountants need to access so you can

57:02.440 --> 57:03.620
make a role and that's what he's

57:03.620 --> 57:06.080
saying by these role-based stuff and I

57:06.080 --> 57:07.720
look at that this decoder calling me

57:07.720 --> 57:10.080
in the middle of the show his call

57:10.080 --> 57:11.380
coming on the other line and I'm not

57:11.380 --> 57:12.320
going to answer it can you still hear

57:12.320 --> 57:15.540
me okay by the way yeah okay you're

57:15.540 --> 57:16.880
going to get voxed for a second as

57:16.880 --> 57:18.760
decoder there he goes he hung up

57:18.760 --> 57:20.960
decoder is on this week's episode of

57:20.960 --> 57:22.600
binary revolution radio unbeknownst to

57:22.600 --> 57:24.860
him but I was saying that's what he's

57:24.860 --> 57:25.980
saying by roles if you're in

57:25.980 --> 57:26.960
accounting you have an accounting

57:26.960 --> 57:28.160
role set up and they're only allowed

57:28.160 --> 57:31.440
access to screens a b c d and e whereas

57:31.440 --> 57:34.600
people over in the ass wiping

57:34.600 --> 57:36.400
department I don't know they only get

57:36.400 --> 57:39.300
access to screen 7 to order more TP I

57:39.300 --> 57:41.340
don't know whatever the case may be and

57:41.340 --> 57:43.120
only give them access to what they need

57:43.120 --> 57:45.100
and what they use now there's one

57:45.100 --> 57:46.520
caveat I'm going to throw into this

57:46.520 --> 57:49.080
that frustrates me as a programmer and

57:49.080 --> 57:51.360
now he's calling my cell phone decoder I'm

57:51.360 --> 57:52.300
going to have to get back to you there

57:52.300 --> 57:55.340
buddy one caveat to that is as a

57:55.340 --> 57:57.300
programmer I get frustrated if I get

57:57.300 --> 57:59.380
clumped into one of those groups and I

57:59.380 --> 58:01.940
need access to some other tables or you

58:01.940 --> 58:03.740
know somebody from accounting calls me

58:03.740 --> 58:05.460
and wants me to check something or fix

58:05.460 --> 58:06.500
something for him but I don't have

58:06.500 --> 58:08.440
access to accounting because they only

58:08.440 --> 58:10.300
gave me least privilege you got to make

58:10.300 --> 58:12.000
some exceptions there for staff you got

58:12.000 --> 58:13.440
to extend certain levels of trust to

58:13.440 --> 58:16.440
your IT group your IT people but

58:16.440 --> 58:18.380
definitely for users I'm on board with

58:18.380 --> 58:20.380
that 110 percent

58:20.380 --> 58:23.700
you know

58:23.700 --> 58:26.420
let's just go on to the next one so it

58:26.420 --> 58:27.960
pretty much goes into the same thing

58:27.960 --> 58:31.420
okay six is define and enforce security

58:31.420 --> 58:33.460
domains who needs access to what what

58:33.460 --> 58:35.600
types of traffic are legitimate answer

58:35.600 --> 58:36.840
these questions and then design

58:36.840 --> 58:39.140
perimeter defenses take baselines and

58:39.140 --> 58:41.560
note abnormal traffic well you talk

58:41.560 --> 58:42.440
about that and I'm going to have some

58:42.440 --> 58:42.760
ice tea

58:42.760 --> 58:46.080
absolutely okay well it reminds me of when

58:46.080 --> 58:47.820
I worked at the my previous company is a

58:47.820 --> 58:51.480
tech janitor we had a huge problem with

58:51.480 --> 58:52.740
the majority of the staff and we're

58:52.740 --> 58:54.240
talking 200 people in the house

58:54.240 --> 58:56.340
running off of I think 61 it wasn't a

58:56.340 --> 58:59.360
fat pipe but anyway they would always go

58:59.360 --> 59:01.260
to my space just constantly like

59:01.260 --> 59:03.120
majority of the traffic my space would

59:03.120 --> 59:05.840
get 60 to 80 percent more hits than our

59:05.840 --> 59:07.840
home page would you know from internal

59:07.840 --> 59:10.740
use and the problem with my space is

59:10.740 --> 59:12.160
that it does cater the lowest common

59:12.160 --> 59:13.680
denominator people are used to a

59:13.680 --> 59:15.820
certain level of idiocy and so things

59:15.820 --> 59:17.940
like getting my space fished or getting

59:17.940 --> 59:21.080
trojans set along the lines it may seem

59:21.080 --> 59:24.540
like benign activity but really if if

59:24.540 --> 59:26.680
betting accounting uses the same profile

59:26.680 --> 59:29.460
password as she does for your w2 forms

59:29.460 --> 59:33.620
then there's a real problem here she

59:33.620 --> 59:34.840
shouldn't be checking from work in the

59:34.840 --> 59:36.840
first place and I know that's kind of a

59:36.840 --> 59:40.000
sort of off topic red but really deny by

59:40.000 --> 59:42.060
default least privilege wherever possible

59:42.060 --> 59:44.340
in the security domain you have to

59:44.340 --> 59:46.600
consider that everything is a threat

59:46.600 --> 59:48.480
unless you've specifically analyzed and

59:48.480 --> 59:50.300
assessed it beforehand and have

59:50.300 --> 59:53.200
established that it's okay to this

59:53.200 --> 59:56.560
extent but it's just blatant wild

59:56.560 --> 59:58.940
rampaging activity on your network is

59:58.940 --> 01:00:00.820
going to end up in more security

01:00:00.820 --> 01:00:05.600
breaches than than not yeah I you know

01:00:05.600 --> 01:00:07.260
the easy answer that is just everybody

01:00:07.260 --> 01:00:09.120
should block my space that that's at the

01:00:09.120 --> 01:00:12.180
end well I think we did a DNS poison

01:00:12.180 --> 01:00:14.120
locally and redirected it to mcdonald's

01:00:14.120 --> 01:00:17.560
there you go let's see number seven

01:00:17.560 --> 01:00:19.580
encrypt all confidential data whenever

01:00:19.580 --> 01:00:21.800
possible especially on portable computers

01:00:21.800 --> 01:00:23.400
and media there's no excuse for not

01:00:23.400 --> 01:00:25.960
doing this the bad PR you'll get blah

01:00:25.960 --> 01:00:29.020
blah blah encryption very good thing

01:00:29.020 --> 01:00:30.640
absolutely no debating there's no

01:00:30.640 --> 01:00:32.300
denying that's got to be a great

01:00:32.300 --> 01:00:34.920
practice I think I've gone into I think

01:00:34.920 --> 01:00:36.600
verbal and I have talked about this

01:00:36.600 --> 01:00:38.100
before because verbal also very much

01:00:38.100 --> 01:00:41.140
agrees with this and playing devil's

01:00:41.140 --> 01:00:43.140
advocate to him my defense or my

01:00:43.140 --> 01:00:45.420
reasoning anyway is that encryption is

01:00:45.420 --> 01:00:46.960
still not easy enough for your everyday

01:00:46.960 --> 01:00:49.480
user to use it still hasn't been

01:00:49.480 --> 01:00:51.840
incorporated easily enough into the

01:00:51.840 --> 01:00:53.440
outlook and the Thunderbird and the

01:00:53.440 --> 01:00:55.060
different clients that they're using

01:00:55.060 --> 01:00:58.200
some of it is you know they've made it

01:00:58.200 --> 01:01:00.540
very easily very easy for you to set up

01:01:00.540 --> 01:01:02.560
SSL on your website and when you

01:01:02.560 --> 01:01:04.640
somebody browses to it redirects it

01:01:04.640 --> 01:01:06.120
encrypts all that traffic so that you

01:01:06.120 --> 01:01:07.600
can securely purchase things through

01:01:07.600 --> 01:01:11.100
the web or whatever but it's not that

01:01:11.100 --> 01:01:13.340
level on other applications other than

01:01:13.340 --> 01:01:17.540
online other than browsers right well

01:01:17.540 --> 01:01:19.460
there's the GPG plug-in for Thunderbird

01:01:19.460 --> 01:01:20.640
that if you haven't checked out you're

01:01:20.640 --> 01:01:21.900
really ought to because it makes the

01:01:21.900 --> 01:01:24.880
whole process pretty easy yeah outlet

01:01:24.880 --> 01:01:28.480
doesn't have any free easily accessible

01:01:28.480 --> 01:01:31.760
or at least corporate aware suite like

01:01:31.760 --> 01:01:34.280
one thing I've noticed with management

01:01:34.280 --> 01:01:35.520
types is that if you throw the word

01:01:35.520 --> 01:01:37.060
free or open source in front of them

01:01:37.060 --> 01:01:38.740
they automatically assume cheap and

01:01:38.740 --> 01:01:40.920
unreliable yeah and if something's free

01:01:40.920 --> 01:01:43.120
then how could it be any good and so

01:01:43.120 --> 01:01:45.080
you might find a lot of apprehension

01:01:45.080 --> 01:01:46.980
there why would we use a free product

01:01:46.980 --> 01:01:48.400
to encrypt our most important data

01:01:48.400 --> 01:01:50.700
let's just not encrypt it at all right

01:01:50.700 --> 01:01:53.100
well any kind of encryption is better

01:01:53.100 --> 01:01:55.780
than no encryption first of all right but

01:01:55.780 --> 01:01:57.360
yeah and actually that mentality is

01:01:57.360 --> 01:01:59.540
starting to change it's probably for the

01:01:59.540 --> 01:02:01.400
bad reasons the reason being they're

01:02:01.400 --> 01:02:02.780
saving money they're being penny

01:02:02.780 --> 01:02:05.380
pinchers but that's a whole nother

01:02:05.380 --> 01:02:08.120
topic all together I guess but one

01:02:08.120 --> 01:02:09.860
other thing kind of related to this and

01:02:09.860 --> 01:02:11.320
maybe this would make a show in and of

01:02:11.320 --> 01:02:15.180
itself is the the new onset of these

01:02:15.180 --> 01:02:20.400
new encrypted file systems and things

01:02:20.400 --> 01:02:21.820
that are integrated that will encrypt

01:02:21.820 --> 01:02:24.960
everything on your hard drive completely

01:02:24.960 --> 01:02:28.580
authenticated with just you logging in

01:02:28.580 --> 01:02:30.820
one time and if anybody were to ever get

01:02:30.820 --> 01:02:32.260
it they'd never be able to get it

01:02:32.260 --> 01:02:35.100
unencrypted there's been a lot of

01:02:35.100 --> 01:02:36.800
breakthroughs in that and again we could

01:02:36.800 --> 01:02:38.100
go into that in more detail but I think

01:02:38.100 --> 01:02:39.960
I think we'll just go along with

01:02:39.960 --> 01:02:42.480
encryption is good certainly we support

01:02:42.480 --> 01:02:45.520
that and the easier it becomes for your

01:02:45.520 --> 01:02:48.080
everyday Thelma in accounting or

01:02:48.080 --> 01:02:50.220
grandmother to use then it will

01:02:50.220 --> 01:02:54.020
definitely change a lot of things number

01:02:54.020 --> 01:02:56.900
eight update patch management for OS's

01:02:56.900 --> 01:02:58.960
and all applications have you patched

01:02:58.960 --> 01:03:00.440
macromedia flash real player and

01:03:00.440 --> 01:03:03.640
adobe acrobat lately yeah I guess you

01:03:03.640 --> 01:03:05.440
can't really debate well actually I

01:03:05.440 --> 01:03:07.460
could think of one debate for that but

01:03:07.460 --> 01:03:10.520
I pretty much agree with this there's

01:03:10.520 --> 01:03:11.740
something to be said about not

01:03:11.740 --> 01:03:14.760
upgrading to things right away because

01:03:14.760 --> 01:03:16.020
there's sometimes bugs in there

01:03:16.020 --> 01:03:17.100
sometimes they're not backwards

01:03:17.100 --> 01:03:20.140
compatible ie 7 is a great example a

01:03:20.140 --> 01:03:21.300
lot of people a lot of corporations

01:03:21.300 --> 01:03:22.600
aren't moved to that yet because it's

01:03:22.600 --> 01:03:24.020
not backwards compatible with a lot

01:03:24.020 --> 01:03:26.500
of their applications doesn't have

01:03:26.500 --> 01:03:27.920
good legacy support so there's

01:03:27.920 --> 01:03:28.860
something to be said about not

01:03:28.860 --> 01:03:30.340
always upgrading immediately but for

01:03:30.340 --> 01:03:31.820
the most part the benefits are going

01:03:31.820 --> 01:03:33.320
to outweigh that never upgrade to a

01:03:33.320 --> 01:03:38.140
beta but don't most applications now

01:03:38.140 --> 01:03:40.900
call home and tell you that there's

01:03:40.900 --> 01:03:41.900
an upgrade available they've been

01:03:41.900 --> 01:03:44.200
really good about that but yeah it's

01:03:44.200 --> 01:03:45.480
becoming more and more common for

01:03:45.480 --> 01:03:47.020
sure yeah that that's definitely a

01:03:47.020 --> 01:03:48.300
great thing because the other thing

01:03:48.300 --> 01:03:49.400
is human nature you're going to

01:03:49.400 --> 01:03:50.620
forget about it quite frankly

01:03:50.620 --> 01:03:52.260
especially when you've got tons of

01:03:52.260 --> 01:03:55.520
applications installed one you know

01:03:55.520 --> 01:03:57.700
okay I'm going to rant for a mini

01:03:57.700 --> 01:03:59.860
second here but most people that I've

01:03:59.860 --> 01:04:01.600
ever had those calls of my neighbors

01:04:01.600 --> 01:04:04.000
hey will you fix my computer those

01:04:04.000 --> 01:04:06.900
fucking calls it never fails it never

01:04:06.900 --> 01:04:09.160
ever fails that I always got that

01:04:09.160 --> 01:04:10.460
little yellow shield on the bottom

01:04:10.460 --> 01:04:12.460
corner you've got the Java update thing

01:04:12.460 --> 01:04:13.600
next to what you've got the fucking

01:04:13.600 --> 01:04:15.520
Dell support logo you've got 14

01:04:15.520 --> 01:04:18.100
important updates pending nobody does

01:04:18.100 --> 01:04:19.740
this shit I mean I'm sure our

01:04:19.740 --> 01:04:21.300
listeners who are tech savvy enough to

01:04:21.300 --> 01:04:23.440
actually care to click a radio show do

01:04:23.440 --> 01:04:26.100
but goddamn like it's one of those

01:04:26.100 --> 01:04:27.820
things where you know you could use

01:04:27.820 --> 01:04:29.640
Kazaa and your fucking peer-to-peer

01:04:29.640 --> 01:04:32.020
applications all day and night for the

01:04:32.020 --> 01:04:34.900
most part as long as your shit patched I

01:04:34.900 --> 01:04:36.420
mean the people are still getting caught

01:04:36.420 --> 01:04:38.100
with you know blaster or code red or

01:04:38.100 --> 01:04:39.700
something because they're downloading

01:04:39.700 --> 01:04:41.880
their goddamn Britney Spears naked videos

01:04:41.880 --> 01:04:44.040
off the fucking peer-to-peer and they're

01:04:44.040 --> 01:04:46.740
they're not running their updates okay

01:04:46.740 --> 01:04:48.940
yeah the you know that goes back to

01:04:48.940 --> 01:04:49.880
I need another piece of gum hold on

01:04:49.880 --> 01:04:52.600
that goes back to what you said earlier

01:04:52.600 --> 01:04:54.360
about there's always new people but you

01:04:54.360 --> 01:04:56.260
know what that to me falls more under

01:04:56.260 --> 01:04:59.860
just pure laziness and sometimes it's

01:04:59.860 --> 01:05:01.700
also why I never do side work like that

01:05:01.700 --> 01:05:03.880
anymore I might help out a friend or

01:05:03.880 --> 01:05:05.540
family that asks or something but for

01:05:05.540 --> 01:05:08.340
most part to me they learn the lesson

01:05:08.340 --> 01:05:11.000
better if I tell them that oh the

01:05:11.000 --> 01:05:12.920
solution is and sometimes it's better

01:05:12.920 --> 01:05:15.600
to lie sometimes it's easier to say

01:05:15.600 --> 01:05:18.180
you know what you you've gotten a

01:05:18.180 --> 01:05:19.660
virus you've gotten a malware you've

01:05:19.660 --> 01:05:21.200
gotten spyware and there's no way to

01:05:21.200 --> 01:05:22.760
clean it up you have to reformat your

01:05:22.760 --> 01:05:24.700
drive and start over that's the best

01:05:24.700 --> 01:05:26.220
way to drill the message home because

01:05:26.220 --> 01:05:28.840
then they realize oh I better be more

01:05:28.840 --> 01:05:30.660
careful next time because I just lost

01:05:30.660 --> 01:05:33.520
everything right so sometimes that you

01:05:33.520 --> 01:05:35.100
got to play the tough love when it comes

01:05:35.100 --> 01:05:39.420
to that my opinion of course no I agree

01:05:39.420 --> 01:05:42.440
completely number nine is that we're

01:05:42.440 --> 01:05:44.500
wrong number nine implement anti-virus

01:05:44.500 --> 01:05:46.980
anti-spam and anti spyware tools on the

01:05:46.980 --> 01:05:50.320
gateway and or at the host level well

01:05:50.320 --> 01:05:51.900
yeah that's pretty straightforward I can't

01:05:51.900 --> 01:05:55.340
argue with that one no be careful though

01:05:55.340 --> 01:05:57.000
and we've gone into this in the show in

01:05:57.000 --> 01:06:00.320
the past you know with with some of

01:06:00.320 --> 01:06:01.700
these gateways and actually not even

01:06:01.700 --> 01:06:03.280
with the gateway even on your on your

01:06:03.280 --> 01:06:06.500
client side sometimes you get false

01:06:06.500 --> 01:06:08.000
positives you're going to lose email

01:06:08.000 --> 01:06:09.880
that's not really spam just because it

01:06:09.880 --> 01:06:11.560
triggers certain keywords and stuff so

01:06:11.560 --> 01:06:12.820
it's going to happen occasionally but

01:06:12.820 --> 01:06:15.720
the the gains far outweigh the risks in

01:06:15.720 --> 01:06:21.520
that situation I think number 10 this

01:06:21.520 --> 01:06:25.040
one could be number 10 is embrace

01:06:25.040 --> 01:06:28.280
security by obscurity rename your admin

01:06:28.280 --> 01:06:30.140
and root accounts to something else don't

01:06:30.140 --> 01:06:32.140
have an account called exchange admin

01:06:32.140 --> 01:06:34.520
don't give your file server name such as

01:06:34.520 --> 01:06:38.060
fs1 exchange one or gateway serve one put

01:06:38.060 --> 01:06:39.960
services on non-default ports when you

01:06:39.960 --> 01:06:44.380
can you can move ssh to 30456 or blah

01:06:44.380 --> 01:06:46.800
blah blah blah blah blah I think we get the

01:06:46.800 --> 01:06:51.840
point there now you know hackers for years

01:06:51.840 --> 01:06:53.980
have screamed about never relying on

01:06:53.980 --> 01:06:55.780
security for obscurity and I've always

01:06:55.780 --> 01:06:57.360
disagreed with it and let me explain

01:06:57.360 --> 01:07:00.060
why it's because everything that he

01:07:00.060 --> 01:07:01.900
suggested to do here is perfectly valid

01:07:01.900 --> 01:07:05.660
security by obscurity in and of itself of

01:07:05.660 --> 01:07:07.280
course is terrible you can't expect your

01:07:07.280 --> 01:07:09.900
your software or anything to be secure

01:07:09.900 --> 01:07:11.440
just because you don't document it

01:07:11.440 --> 01:07:13.300
somewhere publicize it that's there if

01:07:13.300 --> 01:07:14.540
that's your only measure of security

01:07:14.540 --> 01:07:16.920
that's terrible but you should always

01:07:16.920 --> 01:07:19.800
basically what I interpret this is take

01:07:19.800 --> 01:07:23.140
everything off of default yep that's

01:07:23.140 --> 01:07:24.320
pretty much what I'm saying when they

01:07:24.320 --> 01:07:26.200
say of security through obscurity yeah

01:07:26.200 --> 01:07:28.580
move it off of whatever default port it

01:07:28.580 --> 01:07:30.660
uses change the default username change

01:07:30.660 --> 01:07:34.160
your default passwords etc etc the way

01:07:34.160 --> 01:07:36.460
that should read is never rely on only

01:07:36.460 --> 01:07:38.360
security through obscurity but

01:07:38.360 --> 01:07:40.420
definitely implemented security is a

01:07:40.420 --> 01:07:41.840
layered process you need to have as

01:07:41.840 --> 01:07:44.700
many defense in depth rings as possible

01:07:44.700 --> 01:07:47.220
and you know that's a cliche you hear a

01:07:47.220 --> 01:07:49.540
lot in security world secure in the

01:07:49.540 --> 01:07:52.340
technical security world is layered

01:07:52.340 --> 01:07:55.060
security but it's so accurate and so

01:07:55.060 --> 01:07:58.180
true it really is it's one of those

01:07:58.180 --> 01:08:01.360
fucking dusting is like the the bottom

01:08:01.360 --> 01:08:03.860
line I mean this is if you're serious

01:08:03.860 --> 01:08:05.340
about securing your shit and if you're

01:08:05.340 --> 01:08:06.700
a corporation if you're a company with

01:08:06.700 --> 01:08:08.640
something to lose then that is step

01:08:08.640 --> 01:08:10.960
number one after you know enforce good

01:08:10.960 --> 01:08:15.520
passwords you know I even layer layers of

01:08:15.520 --> 01:08:17.440
security and that makes no sense like

01:08:17.440 --> 01:08:20.880
for example I don't run only one like

01:08:20.880 --> 01:08:23.000
like for example virus checking is only

01:08:23.000 --> 01:08:24.720
one form of security one layer of

01:08:24.720 --> 01:08:26.040
security that you're protecting yourself

01:08:26.040 --> 01:08:27.980
front but I don't even run only one

01:08:27.980 --> 01:08:30.180
virus scanner I run two or three virus

01:08:30.180 --> 01:08:32.560
scanners on all my systems because the

01:08:32.560 --> 01:08:34.460
signatures are never all up to date on

01:08:34.460 --> 01:08:35.480
each other they've always got

01:08:35.480 --> 01:08:36.940
differences and that's just one

01:08:36.940 --> 01:08:38.680
example I mean same thing with spyware

01:08:38.680 --> 01:08:40.420
I don't just run out of where I'll put

01:08:40.420 --> 01:08:42.520
on search and destroy I'll put on any

01:08:42.520 --> 01:08:44.040
number of others you know I'll try

01:08:44.040 --> 01:08:45.680
several ones that I never go with just

01:08:45.680 --> 01:08:47.260
one solution I don't have just one

01:08:47.260 --> 01:08:49.540
firewall on my systems at home I just

01:08:49.540 --> 01:08:51.500
don't do it you can have layers of

01:08:51.500 --> 01:08:53.860
your layers that sounds kind of

01:08:53.860 --> 01:08:58.860
weird anyway number 11 number 11 scan

01:08:58.860 --> 01:09:00.340
for and investigate unexpected

01:09:00.340 --> 01:09:03.100
listening TCP or UDP ports on your

01:09:03.100 --> 01:09:05.980
network well that one's not really so

01:09:05.980 --> 01:09:07.940
much for the user client side of things

01:09:07.940 --> 01:09:09.280
that's obviously for the administrator

01:09:09.280 --> 01:09:11.240
side of things if you see something on

01:09:11.240 --> 01:09:12.940
your server that you don't recognize

01:09:12.940 --> 01:09:15.460
and you didn't install yeah check it

01:09:15.460 --> 01:09:19.720
out because that's root catch you've

01:09:19.720 --> 01:09:21.020
been you've been root kitted you've

01:09:21.020 --> 01:09:23.160
been root rooted and it's installed

01:09:23.160 --> 01:09:24.520
something on there and if you've got

01:09:24.520 --> 01:09:27.220
something shouting out to IRC and your

01:09:27.220 --> 01:09:29.020
box is an exchange server that doesn't

01:09:29.020 --> 01:09:32.240
use IS IRC or whatever yep you got

01:09:32.240 --> 01:09:35.020
owned then you got to check into it and

01:09:35.020 --> 01:09:37.420
it will moreover things like the older

01:09:37.420 --> 01:09:39.100
versions of iTunes or win amps that

01:09:39.100 --> 01:09:40.620
people would think are pretty benign and

01:09:40.620 --> 01:09:41.800
used to listen to their music at their

01:09:41.800 --> 01:09:44.200
workstations they have you know local

01:09:44.200 --> 01:09:46.640
exploits that will pop to admin access

01:09:46.640 --> 01:09:48.460
or or buffer overflows or you know

01:09:48.460 --> 01:09:50.020
insert your favorite exploit here

01:09:50.020 --> 01:09:53.640
right so it's not I mean it's it's

01:09:53.640 --> 01:09:55.180
also the devil you know not just the

01:09:55.180 --> 01:09:58.280
devil you don't true true yeah that's a

01:09:58.280 --> 01:09:59.780
good point it is client side as much

01:09:59.780 --> 01:10:01.780
more I was thinking more server side

01:10:01.780 --> 01:10:03.080
and admin side but you're right

01:10:03.080 --> 01:10:04.840
absolutely that's a good point client

01:10:04.840 --> 01:10:09.180
side too but you know and this is again

01:10:09.180 --> 01:10:12.780
back to real realistically any user using

01:10:12.780 --> 01:10:15.260
Windows of any flavor Windows XP whatever

01:10:15.260 --> 01:10:19.580
you've got 50 80 117 services running at

01:10:19.580 --> 01:10:21.380
any given fucking point when there's

01:10:21.380 --> 01:10:23.260
Windows XP and you can't find an isolate

01:10:23.260 --> 01:10:25.100
one little thing in there very easily

01:10:25.100 --> 01:10:31.020
certainly not grandma or Thelma Lou in

01:10:31.020 --> 01:10:32.400
accounting whatever I keep changing her

01:10:32.400 --> 01:10:35.640
name to they're not going to notice

01:10:35.640 --> 01:10:36.700
they're not going to know where to look

01:10:36.700 --> 01:10:37.740
and even if they did they're not going

01:10:37.740 --> 01:10:39.020
to notice they're going to see stuff and

01:10:39.640 --> 01:10:42.640
I think I told this story on the air a

01:10:42.640 --> 01:10:44.280
long time ago about my sister got the

01:10:44.280 --> 01:10:47.360
teddy bear virus that's that's what she

01:10:47.360 --> 01:10:49.080
called it it was because it was one of

01:10:49.080 --> 01:10:52.080
the Windows system files that has a

01:10:52.080 --> 01:10:53.760
little teddy bear icon on it while it's

01:10:53.760 --> 01:10:55.640
running and she got one of those chain

01:10:55.640 --> 01:10:57.920
letter emails that said warning this is a

01:10:57.920 --> 01:10:59.580
virus you must delete it and she's like

01:10:59.580 --> 01:11:01.600
oh I better I found it I better delete

01:11:01.600 --> 01:11:04.980
it I know it was funny that was good

01:11:04.980 --> 01:11:09.320
stuff oh I boy I I let her have it for

01:11:09.320 --> 01:11:11.900
that one she felt pretty stupid now the

01:11:11.900 --> 01:11:17.660
teddy bear virus she called it so yeah I'm

01:11:17.660 --> 01:11:18.940
not sure I was going with that but that

01:11:18.940 --> 01:11:22.780
was a funny story number 12 track where

01:11:22.780 --> 01:11:24.620
everyone browses on the internet and for

01:11:24.620 --> 01:11:26.620
how long nope nope nope nope I don't like

01:11:26.620 --> 01:11:28.500
this one already number 12 track where

01:11:28.500 --> 01:11:30.260
everyone browses on the internet and for

01:11:30.260 --> 01:11:32.500
how long post the findings on a real

01:11:32.500 --> 01:11:34.880
time online report that is accessible by

01:11:34.880 --> 01:11:36.860
anyone this recommendation tends to make

01:11:36.860 --> 01:11:40.260
users internet surfing habits self-policing

01:11:40.260 --> 01:11:43.140
I bet it will also lead to a sudden

01:11:43.140 --> 01:11:45.020
increase in productivity well I'm gonna

01:11:45.020 --> 01:11:46.020
have to give you a big fat fuck you on

01:11:46.020 --> 01:11:49.980
that one certainly businesses have the

01:11:49.980 --> 01:11:51.640
right I wouldn't debate that they have

01:11:51.640 --> 01:11:53.780
the right it's their equipment it's their

01:11:53.780 --> 01:11:55.420
network they certainly have the right to

01:11:55.420 --> 01:11:59.100
spy and track everything they want but a it's

01:11:59.100 --> 01:12:04.240
not ethical in my opinion and be if you know of

01:12:04.240 --> 01:12:06.520
individual employees or something that may

01:12:06.520 --> 01:12:09.420
be abusing the service then focus on those

01:12:09.420 --> 01:12:12.740
employees but don't blanketly don't throw a

01:12:12.740 --> 01:12:15.080
blanket over your whole company and catch

01:12:15.080 --> 01:12:18.180
everybody up in that net and track everything

01:12:18.180 --> 01:12:22.940
they do I do not like this one at all I know I

01:12:22.940 --> 01:12:26.580
know I know I it is it's kind of for me too it's

01:12:26.580 --> 01:12:28.420
well-intended I know if you're thinking from an

01:12:28.420 --> 01:12:30.180
admin standpoint you want to protect your

01:12:30.740 --> 01:12:32.860
server and stuff like that and productivity but

01:12:32.860 --> 01:12:36.700
you know what well saying let I tell you what

01:12:36.700 --> 01:12:38.980
let's also let me let me also throw this in the

01:12:38.980 --> 01:12:41.480
logistics behind that you're gonna have to hire

01:12:41.480 --> 01:12:43.740
somebody full-time practically who's going to

01:12:43.740 --> 01:12:46.080
go through and monitor and watch what is

01:12:46.080 --> 01:12:49.940
considered allowable or safe and not allowable

01:12:49.940 --> 01:12:51.600
what where do we draw the line I mean I can

01:12:51.600 --> 01:12:53.600
go to binrev.com and get a lot of good useful

01:12:53.600 --> 01:12:55.460
information for my programming or for something

01:12:55.460 --> 01:12:58.160
I'm working on but that'd be the first thing

01:12:58.160 --> 01:13:01.680
that would be banned or blocked you know so

01:13:01.680 --> 01:13:04.060
there's a catch-22 I can go into IRC during

01:13:04.060 --> 01:13:07.580
the day and go into pound coding on the IRC

01:13:07.580 --> 01:13:11.920
binrev net server and get an answer to my

01:13:11.920 --> 01:13:15.900
question but I don't want that being posted

01:13:15.900 --> 01:13:17.980
out there that I'm hanging out in IRC or I'm

01:13:17.980 --> 01:13:21.720
unproductive or somebody puts a kiddie porn joke

01:13:21.720 --> 01:13:23.680
on there and then that gets stuck up on a wall

01:13:23.680 --> 01:13:27.180
somewhere that's not cool oh and then think of

01:13:27.180 --> 01:13:30.280
think of the justification okay Joe Joe in

01:13:30.280 --> 01:13:32.920
accounts payable or something is gay and he's

01:13:32.920 --> 01:13:35.900
not out but his boyfriend sends him a link that

01:13:35.900 --> 01:13:38.560
has you know maybe some css tag from

01:13:38.560 --> 01:13:41.180
joesgaylover.com or something okay just

01:13:41.180 --> 01:13:43.340
hypothetically now if this gets automatically

01:13:43.340 --> 01:13:45.920
posted even though Joe who's been completely

01:13:45.920 --> 01:13:47.740
quiet and compliant about his sexuality this

01:13:47.740 --> 01:13:50.240
whole time is suddenly outed you know on

01:13:50.240 --> 01:13:52.820
this this scrolling LED ticker this defcon

01:13:52.820 --> 01:13:55.640
wall of shame I mean what's the liability

01:13:55.640 --> 01:13:57.180
for the company or something like that I

01:13:57.180 --> 01:13:59.220
mean yeah it is kind of a wall of sheep for

01:13:59.220 --> 01:14:01.680
millions it is it is kind of a wall of

01:14:01.680 --> 01:14:04.920
sheep isn't it yeah um yeah that's a good

01:14:04.920 --> 01:14:08.180
point yeah I think that's going a little

01:14:08.180 --> 01:14:10.280
far political stepping into evil or

01:14:10.280 --> 01:14:13.220
dictatorship I mean the more you threaten

01:14:13.220 --> 01:14:14.880
someone to do something like the more

01:14:14.880 --> 01:14:16.440
people are going to look into ways to

01:14:16.440 --> 01:14:18.160
circumvent that the harder you squeeze the

01:14:18.160 --> 01:14:19.960
more people are going to slip through but

01:14:19.960 --> 01:14:21.940
that's not any excuse that there's no

01:14:21.940 --> 01:14:24.500
exchange for just being a good manager

01:14:24.500 --> 01:14:26.060
and talking to them personally about it

01:14:26.060 --> 01:14:27.920
exactly and you know what I would refer

01:14:27.920 --> 01:14:29.800
those users who are concerned about that

01:14:29.800 --> 01:14:32.240
back to number seven encrypt all confidential

01:14:32.240 --> 01:14:35.360
data whenever possible yep tunnel your

01:14:35.360 --> 01:14:37.240
shit through SSH they're not going to be

01:14:37.240 --> 01:14:39.720
able to do shit I feel like kind of a

01:14:39.720 --> 01:14:42.680
hypocrite of course if I and then on one

01:14:42.680 --> 01:14:45.140
hand telling people to not do anything

01:14:45.140 --> 01:14:47.160
and on the other hand to encrypt it but I

01:14:47.160 --> 01:14:48.800
mean that's the hacker mentality I guess

01:14:48.800 --> 01:14:51.280
well it's a duality to it it's not black

01:14:51.280 --> 01:14:52.940
and white it's not that quite that simple

01:14:52.940 --> 01:14:56.680
you know if I'm at okay let's say um

01:14:56.680 --> 01:15:00.720
political affiliation or um come on is

01:15:00.720 --> 01:15:02.440
there really anything wrong with um

01:15:02.440 --> 01:15:04.600
exchanging email with a family member

01:15:04.600 --> 01:15:05.880
or something I mean people are entitled

01:15:05.880 --> 01:15:07.760
to break time if there are you can you

01:15:07.760 --> 01:15:09.220
know people are abusing it you know

01:15:09.220 --> 01:15:10.640
people aren't getting their work done or

01:15:10.640 --> 01:15:11.920
if you catch somebody on multiple

01:15:11.920 --> 01:15:15.040
occasions then yes monitor them that I

01:15:15.040 --> 01:15:16.920
see you have that right as no as an

01:15:16.920 --> 01:15:22.120
employee as a company I should say I can

01:15:22.120 --> 01:15:23.620
see that and I can understand that and I

01:15:23.620 --> 01:15:25.260
don't know that I would argue against it

01:15:25.260 --> 01:15:27.960
in that case but throwing this net out

01:15:27.960 --> 01:15:29.420
there for everybody and just phishing

01:15:29.420 --> 01:15:31.620
that's the way that's what I don't like

01:15:31.620 --> 01:15:33.340
about it it's just casting the net

01:15:33.340 --> 01:15:36.680
target it focus it and then from again

01:15:36.680 --> 01:15:38.420
the administration standpoint the

01:15:38.420 --> 01:15:40.260
logistics it takes time you're going to

01:15:40.260 --> 01:15:42.180
hire somebody is it really worth you

01:15:42.180 --> 01:15:43.680
spending all the time parsing through

01:15:43.680 --> 01:15:45.540
logs posting this kind of stuff looking

01:15:45.540 --> 01:15:47.780
through it you're going to have legal

01:15:47.780 --> 01:15:49.400
issues like you said I don't know that

01:15:49.400 --> 01:15:51.580
one I'm going to so far I'm going to say

01:15:51.580 --> 01:15:53.640
that's the only one I will out and out

01:15:53.640 --> 01:15:55.760
disagree with only the way that it's

01:15:55.760 --> 01:15:58.120
implemented again it can be more fine

01:15:58.120 --> 01:16:00.360
tuned I could work with it having a

01:16:00.360 --> 01:16:02.880
policy having a policy is one thing but

01:16:02.880 --> 01:16:04.720
the way you enforce it is a whole

01:16:04.720 --> 01:16:08.120
different thing entirely so I don't

01:16:08.120 --> 01:16:09.720
debate the policy I debate the

01:16:09.720 --> 01:16:12.720
application or the enforcement of said

01:16:12.720 --> 01:16:15.820
policy let's see quickly wrap up these

01:16:15.820 --> 01:16:19.460
last two number 13 automate security if

01:16:19.460 --> 01:16:20.960
you don't automate it you won't do it

01:16:20.960 --> 01:16:23.420
consistently I don't know about that

01:16:23.420 --> 01:16:25.280
well that kind of comes back to what we

01:16:25.280 --> 01:16:26.920
said earlier about applications

01:16:26.920 --> 01:16:28.360
reminding you that they need to be

01:16:28.360 --> 01:16:29.700
upgraded or telling you when a new

01:16:29.700 --> 01:16:32.000
upgrade is available I mean I guess

01:16:32.000 --> 01:16:33.780
you could make a policy or make a

01:16:33.780 --> 01:16:35.440
conscious decision the beginning of

01:16:35.440 --> 01:16:37.180
every month upgrade the server I do

01:16:37.180 --> 01:16:38.560
that with the bin ref server all the

01:16:38.560 --> 01:16:41.100
time it ought to a lot of stuff most

01:16:41.100 --> 01:16:42.640
stuff is automatically it does

01:16:42.640 --> 01:16:44.260
automatically happen but I still go

01:16:44.260 --> 01:16:46.280
there once a month and manually

01:16:46.280 --> 01:16:48.280
upgrade things just in case something

01:16:49.000 --> 01:16:51.520
didn't upgrade that should have or there

01:16:51.520 --> 01:16:53.580
was a failure or connection problem or

01:16:53.580 --> 01:16:56.160
something just to back it up just don't

01:16:56.160 --> 01:16:57.260
get too comfortable in your

01:16:57.260 --> 01:16:59.200
automation that you're not actually

01:16:59.200 --> 01:17:00.800
securing systems anymore you're just

01:17:00.800 --> 01:17:02.000
hoping that the machine's working

01:17:02.000 --> 01:17:05.600
properly right right absolutely and

01:17:05.600 --> 01:17:07.460
number 14 you know what in 14 to me

01:17:07.460 --> 01:17:09.240
this one should be number one I don't

01:17:09.240 --> 01:17:10.640
know why this is the last one because

01:17:10.640 --> 01:17:11.940
I've said it twice I think in this

01:17:11.940 --> 01:17:13.860
episode number one should be but

01:17:13.860 --> 01:17:15.520
they've got it listed as 14 educate

01:17:16.100 --> 01:17:18.740
staff and employees about security risks

01:17:18.740 --> 01:17:20.760
and create appropriate policies and

01:17:20.760 --> 01:17:24.300
procedures education I said that that

01:17:24.300 --> 01:17:27.080
is the key to all of this stuff I'm

01:17:27.080 --> 01:17:29.340
sorry you can be you can be an

01:17:29.340 --> 01:17:31.320
accountant you can be a secretary you

01:17:31.320 --> 01:17:33.020
can be a janitor you can be whatever it

01:17:33.020 --> 01:17:36.180
is in the company but just it's not that

01:17:36.180 --> 01:17:39.180
big a deal to have everybody go in for a

01:17:39.180 --> 01:17:42.220
week a day even a few hours or a few

01:17:42.220 --> 01:17:44.860
minutes a half an hour explanation of

01:17:44.860 --> 01:17:48.460
this is how our email system works you

01:17:48.460 --> 01:17:50.200
should never do this you should never

01:17:50.200 --> 01:17:52.160
do that and here's why people aren't

01:17:52.160 --> 01:17:55.520
stupid educate them teach them what to

01:17:55.520 --> 01:17:57.560
do and what not to do and they'll get

01:17:57.560 --> 01:17:59.540
the hang of it and they will hopefully

01:17:59.540 --> 01:18:00.840
not there's always going to be some

01:18:00.840 --> 01:18:03.180
people that do it anyway there's always

01:18:03.180 --> 01:18:04.280
going to people that ignore you and

01:18:04.280 --> 01:18:05.520
there are going to be fucktards that

01:18:05.520 --> 01:18:07.820
don't get it no matter how many times

01:18:07.820 --> 01:18:09.500
you tell them well you fire them

01:18:09.500 --> 01:18:10.520
because you don't want them working

01:18:10.520 --> 01:18:11.880
for you anyway if they're that rock

01:18:11.880 --> 01:18:12.440
stupid

01:18:12.440 --> 01:18:15.980
well hey now every company is that every

01:18:15.980 --> 01:18:17.620
corporate environment that I've worked

01:18:17.620 --> 01:18:19.880
at I've had to sit through once a year

01:18:19.880 --> 01:18:22.740
at least a fucking two hour long video

01:18:22.740 --> 01:18:24.760
and talk about sexual harassment

01:18:24.760 --> 01:18:27.000
policies and it's required by the state

01:18:27.000 --> 01:18:28.560
and all that shit well you know what

01:18:28.560 --> 01:18:31.520
that seems to me to be way more obvious

01:18:31.520 --> 01:18:33.000
than most of the things that we covered

01:18:33.000 --> 01:18:34.420
in these emails and yet it is still

01:18:34.420 --> 01:18:37.440
required by law so how is this any

01:18:37.440 --> 01:18:37.780
different

01:18:37.780 --> 01:18:41.940
yeah I agree absolutely right

01:18:41.940 --> 01:18:45.280
well I mean I guess that's all we can

01:18:45.280 --> 01:18:46.960
really say about that yeah and I think

01:18:46.960 --> 01:18:48.220
that's all we can really say about the

01:18:48.220 --> 01:18:49.840
article he does mention in his closing

01:18:49.840 --> 01:18:51.920
statement that he left off something

01:18:51.920 --> 01:18:53.580
that could be there very easily be there

01:18:53.580 --> 01:18:55.440
and that is physical security and that

01:18:55.440 --> 01:18:56.880
is I agree with that too I would have

01:18:56.880 --> 01:19:00.260
made that a 15th one myself and of

01:19:00.260 --> 01:19:01.840
course I'm sure other people listeners

01:19:01.840 --> 01:19:03.580
might have others they would add or

01:19:03.580 --> 01:19:05.280
maybe they would debate or argue with

01:19:05.280 --> 01:19:07.080
some of the ones we've talked about and

01:19:07.080 --> 01:19:09.420
if you do of course feel free to email

01:19:09.420 --> 01:19:11.960
us radio at binrev.com and tell us that

01:19:11.960 --> 01:19:13.380
you agree or disagree with some of

01:19:13.380 --> 01:19:14.660
these policies we're not going to take

01:19:14.660 --> 01:19:18.560
too much offense and I think that's

01:19:18.560 --> 01:19:20.560
going to do it for this episode we've

01:19:20.560 --> 01:19:20.880
got

01:19:20.880 --> 01:19:23.500
wow I've got a lot of topics I want to

01:19:23.500 --> 01:19:24.940
cover here in the upcoming months I've

01:19:24.940 --> 01:19:27.500
got several new guest hosts coming on

01:19:27.500 --> 01:19:28.800
the show that I'm trying to work out

01:19:28.800 --> 01:19:31.160
trying to get some some new people on

01:19:31.160 --> 01:19:33.160
here that are fairly well-known

01:19:33.160 --> 01:19:34.440
people that we've just never I don't

01:19:34.440 --> 01:19:35.780
know I just never invited on I'm

01:19:35.780 --> 01:19:36.940
going to start getting some people on

01:19:36.940 --> 01:19:39.440
the show and some new topics so I'm

01:19:39.440 --> 01:19:41.320
got a lot of stuff coming up in the

01:19:41.320 --> 01:19:43.860
next month or two while mr. ratchet

01:19:43.860 --> 01:19:47.200
mr. rashay takes a break and takes

01:19:47.200 --> 01:19:49.980
care of a few things so I you're stuck

01:19:49.980 --> 01:19:53.500
with me for at least a month or so so

01:19:53.500 --> 01:19:55.700
let's see how about we move into some

01:19:55.700 --> 01:19:59.260
shouts this week mine are pretty easy

01:19:59.260 --> 01:20:00.520
for me this week I'm going to give

01:20:00.520 --> 01:20:02.380
shouts out to all the guys working on

01:20:02.380 --> 01:20:04.000
hackerevents.org that I mentioned

01:20:04.000 --> 01:20:07.060
earlier specifically to zal91 who's

01:20:07.060 --> 01:20:08.220
also been helping with some graphic

01:20:08.220 --> 01:20:10.680
stuff to live and dead risk-free

01:20:10.680 --> 01:20:13.500
kotrin and enigma all friends of the

01:20:13.500 --> 01:20:16.140
show and the finrev so my shouts go to

01:20:16.140 --> 01:20:19.060
them this week how about you okay I'm

01:20:19.060 --> 01:20:21.280
everyone you just named with specific

01:20:21.280 --> 01:20:23.460
regards to zal91 big up to that guy

01:20:23.460 --> 01:20:26.000
great box everyone in pound cookie

01:20:26.000 --> 01:20:28.660
Damon the PLA and red box chili pepper

01:20:28.660 --> 01:20:30.720
and my girlfriend Elizabeth who will

01:20:30.720 --> 01:20:32.900
probably never ever hear this oh man

01:20:32.900 --> 01:20:37.400
score let's see side of the week side of

01:20:37.400 --> 01:20:39.060
the week this week is I gotta say kind

01:20:39.060 --> 01:20:41.500
of pervish like anything we do on the

01:20:41.500 --> 01:20:43.980
show is not pervish but it's that

01:20:43.980 --> 01:20:46.120
deleted YouTube video site somebody had

01:20:46.120 --> 01:20:47.720
posted this in the forums I believe and

01:20:47.720 --> 01:20:49.420
I've just been completely addicted by

01:20:49.420 --> 01:20:51.340
it even though it's filled with jail

01:20:51.340 --> 01:20:53.120
bait I learned by the way I learned

01:20:53.120 --> 01:20:54.600
this in IRC I learned all the terrible

01:20:54.600 --> 01:20:56.180
things in IRC I didn't know what JB

01:20:56.180 --> 01:20:59.720
stood for JB stands for jail bait for

01:20:59.720 --> 01:21:00.680
anybody that doesn't know that if

01:21:00.680 --> 01:21:02.040
people are in IRC talking about oh

01:21:02.040 --> 01:21:04.120
wow this is totally JB oh my gosh look

01:21:04.120 --> 01:21:05.600
at all the JB I'm like what the fuck is

01:21:05.600 --> 01:21:07.480
JB I don't know what that means stands

01:21:07.480 --> 01:21:09.100
it turns out that stands for jail bait I

01:21:09.100 --> 01:21:12.260
did not realize that so there's lots of

01:21:12.260 --> 01:21:14.780
jail bait at today's side of the week

01:21:14.780 --> 01:21:18.840
oh I'm terrible actually there's don't

01:21:18.840 --> 01:21:19.900
get me wrong there's not actually

01:21:19.900 --> 01:21:21.180
really bad stuff that I've seen

01:21:21.180 --> 01:21:22.220
anyway it's a bunch of chicks

01:21:22.220 --> 01:21:24.140
dancing around in their in their

01:21:24.140 --> 01:21:27.000
bedrooms dancing to don't you wish

01:21:27.000 --> 01:21:29.540
your girlfriend was hot like me

01:21:29.540 --> 01:21:32.400
don't you somebody's gonna loop that

01:21:32.400 --> 01:21:35.260
one as well but anyway the site which

01:21:35.260 --> 01:21:37.220
I haven't said yet is let's see

01:21:37.220 --> 01:21:43.760
www.youtube.infamousx.com

01:21:43.760 --> 01:21:48.240
that's I-N-F-A-M-O-U-S-X all one word

01:21:48.240 --> 01:21:52.000
infamousx.com youtube.infamousx.com

01:21:52.000 --> 01:21:54.600
our closing music this week is actually

01:21:54.600 --> 01:21:57.540
from my good friend MC Frontalot who he

01:21:57.540 --> 01:21:58.560
and I are actually working on some

01:21:58.560 --> 01:22:00.960
projects as well but he just released a

01:22:00.960 --> 01:22:04.240
new single from his nerdcore rising

01:22:04.240 --> 01:22:05.880
album it's called this old man this is

01:22:05.880 --> 01:22:08.680
actually my favorite song my favorite

01:22:08.680 --> 01:22:12.540
beat from the whole album so this is one

01:22:12.540 --> 01:22:13.780
of my favorite songs I'm glad he

01:22:13.780 --> 01:22:15.120
actually released this one as the next

01:22:15.120 --> 01:22:18.060
single so listen to this and enjoy it

01:22:18.060 --> 01:22:20.840
and go buy nerdcore rising the album

01:22:20.840 --> 01:22:23.380
bitches and you won't hear the word

01:22:23.380 --> 01:22:24.840
bitches on any of his rhymes either he's

01:22:24.840 --> 01:22:29.520
much more eloquent than I am me I'm just

01:22:29.520 --> 01:22:32.760
low-class white trash trailer trash

01:22:32.760 --> 01:22:35.160
whatever other cliche you want but

01:22:35.160 --> 01:22:38.940
whatever I am we will see you next week

01:22:38.940 --> 01:22:42.440
same hack time same hack channel

01:22:42.440 --> 01:23:02.220
I keep getting older and hairier on my neck

01:23:02.220 --> 01:23:05.960
back and derriere ho but not atop the paint

01:23:05.960 --> 01:23:09.500
dear DNA let's negotiate I'll trade a fading

01:23:09.500 --> 01:23:12.500
vision you can have that back plus the 30 year old man

01:23:12.500 --> 01:23:15.000
belly is kinda whack my hearing is hearing

01:23:15.000 --> 01:23:17.700
death this and I wheeze yo please take me from the wrist

01:23:17.700 --> 01:23:21.380
hurt disease it's invisible that these a whole list of ailments

01:23:21.380 --> 01:23:24.940
should do anything for the crew I'm a fail ten times out of ten

01:23:24.940 --> 01:23:28.740
to age in reverse like morgue is there anything sadder than a dork

01:23:28.740 --> 01:23:33.080
for whom the new hotness is not just inaccessible it's rumbled against you kids

01:23:33.080 --> 01:23:36.360
reduce your decibels don't make me come over there and shake my cane

01:23:36.360 --> 01:23:44.560
it's that rapper from the double a-r-b and he insane this old man he rhymed once he put up some valiant france with a wig

01:23:44.560 --> 01:23:51.560
whacked better like a pupil of some charm this old man kept driving on

01:23:51.560 --> 01:24:04.560
joints creaking while I squeak around the stage hello grandmother's telling me I ought to act my age deep range

01:24:04.560 --> 01:24:09.560
already I don't got no brain medicine if we were running out of food on a boat I'd get jettisoned

01:24:09.560 --> 01:24:11.560
or eaten I'm unsweetened

01:24:11.560 --> 01:24:15.560
don't tell me that I got the shorted straw I'm not a cretin just a little senile and gassy and slow

01:24:15.560 --> 01:24:19.560
but I bet I'm very salty and I can still row let's gobble on that infant

01:24:19.560 --> 01:24:23.560
infants are useless also very soft which is good cause I'm truthless

01:24:23.560 --> 01:24:28.560
come on kids you wanna get rescued or what don't mumble all amongst yourselves speak up

01:24:28.560 --> 01:24:33.560
I lost my ear horn the other day on the bus you would think by the way you whippersnappers make a fuss

01:24:33.560 --> 01:24:38.560
that I said something crazy profound a brim scene wait where the ocean go where have you taken me

01:24:38.560 --> 01:24:46.560
this old man he run twice he found this would not suffice with a wick whack better like a pupil of some men

01:24:46.560 --> 01:24:59.560
this old man was our right grif for this old man was our right grif

01:24:59.560 --> 01:25:03.560
now front of lights shopping for the top of the hill should have bought a burial plot

01:25:03.560 --> 01:25:06.560
soon as I got ill but I foolishly thought that I could put it off

01:25:06.560 --> 01:25:09.560
now I'm ghoulishly fraught with the

01:25:09.560 --> 01:25:12.560
soft in the head hard in the disposition

01:25:12.560 --> 01:25:14.560
how to earn this intractable attrition

01:25:14.560 --> 01:25:16.560
of the vigor that I figured would be mine for life

01:25:16.560 --> 01:25:18.560
is there no upside?

01:25:18.560 --> 01:25:20.560
well the rhymes are rife every year I'm alive

01:25:20.560 --> 01:25:24.560
that's my vocabulary gonna do it cause I'm staring at the ceiling in the mortuary

01:25:24.560 --> 01:25:26.560
plus I'm probably wise by now

01:25:26.560 --> 01:25:29.560
and could do all the things old people talk about

01:25:29.560 --> 01:25:32.560
like count pills, argue bills at diners

01:25:32.560 --> 01:25:34.560
get a little tiny funky car and be a shriner

01:25:34.560 --> 01:25:36.560
go to the haberdasher

01:25:36.560 --> 01:25:37.560
so I could look dapper

01:25:37.560 --> 01:25:38.560
get stroke and forget

01:25:38.560 --> 01:25:40.560
I'm too old to be a rapper

01:25:40.560 --> 01:25:42.560
this old man, he rhymes thrice

01:25:42.560 --> 01:25:44.560
he spoke a thin gruel of lies

01:25:44.560 --> 01:25:47.560
with a wick-wack bitter like a mute-fulness and spunk

01:25:47.560 --> 01:25:50.560
this old man's rhymes was fun

01:25:50.560 --> 01:25:52.560
this old man, he rhymes thrice

01:25:52.560 --> 01:25:54.560
right till he grew liver spots

01:25:54.560 --> 01:25:57.560
with a wick-wack bitter like a mute-fulness and sheer

01:25:57.560 --> 01:26:00.560
why he rhymes, remains unclear

01:26:00.560 --> 01:26:02.560
when are the guitar this morning!

01:26:02.560 --> 01:26:04.560
I mean I am an eight how theucklehead

01:26:04.560 --> 01:26:06.560
yes to the beat

01:26:06.560 --> 01:26:09.060
the music is

01:26:09.560 --> 01:26:10.560
chorus of reason

01:26:10.560 --> 01:26:12.560
by my power

01:26:12.560 --> 01:26:13.560
will show fullingers

01:26:13.560 --> 01:26:14.560
with a power

01:26:14.560 --> 01:26:15.560
toldcock

01:26:15.560 --> 01:26:18.560
it's amazing

01:26:18.560 --> 01:26:19.560
it's what...

01:26:19.560 --> 01:26:20.440
wow...

01:26:22.560 --> 01:26:23.560
wow...

01:26:23.560 --> 01:26:24.520
wow...

01:26:24.560 --> 01:26:25.520
you

01:26:25.520 --> 01:26:26.440
forever

01:26:26.440 --> 01:26:27.560
enjoy