<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://permalink.gmane.org/gmane.comp.macosx.general">
    <title>gmane.comp.macosx.general</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57867"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57866"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57865"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57864"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57863"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57862"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57861"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57860"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57859"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57858"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57857"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57856"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57855"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57854"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57853"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57852"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57851"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57850"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57849"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.macosx.general/57848"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57867">
    <title>Re: Text mate and Reg-Ex?</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57867</link>
    <description>Not sure what you mean by "output" them, but here's how you would find  
all files in a dir that contain an input field followed by any  
characters and then one or more uppercase characters on the same line.

Create a TM project.
Cmd-Shift-F to search within the current project.
Turn regex on and Ignore Case off.
Regex:
&lt;input.*[A-Z]

Could be fine-tuned but that should get you close enough.

./s

On Oct 6, 2008, at 5:53 PM, J. Todd Slack wrote:



--
 &gt;&gt;&gt; Birdhouse Hosting &lt;&lt;&lt;
Custom web and mail hosting services
http://hosting.birdhouse.org
</description>
    <dc:creator>Hacker Scot</dc:creator>
    <dc:date>2008-10-07T06:23:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57866">
    <title>Text mate and Reg-Ex?</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57866</link>
    <description>Hi All,

a bit OT, but I use Text Mate and it has a way to search based upon  
RegEX.

I have a folder of HTML files where my HTML input boxes are structured  
like:

&lt;input type="text" name=ALL_CAPS" id="ALL_CAPS&gt;

Would there be a way to search this folder for all UPPERCASE only and  
output them?

I have a bunch of fields and I need to set them all to null in a PHP  
session and assign them all but going through each file and manually  
getting would take a ton of time. If outputed I could just copy and  
paste and not have *as much* manual work.

Get what i am saying? I hope that I am making sense.

-Jason
</description>
    <dc:creator>J. Todd Slack</dc:creator>
    <dc:date>2008-10-07T00:53:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57865">
    <title>Re: anyone using the new garmin mac software?</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57865</link>
    <description>
On Oct 4, 2008, at 4:54 AM, fracai wrote:


Side note: Virtually all non-Garmin-provided GPS software for the Mac  
sits on top of the open source GPSBabel library, which is fantastic.  
However, the gpsbabel team has had to program around some weird  
situations with non-conforming GPS units. One of the most problematic  
has been the inexpensive Venture HC. Its USB apparently works very  
differently from other units. Workarounds in gpsbabel that are present  
in the code to get other units working will crash a Mac hard when a  
Venture is plugged in. I hear they're on the brink of getting that  
fixed, but my general advice to Mac users who want to do anything  
beyond the basics with desktop GPS software (such as photo geocoding,  
geocache databasing, etc.) is *don't buy a Venture* (not that you were  
asking about the Venture - just getting the word out). All other units  
I've tested have worked fine.

./s


--
 &gt;&gt;&gt; Birdhouse Hosting &lt;&lt;&lt;
Custom web and mail hosting services
http://hosting.birdhouse.o</description>
    <dc:creator>Hacker Scot</dc:creator>
    <dc:date>2008-10-04T16:33:59</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57864">
    <title>Re: anyone using the new garmin mac software?</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57864</link>
    <description>
I've used the firmware and map update software.  It was pretty
straightforward, thought you have to go through some hoops to load map
updates.  You buy the update (or get a code for the free update after
purchasing) and receive a link to download the huge update.  That link
expires after a few weeks.  Run the update and enter the update code
that is paired with your GPS and the update.  The update runs and
you're good.

I haven't tried any other software yet (I think there's some for
loading routes and destinations), but if there's something in mind I
can bring it up.

We got a Nuvi 250w and it's been great.  It had the maps we'd need,
I've never been impressed with the road name speech tech, and I've
heard that the road conditions by radio aren't that reliable.

GPSPassion has a review of a variety of Mac software, there's a lot of
other good stuff regarding the nuvi line there as well.
http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=107981

There's also a potential logging hack that I didn't get a c</description>
    <dc:creator>fracai</dc:creator>
    <dc:date>2008-10-04T11:54:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57863">
    <title>anyone using the new garmin mac software?</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57863</link>
    <description>I'm looking for opinions on this before investing in a Nuvi

thanks

scott
</description>
    <dc:creator>Scott Anguish</dc:creator>
    <dc:date>2008-10-04T10:20:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57862">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57862</link>
    <description>
