[nycbug-talk] [Fwd: Security Threat Watch 028]

[Pete Wright]

>
> You didn't say you had clients and servers running other operating 
> systems.  In any case, as Isaac points out, there are plenty of 
> implementations of AFP to choose from that more than likely work just 
> fine with your cheap linux/bsd fileservers.
>
shoot, dosn't look like i got ike's post, i only knew of netatalk.  i'd 
be really interested in checking them out.

>>>>>> sure, but its also a very chatty protocol, which is enough to  
>>>>>> generally
>>>>>> steer me away from it.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Are you sure you're not talking about AppleTalk, the network 
>>>>> layer  that AFP doesn't depend on or even typically use in OS X?
>>>>
>>>>
>>>>
>>>> so what does OS X use now on the "network" layer?
>>>> here's an interesting link regarding AppleTalk and the OSI layers:
>>>>
>>>>
>>>> http://developer.apple.com/documentation/mac/Networking/Networking 
>>>> -21.html
>>>
>>>
>>>
>>> TCP/IP / ZeroConf / Rendezvous / LDAP takes the place of AppleTalk.
>>>
>> which one is it by default?  i'm honestly interested.  i was under 
>> the assumption that DDP("AppleTalk") was being used when i enable 
>> "AppleTalk" in the OSX controll panel.  how else would OSX clients be 
>> able to play with OS 8/9 clients and vice-versa?
>
>
> TCP/IP - Base network layer
> ZeroConf - Gets an IP address without a DHCP server
> Rendezvous - Service discovery
> LDAP - More service discovery, SSO
> (ZeroConf and Rendezvous are actually the same spec, but I'm using the 
> names to mean different things)
>
> AppleTalk did all of these things.  When you enable AppleTalk in the 
> OS X control panel it's enabling AppleTalk, which allows it to talk to 
> OS8/9 clients and vice-versa.  AppleTalk is not on by default, because 
> they've replaced it with open standard technologies.
>

execellent, thanks for clearing that up!

-pete



-- 
~~~oO00Oo~~~
Pete Wright
pete at nomadlogic.org
www.nomadlogic.org/~pete