From Security Weekly Wiki
Jump to navigation
Jump to search
← Older edit
Newer edit →
Revision as of 17:19, 5 July 2007
3,648 bytes added
17:19, 5 July 2007
no edit summary
In Part II, we will show you how to implement a captive portal for guest authentication, and maybe even how to add some further layers of security such as intrusion detection and IP filtering.
= Listener Feedback and News =
[Larry] Jim S. writes:
<pre>In episode 76 when you were discussing the new WiFi distance record, Nick was saying you can't direct a radio wave in flight. We beg to differ. <pictures of waveguide></pre>
[Larry] - So,I went back and read everything I could on Intel's new wireless bending. We were waaaay off the mark. not in flight, but at transmit, for long range and "moving antennas". Only for slight variations!
[Larry] Chris B. writes:
On the last podcast you mentioned blackholing myspace on your home network. Instead of blackholing myspace, I elected to rate limit the traffic to the slowest possible allowed on my home Cisco 831 router, which comes out to the equivalent of about a 9600bps modem. This makes it very painful to browse as it takes a hell of a long time for the graphics to load.
I did this because I have family and a cousin that lives with us. They all know I work in computers/networks/security. Without just blocking the sites, I can blame the 'slowness' on the web site and not 'something I did'. Of course, the cousin gets his own limited user profile with no access to IE and a 'noscript' version of Firefox.
Anyway, I was wondering what myspace networks you were blackholing? I know they have a couple of CIDRs but they also use content distribution providers like Limelight networks and CWIE. The networks I have on the rate limited access list are:
And thanks for podcasting! </pre>
[Larry] - A couple of comments here. Honestly, to protect my (and paul's networks, wouldn't even make those address ranges work at a slow speed! It is not the speed of the attack, it is just the access. Paul, if I recall, you use your own internal caching name server (see book). and created a sone for *.myspace.com, and redirect them to 127.0.0.1. If you want myspace, go elsewhere. This makes it easier to get the big offender, but still allow some of the legit media distribution - akamai, and other providers.
[Larry] Shlomo D. writes:
<pre>I was thinking about what you guys said in Episode 72. It seems that
the most clueless tech people have access and are responsible for the
most important private information. I'm talking about HR. I know
that I wouldn't trust some of our HR people with a laptop, if I had a
choice. They are very nice people, but not clueful on privacy issues.
From what I hear from our helpdesk crew, they can barely use outlook.
Try explaining how to "print" to a pdf and they give you the thousand
yard stare. Now, put them in charge of 1000 people's confidential
information and I get worried.
You say, what about our Information Security people. Oh, them,
they're in the US, and I'm in Israel. Not only that, they're from Arab
countries and will NEVER come here. They scan our server subnet and
DMZ regularly. They complain here and there about technical issues or
about someone they find doing P2P. But company policy regarding HR
issues? No, ours is on their own and Info Sec doesn't deal with them
at all. Now I'm really worried.
Is there anything I can do about it? Probably not. I guess it's not
as much of an issue, b/c the payroll is on a closed system (seperate
PCs and network connections) and there is no SSN in this country, at
least nothing that is secret, everyone wants our Number for something.
Just my 2 cents worth. </pre>
[Larry] Wow, so much seems to be wrong here. Let's discuss - onsite, policies, education, identifiable information....
Retrieved from "
Application Security Weekly
Business Security Weekly
Enterprise Security Weekly
Paul's Security Weekly
Security Weekly News
Security And Compliance Weekly
Tradecraft Security Weekly
Security Weekly Links
About Security Weekly Wiki