I really object to MAC address filtering being considered, or  
trumpeted, as 'security'; it is in that vein that I was replying.  
"Security by obscurity" (not broadcasting SSID) is NOT security.   
"Security by inconvenience" (MAC address filtering) is also not  
security. Calling MAC address filtering a "security measure" is a  
disservice to anyone stumbling across this thread who might believe you.


You don't need MAC address filtering to do that.  My WIFi router keeps  
track of MACs that connect and allows you to set fixed IPs to those  
MAC addresses.  This is quiet useful, but it has nothing to do with  
security.

If you want to have MAC address filtering to keep your employees in  
line and have cause to fire them if they are using unauthorized  
devices, that's fine.  But it still has nothing to do with security.

Want to know what the most security conscious solution is?

A public wifi that sits above your VPN and has no other access to  
anything except port 80 outbound.  Why?  Because most p</description>
    <dc:creator>LuKreme</dc:creator>
    <dc:date>2008-10-03T13:21:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57861">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57861</link>
    <description>_______________________________________________
MacOSX-talk mailing list
MacOSX-talk-sc6jspJ1wlD3oGB3hsPCZA&lt; at &gt;public.gmane.org
http://www.omnigroup.com/mailman/listinfo/macosx-talk
</description>
    <dc:creator>Jared Earle</dc:creator>
    <dc:date>2008-10-03T09:32:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57860">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57860</link>
    <description>
But since spoofing a MAC address is so trivial that it is a feature  
built in to most routers and a single command away on a Mac OS X  
machine, this is completely ineffective.  Security means having a  
strong encryption method (WPA2) and a strong password. No amount of  
MAC filtering will increase that security.


MAC address filtering is always superfluous.  The more sensitive your  
network is and the more important the data is on it, the more  
superfluous MAC filtering is.

</description>
    <dc:creator>LuKreme</dc:creator>
    <dc:date>2008-10-03T05:29:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57859">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57859</link>
    <description>
But it doesn't even stop those people.  You already have your WPA  
password to stop THOSE people.  Adding MAC address filters to that is  
just stupid.

</description>
    <dc:creator>LuKreme</dc:creator>
    <dc:date>2008-10-03T05:23:23</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57858">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57858</link>
    <description>

I can think of more one instance.

1) A company does not permit personal equipment on their network. It's  
a bit harder to enforce if WPA passwords are in use, since you just  
have to type it in. *

2) I run a small business and have a WiFi router by... say Linksys. It  
supports WPA2 and MAC filtering, and I don't really have a budget for  
much more. If I did MAC filtering and let an employee go, I could  
remove his MAC, thereby potentially inconveniencing the IT guy and the  
former employee. If I used only WPA instead of only MAC filtering, I  
could change the password, thereby inconveniencing every employee. *

3) MAC filtering is already used on the physical LAN at the DHCP  
server level, or is enforced via some super expensive NAC product. *

Notice I put an asterisk next to each of those examples. Yes, in EACH  
of those cases, you might potentially sniff out a valid MAC and spoof  
your WiFi card's address to get past this. That's you. MOST people  
will not and can not. The fact that a secur</description>
    <dc:creator>Scott Lewis</dc:creator>
    <dc:date>2008-10-03T00:43:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57857">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57857</link>
    <description>
On Oct 2, 2008, at 5:19 PM, Randal L. Schwartz wrote:



Did I say only a MAC address?

I'd rather have someone turned away at the MAC level then have them  
try to guess a password X number of times (obviously if they automate  
that then they can get past the MAC restriction).

I don't think ANYONE has advocated that you ONLY do the MAC thing.    
Only that it can help with the riffraff and Joe Common type of people  
to have it in addition.  The onion model of security were you have  
multiple layers.
</description>
    <dc:creator>objectwerks inc</dc:creator>
    <dc:date>2008-10-02T23:29:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57856">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57856</link>
    <description>
objectwerks&gt; The OP point is that the MAC address barrier keeps out the
objectwerks&gt; curious people who are not sniffing packets.  Just keeping out
objectwerks&gt; the riffraff who are not trying to break in but just find an open
objectwerks&gt; access point and snoop around where they can without effort.  It
objectwerks&gt; stops those people.  Which is most
objectwerks&gt; people.

As would a WPA password, which actually *is* effective.

Can you tell me one thing a MAC address gives you that a WPA wouldn't,
and why you would use only a MAC address then?

</description>
    <dc:creator>Randal L. Schwartz</dc:creator>
    <dc:date>2008-10-02T23:19:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57855">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57855</link>
    <description>
