--- Log opened Mon Oct 16 00:00:27 2017
00:08 -!- remoford [~remo_lapt@c-68-52-35-32.hsd1.tn.comcast.net] has quit [Quit: Leaving.]
00:24 -!- K`Tetch [~no@unaffiliated/ktetch] has quit [Read error: No route to host]
01:25 -!- EnabrinTain [sid11525@gateway/web/irccloud.com/x-almpgmrmrnztwpum] has quit [Ping timeout: 246 seconds]
03:22 -!- EnabrinTain [sid11525@gateway/web/irccloud.com/x-lieijfluqldbwwgz] has joined #se2600
03:22 -!- mode/#se2600 [+o EnabrinTain] by ChanServ
06:27 <@Dolemite> mr0ning, be0tches and h0ez!
06:30  * aestetix hugs Dolemite 
06:50 -!- TheDukh [~thedukh@2607:fcc8:ac80:d900:c0a:41d3:29a9:407e] has joined #se2600
08:03 -!- scam [~sicsscam@24.154.71.208] has quit [Read error: Connection reset by peer]
08:05 -!- scam [~sicsscam@24.154.71.208] has joined #se2600
08:13 <@Dagmar> The animated "This is fine" meme perfectly sums it up
08:46 <@rattle> Information wants to be freeeeeeeeeeee
08:59 -!- remoford [~remo_lapt@c-68-52-35-32.hsd1.tn.comcast.net] has joined #se2600
09:11 < xray> This is epicly bad https://arstechnica.com/information-technology/2017/10/severe-flaw-in-wpa2-protocol-leaves-wi-fi-traffic-open-to-eavesdropping/
09:11 < PigBot> Title: Severe flaw in WPA2 protocol leaves Wi-Fi traffic open to eavesdropping | Ars Technica (at arstechnica.com) http://tinyurl.com/y7levgh5
09:12 < xray> If it has WiFi it needs to be patched
09:12 < xray> assuming it uses WPA2
09:12 < TheDukh> cat6 all the things
09:12 < xray> yes indeed
09:12 < xray> The issue no one has mentioned yet. . . IoT
09:13 < xray> all the IoT is broken and will remain so because vendors do not patch them
09:15 <@shapr> code code code code, yay!
09:15 <@shapr> xray: does metasploit support that attack yet?
09:16 <@shapr> does metasploit handle wifi based attacks at all?
09:16 < xray> don't know
09:17 <@shapr> xray: got any more python questions?
09:17 <@rattle> It all fine!  Information wants to be freeeeeeeee
09:18 < xray> As long as it isn't YOUR information
09:30  * Catonic stirs
09:30  * Catonic shakes
09:31  * Catonic is martini incarnate
09:43 <@Dagmar> That the attack works because of a flaw in the protocol spec itself is what makes it especially pernicious
09:44 <@shapr> debian put out fixed wpasupplicant packages two days ago
09:51 <@Dagmar> I don't like that the advisory doesn't explcitly say this won't affect the AP end of things
09:51 <@Dagmar> There's a lot of detail in there, but I don't see _that_ one, which is suspicious
09:52 <@Dagmar> For the moment I'm just assuming WPA2 is just plain tamperable
09:58 <@Dolemite> I just got a new phone image from Sprint.  Will have to see if it has that update.
10:06 < aestetix> huh
10:06 < aestetix> I didn't know there was a Black Panther comic
10:06 < aestetix> is it... based on the group?
10:06 <@shapr> er, that was the origin?
10:07 <@shapr> of the movie superhero?
10:07 < aestetix> That's what I'm wondering
10:07 < aestetix> at least I assume there was a comic
10:07 < aestetix> because apparently there is a marvel movie coming out
10:07 < aestetix> and if it's marvel, I assumed there was a comic
10:08 < xray> yes there was a comic
10:08 < xray> https://en.wikipedia.org/wiki/Black_Panther_(comics)
10:08 < PigBot> Couldn't snarf url: HTTP Error 404: Not Found. http://tinyurl.com/ya8dwjr2
10:09 <@shapr> aestetix: 1966
10:09 < TheDukh> first major black superhero
10:09 < aestetix> The Black Panther's name predates the October 1966 founding of the Black Panther Party, though not the black panther logo of the party's predecessor, the Lowndes County Freedom Organization, nor the segregated World War II Black Panthers Tank Battalion.[1][2]
10:09 < aestetix> so now I wonder if the black panthers took their name from the comic
10:10 <@shapr> huh, interesting question
10:11 < TheDukh> i think they took it from the same source, the world war 2 all black tank battalion.
10:12 <@shapr> oh wow: https://en.wikipedia.org/wiki/761st_Tank_Battalion_(United_States)
10:12 < PigBot> Couldn't snarf url: HTTP Error 404: Not Found. http://tinyurl.com/y9ub3a5b
10:13 < TheDukh> Men, you're the first Negro tankers to ever fight in the American Army. I would never have asked for you if you weren't good. I have nothing but the best in my Army. I don't care what color you are as long as you go up there and kill those Kraut sonsofbitches. Everyone has their eyes on you and is expecting great things from you. Most of all your race is looking forward to your success. Don't let them down and damn you
10:13 < TheDukh> , don't let me down! They say it is patriotic to die for your country. Well, let’s see how many patriots we can make out of those German sonsofbitches.
10:14 < TheDukh> That's a helluva speech
10:15 < aestetix> TheDukh: ok I feel better about the comic now
10:15 < aestetix> and I guess the movie
10:15 <@shapr> wow
10:15 -!- K`Tetch [~no@24-178-141-147.dhcp.thtn.ga.charter.com] has joined #se2600
10:15 -!- K`Tetch [~no@24-178-141-147.dhcp.thtn.ga.charter.com] has quit [Changing host]
10:15 -!- K`Tetch [~no@unaffiliated/ktetch] has joined #se2600
10:15 < aestetix> although hollywood is not... an exemplar of excellence
10:16 <@shapr> understatement
10:17 < aestetix> shapr: I dunno, maybe now that there is a huge shakeup going on in hollywood, they might start making good movies again?
10:17 <@shapr> seems unlikely
10:18 <@shapr> from what I've seen
10:18 < aestetix> well at least some people will likely go to jail. I hope
10:18 <@shapr> the old guard must die for anything to change
10:18 < K`Tetch> good movies, rather than profitable ones?
10:18 <@shapr> and that's true for all things
10:19 < aestetix> good movies can be profitable
10:20 < aestetix> it's the endless sequels to good movies that make everything suck
10:22 < aestetix> trying to think of a good example
10:22 < aestetix> the only one I can think of right now is Saw :p
10:23 < xray> Sharknado?
10:24 < xray> Holloween?
10:24 < xray> Freddy Kruger movies?
10:24 < xray> do you really need more examples
10:24 <@oddball> Jaws?
10:24 < aestetix> well to be fair the freddy kruger movies were mostly so you could take a girl to the theatre and get play
10:24 < xray> Agree
10:25 < aestetix> although I do have a friend who got a blowjob in the back of the theatre during a showing of Patch Adams
10:25 < xray> or you could get married an play all you want
10:25 <@Dagmar> Explain Cube 2: Hypercube and Cube Zero then
10:25 < xray> Oh wait. . .  that's so old fashioned
10:25 < aestetix> which is about the strangest movie to get a bj during
10:26 < TheDukh> I lost my virginity while watching Seven, so....thats awkward
10:26 < xray> some sequels make sense and others are clearly just trying to jump on the bandwaggon
10:26 <@Evilpig> Cube is nothing.  Sharknado...2...3..4..5?!?!?!!!!
10:26 < aestetix> I haven't even heard of sharknado
10:26 <@Evilpig> 5 fucking shardnados!
10:26 < aestetix> that sounds like a straight-to-torrent movie
10:26 < xray> And you really don't want to know about sharknado
10:27 <@Dagmar> Sharknado was shit in the first instance
10:27 <@oddball> Close, Syfy movie series.
10:27 < xray> torrent is to good for Sharknado
10:27 < xray> bad doesn't begin to describe it
10:27 < xray> it gives good B movies a bad name
10:27 < TheDukh> SyFy movies.  Pretty sure they just created that studio for future reuse on MST3k
10:27 < xray> LoL
10:27 <@Evilpig> they got theater time for one or two of them
10:27 <@Dagmar> That seems a perfectly valid excuse
10:28 < xray> some times SyFy makes a good one
10:28 < xray> Dune for instance
10:28 <@Evilpig> their remake of dune was excellent
10:28 < xray> I will admit that is the exception rather than the rule
10:28 < xray> agreed
10:29 < TheDukh> How could it beat out the David Lynch version though?
10:30 <@Evilpig> modern effects
10:30 <@Dagmar> Acting that made any sense
10:30 <@Evilpig> they also had four hours to fill so they got a bit more story in there
10:30 < TheDukh> I suppose it makes the sand worms look more like something from Beetlejuice...
10:31 < xray> The David Lynch version makes a great trailer for the movie if they had made it.
10:31 < TheDukh> did anyone watch the new Bladerunner?
10:31 < xray> Not yet
10:31 <@Evilpig> yes
10:31 <@Evilpig> it was a good sequel
10:31 < aestetix> was it any good?
10:32 < xray> not doing well at the box office despite good reviews. Or so I have heard.
10:32 < xray> I'll watch it when it comes to RedBox
10:32 < xray> supposedly stunning visuals
10:33 <@Evilpig> I enjoyed it.  they had a valid reason for ford to be old as dirt and the story albeit obvious at points was told well enough to keep you invested 
10:42 -!- remoford [~remo_lapt@c-68-52-35-32.hsd1.tn.comcast.net] has quit [Quit: Leaving.]
10:58 -!- robogoat [~robogoat@163.172.136.88] has quit [Ping timeout: 255 seconds]
10:59 -!- robogoat [~robogoat@163.172.136.88] has joined #se2600
11:06 <@Dagmar> By the time it comes to Redbox I'll probably just buy it on Bluray since they seem to be getting lazy about stocking bluray discs lately
11:12 < xray> I use a laptop to play discs and menus are not supported on Bluray so I stick to DVD
11:12 < xray> Well I can get menus if I want to pay $100 per year in extortion for software upgrades
11:13 < xray> sorry no
11:13 -!- Catonic [~catonic@71-45-91-197.res.bhn.net] has quit [Quit: fraking kernel]
11:13 < xray> so far there is no viable open source Blueray menu software that works
11:14 < k3ymkr> Proof-of-concept
11:15 < xray> are you asking if there is one or saying you know of one
11:15 < k3ymkr> https://s3.amazonaws.com/k3ymkr/index.html
11:15 < PigBot> Title: Severe flaw in WPA2 https://tinyurl.com/ycmuf4m6 (at s3.amazonaws.com) http://tinyurl.com/y9ywgnxu
11:15 < xray> yeah posted about it this morning
11:15 < k3ymkr> Was seeing if it would print out my malicious tinyurl
11:16 < k3ymkr> No, I'm just being dumb
11:16 < xray> basically if it uses wifi it is vulnerable
11:16 < xray> both client and AP
11:16 < xray> even enterprise
11:16 < k3ymkr> Yeah
11:16 < k3ymkr> I just used that as page of the day
11:17 < xray> since most wifi enabled devices in use have been abandoned by there vendor and will never get a patch you will just have to disable wifi or throw it out.
11:18 < xray> that includes your TV, Firestick, Chromecast, Roku, etc.
11:18 < xray> all IoT
11:18 <@Evilpig> Ubiquiti already put out a firmware update for my APs. :D
11:19 < xray> After this, WiFi will become a target rich environment.
11:19 < xray> Cisco as well
11:20 < xray> but all those old Linksys, Netgear, Belkin, etc. will need to be trashed if there isn't a patched 3rd party firmware for them
11:20 < xray> the vendors have abandoned most of what is deployed in the wild
11:21 < xray> not to mention most of them were vulnerable because they use dnsmasq
11:21 < xray> and that didn't get updated eiither
11:25 <@Dagmar> hopefully in a few days someone will clarify that this can't be leveraged against APs
11:33 < aestetix> ok this is interesting
11:33 < aestetix> http://www.businessinsider.com/students-learning-education-print-textbooks-screens-study-2017-10
11:33 < PigBot> Title: Students learn more effectively from print textbooks than screens, study says - Business Insider (at www.businessinsider.com) http://tinyurl.com/ych6xtb4
11:34 <@Evilpig> that isn't all that interesting.  it's easier to do shit on a pc while looking at a real book than trying to tab back and forth between a digital book and whatever you're trying to do
11:34 <@Evilpig> same should apply to kids writing papers, etc
11:37 <@Dagmar> ...for people who only have one screen
12:02 < xray> Dagmar: why do you think this doesn't affect APs?
12:02 <@Dagmar> That's not what I said
12:02 < xray> from what I have read. If it uses WiFi it is vulnerable.
12:02 <@Dagmar> That's literally the exact opposite of what I've been saying
12:03 < xray> So why do you think access points are immune?
12:03 <@Dagmar> Why do you think climbing into an elephant's ass would be fun?>
12:03 < xray> ubiquity and cisco have released patches for their enterprise APs for KRACK
12:03 < xray> What?
12:04 < xray> I don't understand your point?
12:04 <@Dagmar> Paste where I apparently said access points are immune
12:04 < xray> @Dagmar
12:04 < xray> hopefully in a few days someone will clarify that this can't be leveraged against APs
12:04 <@Dagmar> You've never had a class on forensic logic, have you
12:05 < xray> are you referring to debate?
12:05 < xray> if so yes
12:05 <@Dagmar> At the moment, rather lots of people seem to think that APs are immune because they're not explciitly mentioned directly
12:05 <@Dagmar> I am looking at this stuff and finding it very suspicious that they do not come out and say "APs will not need patching"
12:05 < xray> actually they are if you read the KRACK web site
12:05 < xray> that's because APs will need patching
12:06 < xray> If it has WPA2 implemented it is vulnerable
12:06 < xray> AP and client alike
12:06 <@Dagmar> That's how I feel about it
12:07 <@Dagmar> Yet people are somehow getting the idea that APs can't be abused this way because the attack examples they walk through only leverage attacks against the client end
12:07 <@Dagmar> I'm frankly assuming there's ways to leverage these attacks in both directions until someone says explcitly otherwise
12:07 < xray> I read what you said as " once the smoke clears it will become evident that APs don't need to be patched, this only affects clients"
12:07 < xray> I guess I read that wrong
12:07 <@Dagmar> Yep
12:08 <@Dagmar> I am *hoping* someone will clarify in that way, one way or another, very soon
12:08 <@Dagmar> ...because right now i'm seeing people make what I feel are pretty dangerous assumptions
12:08 < xray> never mind (in my best Rosanna Rosanna Danna impertionation)
12:08 <@Dagmar> 'illegal obversion' is the thing I think was happening there
12:09 < xray> Well Ubiquity and Cisco have released AP patches for this so I'd say that'e pretty definitive
12:09 <@Dagmar> Yep
12:09 <@Dagmar> I suspect they are leaving some details out of the current published info because frankly, it's all pretty fucking terryfing
12:09 <@Dagmar> er terrifying
12:09 < xray> Unless they want to claim it was only for the code that lets the AP act as a client
12:10 < xray> I agree
12:10 <@Dagmar> I'm willing to read between the lines on this one
12:10 < xray> their full paper is available on line
12:10 <@Dagmar> The fun thing is if PEOPLE WOULD JUST FUCKING USE HTTPS CORRECTLY ALREADY this wouldn't be such a major deal
12:10 <@Dagmar> It would be a network access problem, and not a secret disclosure problem
12:11 < xray> Actually there is a different problem that HTTPS (encrypted protocols) won't fix
12:11 <@Corydon76> Dagmar: until the next SSL vuln comes out, like, say, the Infineon vuln released today.
12:11 <@Dagmar> That's a typical "cheapass vendor fail"
12:11 < xray> the primary reason you should set your AP to encrypt is to control who has access to your network
12:11 <@Dagmar> Their hardware implementations generated shit keys because no one was checking
12:12 <@Dagmar> xray: Yeah but people using HKPK stupidly or not at all (which is like 99% of sites) makes it worse
12:12 < xray> rehad "Wouldn't using encrypted Wi-Fi or a VPN protect my traffic?" here https://narknet.com/faq.html
12:12 < PigBot> Title: NarkNet - Passive Wi-Fi Surveillance FAQ (at narknet.com) http://tinyurl.com/y7q9pysf
12:12 <@Corydon76> Whose fault it was isn't the issue.  The issue is that our goto plan for securing needs caveats for the foreseeable future
12:12 < xray> I totally agree
12:13 < xray> There are a lot of devices abandoned by their vendors that we still use
12:14 < xray> they all will have to be tossed out unless you can install patched 3rd party hardware or just disable WiFi on them
12:14 <@Dagmar> Yep
12:14 <@Corydon76> Unfortunately, it's also the norm that as soon as chips are released, they're effectively abandoned by the manufacturer.
12:15 < xray> That is why I would love a cell phone based on commodity hardware that runs OTS Linux
12:15 <@Corydon76> As long as it's operating according to spec, even if the spec is vulnerable, they're not going to support it.
12:15 < xray> like a Raspberry Pi cell phone
12:15 < xray> but that will never happen
12:15 <@Dagmar> Those exist
12:15 <@Dagmar> They look like that shit PDA from Quantum Leap tho
12:16 < xray> there is Plasma which only runs on the Nexus 5 and 5x
12:16 < xray> very experimental
12:16 <@Corydon76> Yep, by the time they gain the usability of Android 2.2, the world will have moved onto Android 22.0.
12:16 < xray> and I will have spent $20K on replacing my cell phone every 18 months
12:17 < xray> talk about planned obsolescence
12:17 <@Corydon76> You replace at 18 months?
12:17 < xray> No
12:17 < xray> that is how often the abandon a platform
12:17 < xray> I have a research phone
12:17 <@Corydon76> My husband replaces at 12 months.  I tend to try for 36 months.
12:18 < xray> so I replace it when they give me a new one
12:18 <@Corydon76> I replace mine when the problems with it make it impossible for me to ignore
12:18 < xray> even with that the patches take a really long time to roll out
12:19 < xray> I have seen posts that Microsoft has already rolled out Windows patches for KRACK
12:19 < xray> yet I have not been able to find a single KB article that confirms it
12:20 < xray> The CVEs are reserved so there isn't much published about them
12:24 <@Corydon76> Is tomorrow Patch Tuesday?
12:25 < k3ymkr> Patch Tuesday was last week
12:25 < k3ymkr> https://s3.amazonaws.com/k3ymkr/index.html
12:25 < PigBot> Couldn't snarf url: HTTP Error 403: Forbidden. http://tinyurl.com/y9ywgnxu
12:25 < k3ymkr> Stupid bot :)
12:25 < k3ymkr> I'm kidding.  Smart bot
12:25 < k3ymkr> Oh that's on me
12:26 < k3ymkr> https://s3.amazonaws.com/k3ymkr/index.html
12:26 < PigBot> Title: Severe flaw in WPA2 https://tinyurl.com/ycmuf4m6 (at s3.amazonaws.com) http://tinyurl.com/y9ywgnxu
12:26 < k3ymkr> So a malicious url in the title comes across
12:27 < k3ymkr> Think anyone would click it?
12:27 < k3ymkr> Or is it sufficient that it's not the last?
12:29 <@Dagmar> Isn't https://www.krackattacks.com/ easy enough?
12:29 < PigBot> Couldn't snarf url: [Errno 1] _ssl.c:492: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure. http://tinyurl.com/ybzzv2kb
12:29 < k3ymkr> My point was to put a malicious tinyurl into the title of a page
12:29 < k3ymkr> The bot would display it.
12:30 < k3ymkr> and so there are two above
12:30 < k3ymkr> Clicking the first would take you to "evil"
12:39 < xray> see "Is my device vulnerable?" https://www.krackattacks.com/#faq
12:39 < PigBot> Couldn't snarf url: [Errno 1] _ssl.c:492: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure. http://tinyurl.com/ybma9rgg
12:39 < xray> "Probably. Any device that uses Wi-Fi is likely vulnerable. Contact your vendor for more information."
12:39 < xray> What if there are no security updates for my router?
12:39 < xray> "Our main attack is against the 4-way handshake, and does not exploit access points, but instead targets clients. So it might be that your router does not require security updates. We strongly advise you to contact your vendor for more details. In general though, you can try to mitigate attacks against routers and access points by disabling client
12:39 < xray> functionality (which is for example used in repeater modes) and disabling 802.11r (fast roaming). For ordinary home users, your priority should be updating clients such as laptops and smartphones."
12:40 < xray> So that sounds like an AP is vulnerable if it can act like a client
12:41 < xray> This might also mean that anyone connecting to an AP with a vulnerable client can expose the patched clients.
12:44 -!- rhia [~rhia@66.165.15.89] has joined #se2600
12:44 -!- mode/#se2600 [+o rhia] by ChanServ
13:13 <@Corydon76> xray: sounds like Wifi extenders are vulnerable, though simple APs are not.
13:24 <@Dagmar> "Moreover, because GCMP uses the same authentication key in both communication directions, and this key can be recovered if nonces are reused, it is especially affected."
13:26 <@Dagmar> ...also "The direction in which packets can be decrypted (and possibly forged) depends on the handshake being attacked."
13:27 <@shapr> Is wigig the 60ghz short range stuff?
13:27 <@shapr> ah, 802.11ad
13:42 -!- remoford [~remo_lapt@c-68-52-35-32.hsd1.tn.comcast.net] has joined #se2600
13:46 -!- Catonic [~catonic@71-45-91-197.res.bhn.net] has joined #se2600
13:46 -!- mode/#se2600 [+o Catonic] by ChanServ
13:46 <@Catonic> when you start getting disk errors but hardware isn't failing...
13:47 -!- remoford [~remo_lapt@c-68-52-35-32.hsd1.tn.comcast.net] has quit [Ping timeout: 255 seconds]
14:15 -!- remoford [~remo_lapt@c-68-52-35-32.hsd1.tn.comcast.net] has joined #se2600
14:17 <@Evilpig> Catonic: what is an overloaded virtual host using zfs for client backend storage
14:17 <@Evilpig> did I win?
14:22 < dc0de[m]> What is a device driver with a memory leak?
14:23 <@Evilpig> What is nfs client to a windows server?
14:50 <@Corydon76> What is a busy network on which your SAN is connected?
14:51  * Evilpig claps "good answer, good answer"
14:51 <@Corydon76> aka why VLAN alone is insufficient separation
15:01 <@Dagmar> Answer: "It's not a problem until the Sharepoint admin complains about slow disk access."
15:01 <@Dagmar> Because *fuck* Hogan
15:04 < xray> Just to round out the day and pry you out from under you're bed where you were hiding with your WiFi devices. . . https://arstechnica.co.uk/information-technology/2017/10/crypto-failure-cripples-millions-of-high-security-keys-750k-estonian-ids/
15:04 < PigBot> Title: Millions of high-security crypto keys crippled by newly discovered flaw | Ars Technica UK (at arstechnica.co.uk) http://tinyurl.com/y8gjerde
15:08 <@Dagmar> Those are nothing we have to worry about
15:08 <@Dagmar> Only people that bought lowest-bidder smartcards for generating their keys are affected
15:08 <@Dagmar> Mainly Estonia
15:10 <@Evilpig> I guess while it's on my mind and I have a few minutes I should go ahead and update my APs and the ones at my parents' houses too
15:11 < xray> assuming there is a patch avaialble
15:11 <@Evilpig> there is
15:11 < xray> Ubiquity?
15:11 <@Evilpig> they were one of the two companies that listed updates in that ars technica article this morning
15:11 <@Evilpig> yes
15:12 < xray> I may upgrade my ap
15:12 < xray> any suggestions?
15:12 <@Dagmar> Yeah.  Buy a Raspberry Pi 3 and that Edimax two-antenna wireless dongle
15:12 <@Evilpig> I've got a few of the AP-LP or whatever and they work well
15:12 <@Evilpig> I have two of the mesh nodes at my mom and mike's and they've been tickled pink
15:12 <@Dagmar> It seems like the only way to get an AP that isn't a low-bidder shitfest is to spend over $100
15:12 < xray> Interesting
15:13 < xray> I was considering that
15:13 <@Dagmar> ...and at that point you can get a Pi3 kit and that dongle and Raspbian and it's both fucking easy and future-proof
15:13 <@Evilpig> my only complaint with those is I haven't been able to easily update them remotely
15:13 < xray> got a link to the adapter?
15:13 < xray> You can update them via an ssh connection
15:14 < xray> I have an ssh bastion on a PI on my network
15:14 < xray> I can then connect to any of my Pis and patch them
15:14 <@Evilpig> xray: yeah I'm aware, but I didn't want to risk anything weird happening and me having to drive two hours north to fix it when it isn't critical and can wait til I go up for thankgiving
15:14 < xray> ah
15:15 < xray> I setup dynamic dns with ssh forwarding on a non standard port
15:15 < xray> then all the usual ssh hardening tricks
15:15 <@Evilpig> hrmm weird.  my usg shows provisioning right after I brought hte controller back up.
15:16 < xray> if you can't get access no foul you can still go up in person
15:16 <@Dagmar> Gimme a few minutes to dig up a link
15:16 < xray> thanks
15:16 <@Dagmar> It's one of the few that have two external antennas on it
15:16 <@Evilpig> I'm just not gonna break the ones at mom's because that would cut grandpa's internet off
15:16 < xray> I have a few Edimax now but they no longer make them
15:17 < xray> I have also found that Rosewill often sells OEM versions of the Edimax adapters
15:18 -!- remoford [~remo_lapt@c-68-52-35-32.hsd1.tn.comcast.net] has quit [Ping timeout: 260 seconds]
15:22 < xray> https://www.bleepingcomputer.com/news/security/list-of-firmware-and-driver-updates-for-krack-wpa2-vulnerability/
15:26 <@Dagmar> This looks a reasonable model https://www.amazon.com/BrosTrend-1200Mbps-Wireless-Antennas-Supports/dp/B01IEU7UZ0/ref=sr_1_8?ie=UTF8&qid=1508185341&sr=8-8&keywords=linux+usb+wifi+adapter
15:26 < PigBot> Title: Amazon.com: BrosTrend 1200Mbps Long Range USB WiFi Adapter; Dual Band 5GHz Wireless Network Speed 867Mbps, 2.4GHz 300Mbps; 2 X 5dBi WiFi Antennas; USB 3.0; Supports Windows 10/8/7/XP, Linux Mint, Ubuntu, Raspbian: Computers & Accessories (at www.amazon.com) http://tinyurl.com/yclvrb54
15:26 <@Dagmar> It uses the same realtek chipset
15:29 <@Dagmar> Anyway, it's very possible to get a wifi adapter for about $30-35 that will add AC/N to an RPi
15:29 <@Dagmar> ...and if you're not worried about 5GHz or a lot of range, you can just use the built-in
15:32 <@Dagmar> Another one https://www.amazon.com/gp/product/B01LY35HGO/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=B01LY35HGO&linkCode=as2&tag=wireless2017-20&linkId=94341fa33feae300b64a9e01e2deb4cd
15:32 < PigBot> Title: Amazon.com: Panda Wireless PAU09 N600 Dual Band (2.4GHz and 5GHz) Wireless N USB Adapter W/ Dual 5dBi Antennas - Windows XP/Vista/7/8/8.1/10, Mint, Ubuntu, openSUSE, Fedora, CentOS, Kali Linux and Raspbian: Computers & Accessories (at www.amazon.com) http://tinyurl.com/y7k474v6
15:35 < xray> Thanks. I can track down the chip set and find all the adapters built with it
16:38 -!- TheDukh [~thedukh@2607:fcc8:ac80:d900:c0a:41d3:29a9:407e] has quit []
16:54  * Catonic phases back in... and out again
17:25 -!- remoford1 [~remo_lapt@c-69-137-84-154.hsd1.tn.comcast.net] has joined #se2600
17:54 -!- remoford1 [~remo_lapt@c-69-137-84-154.hsd1.tn.comcast.net] has quit [Quit: Leaving.]
17:54 < xray> looking at Realtex chips that support 802.11ac and USB https://wikidevi.com/wiki/Realtek#USB
17:54 < PigBot> Couldn't snarf url: HTTP Error 403: Forbidden. http://tinyurl.com/y832nuhs
18:24 -!- remoford [~remo_lapt@c-69-137-84-154.hsd1.tn.comcast.net] has joined #se2600
18:53 < aestetix> https://twitter.com/FowlCanuck/status/919760665971224577
18:53 < PigBot> Title: Curtis on Twitter: "@jordanbpeterson Who ever could you be referring to? Surely not our beautifully-haired feminist-preaching Saudi-arms-dealing Prime Minister, surely? https://t.co/Sy4LR4Fd96" (at twitter.com) http://tinyurl.com/ybx5cxwj
18:53 < aestetix> this comic is amazing
19:01 < xray> OK looked through all the Atheros, Ralink, Broadcom, MediaTek and Realtek chip sets
19:01 < xray> not much to pick from if you are on USB
19:02 < xray> the newer Realtek adapters will require driver compilation from source
19:02 < xray> https://wikidevi.com/wiki/Realtek#.28a.29bgn_2
19:02 < PigBot> Couldn't snarf url: HTTP Error 403: Forbidden. http://tinyurl.com/yck9yf9d
19:04 < xray> https://wikidevi.com/wiki/Realtek#ac
19:04 < PigBot> Couldn't snarf url: HTTP Error 403: Forbidden. http://tinyurl.com/yb9tzxyb
19:05 < xray> RTL8812AU is looking like the best bet
19:23 -!- TheDukh [~thedukh@2607:fcc8:ac80:d900:c0a:41d3:29a9:407e] has joined #se2600
20:16 -!- TheDukh [~thedukh@2607:fcc8:ac80:d900:c0a:41d3:29a9:407e] has quit []
20:17 <@brimstone> i have one of those
20:18 <@brimstone> these drivers work the best, but i haven't used it much: https://github.com/brimstone/rtl8812au
20:18 < PigBot> Title: GitHub - brimstone/rtl8812au: RTL8812AU/21AU and RTL8814AU driver with monitor mode and frame injection (at github.com) http://tinyurl.com/y99jk55c
20:19 < xray> thanks
20:19 < xray> thinking of using this
20:19 < xray> https://www.amazon.com/dp/B00MX57AO4?tag=wiki085-20
20:19 < PigBot> Title: Amazon.com: Alfa Long-Range Dual-Band AC1200 Wireless USB 3.0 Wi-Fi Adapter w/2x 5dBi External Antennas - 2.4GHz 300Mbps / 5Ghz 867Mbps - 802.11ac & A, B, G, N: Computers & Accessories (at www.amazon.com) http://tinyurl.com/ybsxmj3s
20:19 < xray> with an RPi3
20:19 < xray> not sure it can source the power the adapter needs via usb
20:22 < xray> Then again the built in wifi might work fine
20:22 < xray> building an new AP that has patches
20:22 <@brimstone> i have this one: https://www.amazon.com/Long-Range-Dual-Band-Wireless-External-Antennas/dp/B00VEEBOPG/ref=sr_1_1?s=electronics&ie=UTF8&qid=1508203350&sr=1-1&keywords=RTL8812AU
20:22 < PigBot> Title: Amazon.com: Alfa Long-Range Dual-Band AC1200 Wireless USB 3.0 Wi-Fi Adapter w/2x 5dBi External Antennas 2.4GHz 300Mbps/5GHz 867Mbps 802.11ac & A, B, G, N: Computers & Accessories (at www.amazon.com) http://tinyurl.com/y7zwddk8
20:23 <@brimstone> i need to move it to my backpack
20:23 < xray> I'm considering that one as well
20:23 < xray> does it support monitor and injection with Kali?
20:23 < xray> will it work with the RPi3?
20:23 <@brimstone> remind me next time we meet and i'll let you borrow it
20:23 <@brimstone> it should
20:24 <@brimstone> haven't tried
20:24 < xray> with kali or Rpi?
20:24 < xray> or both
20:24 <@brimstone> i've only used it with debian
20:24 < xray> that is what I run on the RPi
20:25 < xray> Kali is debian based so it should work
20:25 <@brimstone> kali uses its own kernel though
20:25 <@brimstone> they don't use the debian one
20:26 < xray> Ah
20:26 <@brimstone> i need to build that repo into a dkms deb
20:26 <@Catonic> huh
20:28 <@Catonic> I wonder what the wireless at DEFCON looks like now
20:29 <@brimstone> it was kinda shit this year
20:30 <@brimstone> 2.4GHz was useless
20:30 <@brimstone> 5GHz was bearable
20:30 <@Catonic> lmao
20:30 <@Catonic> Did they quit using Aruba?
20:31 <@brimstone> no idea
20:31 <@brimstone> seemed like a lot of APs, just no bandwidth to even internal services
20:38 < xray> I suspect the network is getting hammered with attacks as well
20:38 < aestetix> so you guys wanna learn something interesting
20:38 < xray> Would love to run NarkNet there and see what was happening
20:38 < aestetix> that I found out about the SJWs in the bay area? this has direct relevance to all of you
20:39 < skiboy> I won't even pretend to care
20:39 < aestetix> apparently they have compiled a list of personna non grata, usually people who say things they don't like on twitter and other things, and have started sending the list to companies either discouraging the companies from hiring them, or encouraging the companies to fire them
20:40 < aestetix> a friend of mine learned he was on this list when a company he was consulting with got contacted by these crazies
20:41 < skiboy> nope, still don't care
20:41 < aestetix> good for you. I found it incredibly haunting
20:41 < skiboy> Why not talk about an interesting project that you're working on?
20:42 < aestetix> ok forget I said anything. just trying to warn friends
20:43 < skiboy> I'm working on these little pluggable nixie modules, so you can chain them together and make a display with a customizable length
20:44 < skiboy> The community has gotten too bogged down in politics, and not enough actual hacking is going on
20:47 < xray> like building a new WiFi router out of a Raspberry Pi 3
20:47 < skiboy> exactly
20:47 < xray> I don't think I will be able to find firmware for my WRT54G and WRT54GL with the KRACK patch
20:48 < skiboy> LEDE should support it
20:48 < xray> Not sure
20:48 < skiboy> Topic for #lede-dev is: Welcome to LEDE | Forum: http://forum.lede-project.org/ | Wiki: http://wiki.lede-project.org/ | Release: https://lede-project.org/releases/17.01/ | WPA2 / KRACK fixes are in master and lede-17.01 branch, and 17.01.4 release is being prepared. Be aware that you still need to patch ALL your clients, even if your AP is patched!
20:48 < xray> I know for a fact I can fix it with a Raspberry Pi 3 running Debian
20:48 < PigBot> Title: LEDE Project Forum (at forum.lede-project.org) http://tinyurl.com/y9retgd3
20:49 < skiboy> https://wiki.openwrt.org/toh/linksys/wrt54g
20:49 < PigBot> Couldn't snarf url: HTTP Error 403: Bad Behavior. http://tinyurl.com/hwtkhek
20:49 < xray> yeah I'm not expecting my Samsung Galaxy S5 to be patched by AT&T
20:49 < skiboy> Depends on which version you have
20:49 < xray> they still haven't rolled out any of the Bluetooth patches
20:50 < xray> I can check. biab
20:50 < skiboy> I'm running LineageOS on a Nexus 6, so the AOSP patches should be rolling in soon
20:51 < skiboy> Ubuntu just got patched.  I just ran an update on wpasupplicant.
20:51 < xray> WRT54GL v1.1
20:51 < skiboy> It's supported
20:54 < xray> The RPi 3 usb supports 1.2A https://github.com/superjamie/lazyweb/wiki/Raspberry-Pi-Power
20:54 < PigBot> Title: Raspberry Pi Power · superjamie/lazyweb Wiki · GitHub (at github.com) http://tinyurl.com/ybqa28nv
20:55 < skiboy> I'm looking for the proper firmware
20:55 < xray> OpenWRT does not support the KRACK patch for the WRT54GL
20:56 < xray> the most current version avail is 10.03.1
20:56 < xray> the version with the KRACK patch is 17.01
20:56 < xray> so it looks like the WRT54Gx line has been abandoned by the project
20:57 < skiboy> those wiki pages are crazy out of date
20:57 < skiboy> LEDE still is compiling updates for them
20:57 < skiboy> http://downloads.lede-project.org/releases/17.01.3/targets/brcm47xx/legacy/
20:57 < PigBot> Title: Index of /releases/17.01.3/targets/brcm47xx/legacy/ (at downloads.lede-project.org) http://tinyurl.com/ycfp6yf5
20:58 < skiboy> 17.01.4 should be out soon.  That's what will have the patch
20:58 < xray> then the docs are way out of date
20:58 < skiboy> yuuuuuuuuuup
20:59 < skiboy> That's why LEDE split from OpenWRT.  OpenWRT couldn't get their shit together.
20:59 < xray> not seeing the wrt54GL on that list
20:59 < xray> didn't know that
20:59 < skiboy> I think it just takes the wrt54G firmware
21:00 < xray> I'll look into that
21:00 < xray> It would be great if I could keep using my wrt54 series routers
21:00 < xray> I have a whole case of them
21:00 < skiboy> 80% sure that it just takes the regular 54G firmware
21:02 < skiboy> but wait for 17.01.4
21:02 < xray> will do
21:02 < skiboy> #lede-dev for more info
21:02 < xray> found this https://lede-project.org/toh/views/toh_fwdownload?dataflt%5BModel*~%5D=wrt54gl
21:02 < PigBot> Couldn't snarf url: HTTP Error 403: Bad Behavior. http://tinyurl.com/ydxznvxq
21:03 < skiboy> yeah those tables are wonky too
21:03 < xray> yep same build as the WRT54G https://lede-project.org/docs/targets/brcm47xx
21:03 < PigBot> Couldn't snarf url: HTTP Error 403: Bad Behavior. http://tinyurl.com/ybfgfbay
21:03 < skiboy> LEDE should be merging back into OpenWRT soon
21:05 < skiboy> Pretty much nothing is ever abandoned by OpenWRT/LEDE
21:06 < skiboy> Even devices with 4MiB or less of flash are supported by a smaller version of the firmware
21:06 < skiboy> Yay for sensible FOSS build systems
21:07 < skiboy> Dunno why router manufacturers don't just use this out of the box and save themselves some dev time
21:08 < skiboy> They reinvent the wheel just so people can remove their wheel and put the old wheel on it
21:10 < xray> mac80211: backport kernel fix for CVE-2017-13080
21:10 < xray> https://github.com/lede-project/source/commit/2f701194c29da50bfda968a83c6609843f74a7f4
21:10 < PigBot> Title: mac80211: backport kernel fix for CVE-2017-13080 · lede-project/source@2f70119 · GitHub (at github.com) http://tinyurl.com/y9eyojcx
21:11 < xray> Once I have a patched router I will need to detect devices that are not patched to keep them off my wifi
21:11 < skiboy> If you hop on their channel, all of the 17.01 stuff is being compiled, and their bot is notifying the channel in real-time
21:12 < xray> on freenode
21:12 < xray> ?
21:13 < xray> https://lede-project.org/contact
21:13 < PigBot> Couldn't snarf url: HTTP Error 403: Bad Behavior. http://tinyurl.com/zqhh2sr
21:13 < xray> is it the lede-dev or the lede-adm with the updates
21:15 < xray> i joined both channels. We'll see what happens
21:15 < skiboy> lede-dev
21:16 < xray> thansk
21:16 < skiboy> lede-adm can only be posted in by people with +v
21:17 < xray> This should also patch dnsmasq
21:24 < skiboy> I had to scrub dnsmasq from my system.  It was leaking DNS when I was on my VPN.
21:24 < skiboy> Not like it was doing anything anyway.  dnsmasq doesn't cache DNS on desktop Ubuntu
21:25 < xray> check any device with Busybox
21:25 < xray> it may include dnsmasq
21:26 < xray> this includes cable modems
21:26 < xray> v2.78 has the fix
21:27 < xray> lede patched it https://github.com/lede-project/source/search?utf8=%E2%9C%93&q=dnsmasq&type=
21:27 < PigBot> Title: Search · dnsmasq · GitHub (at github.com) http://tinyurl.com/ycxonaoz
21:27 < xray> https://github.com/lede-project/source/blob/7ffb707576e8c635321275e9f118c8ad27d4c798/package/network/services/dnsmasq/Makefile
21:27 < PigBot> Title: source/Makefile at 7ffb707576e8c635321275e9f118c8ad27d4c798 · lede-project/source · GitHub (at github.com) http://tinyurl.com/yb54dy76
21:28 < xray> which will also be in 17.01.3
21:28 < xray> sorry thats 17.01.4
21:29 < xray> .3 was release before the comit for dnsmasq 2.78
21:36 < xray> I stand corrected v17.01.3 did get dnsmasq v2.78
21:36 < xray> https://lede-project.org/releases/17.01/changelog-17.01.3#
21:36 < PigBot> Couldn't snarf url: HTTP Error 403: Bad Behavior. http://tinyurl.com/ya8npnxm
22:09 <@rattle> Curious.  General question to all.  How much does this really matter in your environments?  At this point, there is so little we depend on sanity of the wire for.
22:10 <@rattle> Talked to several folks today who's threat assessment was basically "meh, boy that sucks" and little more..
22:12 <@rattle> WPA2 going kablooie means basically nothing in my world..  Might help an adversary enumerate better, but little else..  Genuinely curious who is being impacted in a real way...
22:30 < skiboy> Everything I run is FOSS, so it just means that I need to take some time to update about 5 or 6 devices
22:31 < skiboy> Ubuntu is already patched, patches for 3 routers coming soon, and patch for LineageOS phone coming when Google actually bothers to patch AOSP.
22:32 < skiboy> Google is a clusterfuck when it comes to device security
22:33 < skiboy> Apple had it right when they said that they were going to control the entire update process.  Google fucked up when they allowed both the carrier and the phone manufacturer (people who want you to but new phones) to control the update process.
22:36 < skiboy> AOSP updates should be the default base that gets updates, and everything else should be on top of that.  Updating 1 program means a whole 400MB firmware update
22:36 < skiboy> Which is absurd
22:37 < skiboy> We should have just gotten a phone with a proper mainline Linux system out of the gate, but Google decided to choose to be stupid
22:42 -!- remoford [~remo_lapt@c-69-137-84-154.hsd1.tn.comcast.net] has quit [Quit: Leaving.]
22:51 <@rattle> So like, same thing..  e2e rules...  the wire can suck it.
22:52 <@rattle> Lots of discussions about CA management, the clusterfuck of the CA regime, and training users to deal with alerts properly...
22:52 <@rattle> Eh?
22:57 < skiboy> What kinds of alerts?
--- Log closed Tue Oct 17 00:00:28 2017