i don't filter MAC addresses, but the few times i've run into 
someone who does it's been when they wanted to let me on their 
network; first they have to remember they were using the filter, 
and the ensuing process of them getting my MAC address and then 
trying to figure out how to reconfigure their router has usually 
ended up with them just turning off the MAC address filter

that's inconvenient
</description>
    <dc:creator>steve harley</dc:creator>
    <dc:date>2008-10-02T23:06:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57854">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57854</link>
    <description>_______________________________________________
MacOSX-talk mailing list
MacOSX-talk-sc6jspJ1wlD3oGB3hsPCZA&lt; at &gt;public.gmane.org
http://www.omnigroup.com/mailman/listinfo/macosx-talk
</description>
    <dc:creator>objectwerks inc</dc:creator>
    <dc:date>2008-10-02T22:46:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57853">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57853</link>
    <description>_______________________________________________
MacOSX-talk mailing list
MacOSX-talk-sc6jspJ1wlD3oGB3hsPCZA&lt; at &gt;public.gmane.org
http://www.omnigroup.com/mailman/listinfo/macosx-talk
</description>
    <dc:creator>Jared Earle</dc:creator>
    <dc:date>2008-10-02T22:42:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57852">
    <title>Re: virtualization software</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57852</link>
    <description>
I've never had that happen before, where the s/w plain doesn't work or  
crashes out of the box. But you'd think if that was the case, they'd  
have the installation process check for incompatibility, or for  
updates, or at least a sheet of paper in the box that told you to  
check online. To leave the customer scratching his head when the app  
crashes on first launch is not very professional, IMHO. 
</description>
    <dc:creator>Jonathon Kuo</dc:creator>
    <dc:date>2008-10-02T22:20:54</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57851">
    <title>Re: virtualization software</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57851</link>
    <description>
On Oct 2, 2008, at 1:32 PM, Jonathon Kuo wrote:



That is often true for a lot of software.  The version in the box  
worked fine on the OS X version from 6 months ago but in the meantime  
things have changed and it no longer works.

Chad
</description>
    <dc:creator>objectwerks inc</dc:creator>
    <dc:date>2008-10-02T21:57:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57850">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57850</link>
    <description>

Well, the beauty of the WPA2 password is, I can leave the password  
with a few people like the principle, the pastors, and the church  
secretary, and if someone else needs to get on the network, I don't  
have to drive all across town some evening to let them on.  They'll be  
able to get on quickly.

-Andy
</description>
    <dc:creator>Andy Ringsmuth</dc:creator>
    <dc:date>2008-10-02T21:15:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57849">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57849</link>
    <description>

Not substituting. Augmenting. But hopefully something slightly harder  
to use for Joe Common (sniffer) then a zip tie (scissors or a few  
swipes with a key).


The good ones do. MANY don't.
</description>
    <dc:creator>Scott G. Lewis</dc:creator>
    <dc:date>2008-10-02T21:03:13</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57848">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57848</link>
    <description>
It's not appropriate for EVERY organization, for sure, but someone  
commented in an earlier reply that it was very inconvienent when "it  
forgot to setup your MAC address and you can't get on." Your super  
strong WPA2 password would qualify as equally annoying I suspect. :)  
But to me, it sounds like an acceptable solution.
</description>
    <dc:creator>Scott G. Lewis</dc:creator>
    <dc:date>2008-10-02T21:00:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.macosx.general/57847">
    <title>Re: Determining MAC address of a cell phone</title>
    <link>http://permalink.gmane.org/gmane.comp.macosx.general/57847</link>
    <description>

This is true, anyone who can sniff the traffic can find out the MAC  
and spoof it. But again, as an EXTRA (not the sole) form of security,  
it's effective. A) Most people don't sniff wireless traffic. B) Most  
people who merely want to see if there are any open, freely available  
Hotspots don't sniff traffic even if they know how. C) Anyone who  
maliciously wants to get on your network will get based this one form  
and move on to dealing with the others.

You state that filtering MAC addresses is worse, which is just not  
true. It's certainly worse as the SOLE method of security as compared  
to say WPA2, if you can only pick one method and have an off the shelf  
router without advanced authentication support like the Aeronet  
devices. But as *A* layer I can't see how having it is worse than not  
having it. If somebody sniffs out a valid MAC and joins the network  
with a spoofed address, it's not helping them defeat any other layers.  
But since some fantasticly high percentage of PC users are n</description>
    <dc:creator>Scott G. Lewis</dc:creator>
    <dc:date>2008-10-02T20:59:20</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.comp.macosx.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.macosx.general</link>
  </textinput>
</rdf:RDF>
