Netatalk Frequently Asked Questions
-($Id: FAQ,v 1.5 2001-10-17 07:08:28 lancel Exp $)
+($Id: FAQ,v 1.12.8.1 2009-04-30 09:35:06 franklahm Exp $)
-----------------------------------------------------------------------------
Q2: What is this I keep seeing about asun?
Q3: How do I get the most recent version of Netatalk?
Q4: Can I get an almost current version of Netatalk without having to learn CVS?
+Q4a: Is there an RPM, package, or tarball for my platform?
Q5: I'm having massive file deletion problems!
Q6: I am having lots of file locking problems!
Q7: I'm getting this message in my logs:
Q12: Hidden files - what's up with that?
Q13: I get a "socket: Invalid argument" error when trying to start netatalk
under Linux. What is causing this?
-Q14: netatalk works over Appletalk, but my IP connections are refused, even
+Q14: Netatalk works over Appletalk, but my IP connections are refused, even
though I have enabled them in the configuration files.
Q15: I'm having Quark Express file locking problems, is there information on that?
Q16: I'm getting this error in Quark Express when trying to save a file to
Q24: I want to be able to allow users to change their passwords? How do
I enable this feature. Every time I try I get an error that it was
unable to save the password.
+Q25: Can a mount a Mac volume on my unix machine?
+Q26: Can I run Samba and Netatalk together to access the same files?
+Q27: Files I create on my Samba shares are invisible on the mac side.
+Q27a: How can I set netatalk to hide some files from the Samba (or
+ unix) sides?
+Q28: Files I create on my netatalk shares are invisible on the PC side.
+Q28a: How can I set Samba to hide the netatalk specific files (e.g.
+ .AppleDouble).
+Q29: I compiled Samba with the --with-netatalk flag. What did that do?
+Q30: What about the differences in naming schemes, and legal/illegal
+ characters between Windows, Macs (and unix?)
+Q31: Where can I get the cnid-db (Berkely DB) software? (needed for
+ --with-did=cnid)
+Q32: What about security in Netatalk?
+
-----------------------------------------------------------------------------
Q1: Where can I get more information on Netatalk?
-A: The current location of the actively developed netatalk project can be
- found on SourceForge, at: http:/www.sourceforge.net/projects/netatalk.
-
- There are (at least) two very active e-mail lists to which you can
- subscribe, the first, netatalk-admins, is for usage and basic
- setup/compile questions. It is NOT maintained at sourceforge, but rather
- at the University of Michigan, which was involved with a good deal of the
- early development.
-
- Subscribe by sending an e-mail to netatalk-admins-request@umich.edu with a
- subject of "subscribe" and a blank body. This can be very high volume, but
- usually a few messages a day.
-
- The archive is available at:
- ftp://terminator.rs.itd.umich.edu/unix/netatalk/ and is called
- netatalk-admins.mail. This is a ~6M mbox file. Previous archives are
- available there as well.
-
- Netatalk-devel list is more specific to coding and testing. It can be
- browsed at: http://www.geocrawler.com/redir-sf.php3?list=netatalk-devel,
- and subscribed to at:
- http://lists.sourceforge.net/lists/listinfo/netatalk-devel This varies in
- volume, but is usually moderately active.
-
- netatalk-docs is specific to documentation. It can be browsed at:
- http://www.geocrawler.com/redir-sf.php3?list=netatalk-docs
- and subscribed to at:
- http://lists.sourceforge.net/lists/listinfo/netatalk-docs
- As far as I can tell, this list is completely dead.
-
- There are older netatlk information sites at:
- http://www.umich.edu/~rsug/netatalk/index.html
- http://www.anders.com/projects/netatalk/ and many unices have their own
- sites and distributions (tarballs, rpm's, packages, etc.)
-
+A: Netatalk's home page can be found at:
+
+ http://netatalk.sourceforge.net/
+
+ Netatalk is maintained at SourceForge. The Netatalk project page on
+ SourceForge is located at:
+
+ http://sourceforge.net/projects/netatalk/
+
+ There are (at least) three very active e-mail lists to which you can
+ subscribe. The first, netatalk-admins, is for usage and setup/compile
+ questions. Subscription information as well as an archive are available at:
+
+ http://lists.sourceforge.net/lists/listinfo/netatalk-admins
+
+ This can be very high volume, but usually a few messages a day.
+
+ Netatalk-devel list is more specific to coding and testing. The archive
+ and more information can found at:
+
+ http://lists.sourceforge.net/lists/listinfo/netatalk-devel
+
+ This list varies in volume, but is usually moderately active.
+
+ Netatalk-docs is specific to documentation. For more information see:
+
+ http://lists.sourceforge.net/mailman/listinfo/netatalk-docs
+
+ There are other netatalk information sites. Some of these are no
+ longer actively updated, some are site-specific, but still have
+ good information:
+
+ http://www.anders.com/projects/netatalk/
+ http://www.faredge.com.au/netatalk/index.html
+
+
Q2: What is this I keep seeing about asun?
-A: Before netatalk moved to SourceForge, Adrian Sun (asun) had written
- some patches to netatalk which helped significantly with it's usability,
- especially using appleshareIP. These patches are still provided by many
- unix vendors. I believe all of these patches are included in the current
- Sourceforge versions.
+A: Before Netatalk moved to SourceForge, Adrian Sun (asun) had written
+ some patches to Netatalk which helped significantly with its usability,
+ especially using AppleShare IP. These patches are still provided by many
+ Unix vendors. All of these patches are included in the current SourceForge
+ versions.
Q3: How do I get the most recent version of Netatalk?
-A: Via CVS from Sourceforge.net. This is the actively maintained version
- of netatalk, changes are being made constantly, and therefore it is not
- suitable for production environments. The netatalk at Sourceforge is in
+A: Via CVS from SourceForge.net. This is the actively maintained version
+ of Netatalk, changes are being made constantly, and therefore it is not
+ suitable for production environments. The netatalk at SourceForge is in
Beta, so keep that in mind.
-
+
To create the CVS tree - from the directory you want to use as your CVS
root, run:
- % cvs -d:pserver:anonymous@cvs.netatalk.sourceforge.net:/cvsroot/netatalk login
+ % cvs -d:pserver:anonymous@cvs.netatalk.sf.net:/cvsroot/netatalk login
hit <enter> at the Password: prompt
- % cvs -z3
- -d:pserver:anonymous@cvs.netatalk.sourceforge.net:/cvsroot/netatalk co
- netatalk
+ % cvs -z3
+ -d:pserver:anonymous@cvs.netatalk.sf.net:/cvsroot/netatalk co
+ netatalk
- this will create a netatalk subdirectory, and check out all of the files.
+ This will create a netatalk subdirectory, and check out all of the files.
If you run this same command subsequently, you will update any files which
have changed (on the CVS server) since your last checkout.
-
+
Once you've done that, read the INSTALL file in the netatalk/ directory,
+ plus the CONFIGURE file. If you're installing from CVS, you'll most likely
+ need have some supplementary software installed, such as gmake. Some
+ systems work fine with make. Additional information can be found in doc/.
- plus the CONFIGURE file. You'll need to have some supplementary software
- installed, such as gmake. Additional information can be found in docs/.
-
The main things to know, though, are this: you must run
+
+ % ./autogen.sh
+
+ in the netatalk/ directory first, in order to create your configure file.
- % ./autogen.sh in the netatalk/ directory first, in order to create your
- configure file.
-
- Then run % ./configure --help | more in order to get a
- feel for which compile flags are available. Some of these flags are
- summarized below.
+ Then run
+
+ % ./configure --help | more
+
+ in order to get a feel for which compile flags are available. Some of these
+ flags are summarized below, some are summarized in the INSTALL file, and
+ some have individual README files.
- To learn more about CVS, a good place to start is: http://www.cvshome.org,
- or http://www.cvshome.org/docs/manual, or
- http://www.cvshome.org/form/form.cgi (this is the FAQ).
+ To learn more about CVS, good places to start are:
+
+ http://www.cvshome.org
+ http://www.cvshome.org/docs/manual
+ http://www.cvshome.org/form/form.cgi (this is the FAQ)
+
+ There are GUI CVS systems for Windows and MacOS. Search on SourceForge for
+ WinCVS or MacCVS.
Q4: Can I get an almost current version of Netatalk without having to learn CVS?
-A: Yes. Weekly (or thereabouts) snapshots of the CVS tree should be
- posted for the benefit of those that don't want to / can't use CVS. As of
- 10/3/01, these were being put up at:
-
- ftp://ftp.marcuscom.com/pub/netatalk/nightly
-
- From the mail archives:
- I have started an archive of nightly CVS snap shots that build a tar.gz of
- netatalk ready to configure and build. The images can be downloaded from:
-
- ftp://ftp.marcuscom.com/pub/netatalk/nightly
- This site only allows active FTP, so the snaps are also available at:
- http://www.marcuscom.com/netatalk/nightly
+A: Yes. Daily snapshots of the CVS tree should be posted for the benefit of
+ those that don't want to / can't use CVS. They are available at:
+
+ http://www.marcuscom.com/netatalk/nightly/
You should be able to treat these images as you would a release. Just
configure as you normally work, then run make (or gmake as the case may
- be). There is no need to run autogen.sh on these images. Please let me
- know if you have any problems with these images. Thanks. -Joe
+ be). There is no need to run autogen.sh on these images.
+
+
+Q4a: Is there an RPM, package, or tarball for my platform?
+
+A: Perhaps. These vary in how often they're updated:
+
+ FreeBSD
+ port: /usr/ports/net/netatalk - maintained by Joe Clark
+ SuSE Linux
+ included in the distribution
+ OpenBSD
+ port: /usr/ports/net/netatalk/ - not actively maintained
+ Debian GNU/Linux
+ included in all current distributions
+ RedHat Linux
+ included in the distribution
Q5: I'm having massive file deletion problems!
+
Q6: I am having lots of file locking problems!
+
Q7: I'm getting this message in my logs:
WARNING: DID conflict for ... Are these the same file?
A: Compile with the --with-did=last flag set. This activates a different
method of calculating inodes in the software, and will hopefully fix some
of these problems. This code, along with the CNID code, was still being
- worked out in Pre7. The cnid/db3 flags also go along with this:
- --enable-cnid-db use persistent cnid database per volume (EXPERIMENTAL)
- --with-db3=PATH specify path to Berkeley DB3 installation
- --with-did=[scheme] set DID scheme (last,mtab)
+ worked out in Pre7. The cnid/bdb flags also go along with this:
+
+ --with-bdb=PATH specify path to Berkeley DB installation
+ --with-did=[scheme] set DID scheme (cnid,last)
- (For more information on CNID, see the README.cnid file, into which I just
- copied wholesale Joe's comments on what he did with cnid and lastdid.)
+ (For more information on CNID, see the README.cnid file.)
--with-did=last reverted things back to the old 1.4b2 directory ID
calculation algorithm. This also solved the problem of the syslog
or not.
-Q8: I can't seem to use passwords longer than 8 characters for my netatalk
+Q8: I can't seem to use passwords longer than 8 characters for my Netatalk
accounts. How can I fix that?
Q9: I would like to use encrypted passwords to authenticate to the Netatalk
A: Update to a newer version of AppleShare Client (I think the most
recent is 3.8.8). This allows longer passwords, and will allow you to
use encrypted passwords. Set which way you would like to authenticate
- in either afpd.conf or netatalk.conf, depending on your set up.
+ in either afpd.conf or netatalk.conf, depending on your setup.
+
+ For more information on the AppleShare Client from Apple, and which clients
+ are needed for which MacOS, see
+
+ http://til.info.apple.com/techinfo.nsf/artnum/n60792?OpenDocument&software
+
+ (this site requires cookies, and a registration and sign-in).
Q10: How can I set who has access to certain directories?
-A: You can certainly do this with your unix permissions, but also explore the
+A: You can certainly do this with your Unix permissions, but also explore the
allow/deny/rwlist/rolist options in the AppleVolumes.default file:
- # allow/deny/rwlist/rolist format [syntax: allow:user1,@group]:
- # user1,@group,user2 -> allows/denies access from listed users/groups
- # rwlist/rolist control whether or not the
- # volume is ro for those users.
+ # allow/deny/rwlist/rolist format [syntax: allow:user1,@group]:
+ # user1,@group,user2 -> allows/denies access from listed users/groups
+ # rwlist/rolist control whether or not the
+ # volume is ro for those users.
- Also, some unices, specically FreeBSD, have other options:
+ Also, some unices, specially FreeBSD, have other options:
(By Joe Clark)
"What about file and directory permissions? Since I didn't use the FORCE
Q11: What are the .AppleDouble and .Parent directories which are created in
- the netatalk locations?
+ the Netatalk locations?
-A: (also mention samba veto files, and the appledouble/MSwindows options
- in AppleVolumes.default
+A: See the README.veto file in this directory.
- The .AppleDouble folders hold the resource fork information for the mac
+ The .AppleDouble folders hold the resource fork information for the Mac
files, plus other attributes which are not normally stored by Unix. For
- this reason, when you want to move files around in your mac volumes, it's
- a good idea to do it from the Mac side (as opposed to from the unix side,
+ this reason, when you want to move files around in your Mac volumes, it's
+ a good idea to do it from the Mac side (as opposed to from the Unix side,
or Samba), unless you make absolutely sure you get the .AppleDouble
directories. These directories are often hidden from the Samba side, via
the veto files configuration.
- You can also set netatalk to not create an .AppleDouble directory unless
+ You can also set Netatalk to not create an .AppleDouble directory unless
it absolutely needs it, by setting the noadouble setting in
AppleVolumes.default.
A: If you set the noadouble flag in AppleVolumes.default, you won't see
the .Apple* or .Parent directories on the Mac side. If you use the veto
- files option in Samba, they may be hidden from the windows side as well.
+ files option in Samba, they may be hidden from the Windows side as well.
+ (More information in the Samba section, and in the README.veto file in
+ this directory.)
-Q13: I get a "socket: Invalid argument" error when trying to start netatalk
+Q13: I get a "socket: Invalid argument" error when trying to start Netatalk
under Linux. What is causing this?
A: The "appletalk" and "ipddp" kernel modules have to be installed under
- linux for netatalk to function. The appletalk module can be automatically
+ linux for Netatalk to function. The appletalk module can be automatically
loaded by adding the line "alias net-pf-5 appletalk" to the
/etc/modules.conf file. Issuing the command "modprobe (module)" will
load the module for the current session.
-Q14: netatalk works over Appletalk, but my IP connections are refused, even
+Q14: Netatalk works over AppleTalk, but my IP connections are refused, even
though I have enabled them in the configuration files.
-A: If tcp_wrappers support is compiled into netatalk, access has to be
- granted in /etc/hosts.allow for netatalk to successfully accept IP
+A: If tcp_wrappers support is compiled into Netatalk, access has to be
+ granted in /etc/hosts.allow for Netatalk to successfully accept IP
connections. This can be done by the addition of the line:
- afpd: 127. xxx.xxx.xxx. (whatever other subnets)
+
+ afpd: 127. xxx.xxx.xxx. (whatever other subnets)
-Q15: I'm having Quark Express file locking problems, is there information on that?
+Q15: I'm having Quark Express file locking problems, is there information on
+ that?
-A: Yes, see below about the --enable-did= flag. Also, try using the
- --flock-locks flag. Enabling this code disabled the new byte locking
- feature. With FLOCK locks, the whole file would be locked. With byte
- locks, a byte range could be locked without locking the whole file.
+A: Yes, see the question regarding DID conflicts and the --enable-did= flag.
+ Also, try using the --flock-locks flag. Enabling this code disabled the
+ new byte locking feature. With FLOCK locks, the whole file would be locked.
+ With byte locks, a byte range could be locked without locking the whole
+ file.
Q16: I'm getting this error in Quark Express when trying to save a file to
A: Turn off the document preview feature off in Quark.
-Q17: Does netatalk work with Mac OSX?
+Q17: Does netatalk work with MacOS X?
A: Yes, but only the most recent versions, and it's still being finalized.
Versions prior to 1.5Pre7 did NOT work with OS X, although some really
early versions did (netatalk 1.4+asun?).
-Q18: I'm getting an 'Application for this document not found' error on OS X.
+Q18: I'm getting an 'Application for this document not found' error on MacOS X.
-Q19: I'm getting an 'Error Type -43' error on OS X.
+Q19: I'm getting an 'Error Type -43' error on MacOS X.
-A: Configure with --with-did=last. More info on this flag is below.
+A: Configure with --with-did=last. More info on this flag is given in the
+ DID conflicts question.
Q20: How do I get the directories that are created by Netatalk to have the
correct permissions by default?
-A: Investigate the SetGid bit on your unix platform. It's a good idea to
+A: Investigate the setgid bit on your Unix platform. It's a good idea to
set this on your shared directories, and your .AppleDouble directories.
From the mail archives: "Usually directories designated for use with
AppleShare have the setgid (g+s) bit set. It forces inheritance of
permissions. Without it, the .AppleDouble subdirectory can't be created
since the new folder doesn't necessarily have the same write privileges."
-
- Also: Evi Nemeth's "Unix System Administration Handbook" which is chock
- full of useful advice (and one or two pieces of not-so good advice, but
- even those are debatable). Here's what it says about setguid (3rd. ed,
- chap 5.5, pg. 69):
-
+
+ Information about the setgid bit can be found in Evi Nemeth's
+ "Unix System Administration Handbook" (3rd. ed, chap 5.5, pg. 69):
+
"The bits with octal values 4000 and 2000 are the setuid and setgid bits.
- These bits allow programs to acess files and processes that would
- otherwise be off-limits to the users that run them. ... When set on a
+ These bits allow programs to access files and processes that would
+ otherwise be off-limits to the users that run them. [...] When set on a
directory, the setgid bit causes newly created files within the directory
to take on the group membership of the directory rather than the defualt
group of the user that created the file. This convention makes it easier
to share a directory of files among several users, as long as they all
belong to a common group. Check your system before relying on this
- feature, since not all version of UNIX provide it. ... This interpretation
+ feature, since not all version of UNIX provide it. [...] This interpretation
of the setgid bit is unrelated to it's meaning when set on an executable
file, but there is never any ambiguity as to which meaning is
- appropriate." (any typos are mine)
+ appropriate."
- NOTE: The SETUID is usually discussed along with the SetGID bit. The
- SetUID bit is VERY dangerous. If you set it on an executable, and the
+ NOTE: The setuid is usually discussed along with the setgid bit. The
+ setuid bit is VERY dangerous. If you set it on an executable, and the
executable is owned by root, anyone who runs that executable is root for
the duration of that executable's run, so a clever person can leverage
- that into a full-scale compromise. The SETGID bit also has implications
- that way, so be careful where you set it.
+ that into a full-scale compromise. The setgid bit also has other security
+ implications, so be careful where you set it.
- You set it by doing a chmod 2777 or 2775, or whatever. It's that first 2 bit.
+ You set it by doing a chmod 2xxx, where xxx are the normal file permissions
+ (i.e. owner/group/other permissions).
Q21: What does this error mean:
A: This can be due to a few things.
- 1) The SetGid bit might not be set on either your directory, or on the
- .AppleDouble directory. I think the bit has to be set recursively on the
- .AppleDouble folder.
+ 1) The setgid bit might not be set on either your directory, or on the
+ .AppleDouble directory. It has to be set recursively on the .AppleDouble
+ folder.
2) You may not be member of the group set on the directory you're trying
to write to.
Q22: I'm having problems with the Trash folder: either when someone drags
- files into it, the system want's them todelete them immeidately, or files
+ files into it, the system wants them to delete them immediately, or files
get stuck in there and won't delete.
A: chmod the Network Trash folder to 2775 (/home/public/Network Trash
Folder for instance).
+ As of 10/16/01, MacOS X trash didn't work properly with afps volumes.
+ Apple is working on it.
Q23: The daemons aren't starting, things aren't showing up in the Chooser,
and I get a message like this in the logs: afpd[####]: Can't register
This is sometimes a result of missing NIC information in the atalkd.conf
file. Put your network interface (something like le0, eth0, fxp0, lo0)
alone on a line in atalkd.conf, and reboot. When atalkd starts, it will
- populate the file with a line like: le1 -seed -phase 2 -addr 66.6 -net
- 66-67 -zone "No Parking"
+ populate the file with a line such as:
+
+ le1 -seed -phase 2 -addr 66.6 -net 66-67 -zone "No Parking"
To find your network interface, run
- % ifconfig -a | more
+ % ifconfig -a | more
+
and see which interface has your IP address. Use that one.
-Q24: I want to be able to allow users to change their passwords? How do
- I enable this feature. Every time I try I get an error that it was
+
+Q24: I want to be able to allow users to change their passwords. How do
+ I enable this feature? Every time I try I get an error that it was
unable to save the password.
-A: Use -[no]setpassword in afpd.conf. This enables? disables the
- ability of clients to change their passwords
+A: Use -[no]setpassword in afpd.conf. This enables or disables the ability of
+ clients to change their passwords.
+
+
+Q25: Can a mount a Mac volume on my Unix machine?
+
+A: Well, maybe. MacOS X obviously might be able to do this with NFS.
+ Also, there is a program called afpfs which was designed to do this,
+ but is not actively maintained and has been reportedly highly unstable.
+ It should be available from:
+
+ http://www.panix.com/~dfoster/afpfs/
+
+Q26: Can I run Samba and Netatalk together to access the same files?
+
+A: Sure. Lots of us do. But there are some concerns. Quite often it's
+ useful, for instance, to hide files of one OS from the other. See
+ the AppleVolumes.default file in Netatalk, and investigate the veto
+ files option in Samba. (See the README.veto file.)
+
+ Also, when copying and moving files created on the Mac, it's better
+ to do that from the Mac, rather than from the Unix server or from
+ Samba. This is because the .AppleDouble folders hold the resource fork
+ information for the Mac files, plus other attributes which are not
+ normally stored by Unix.
+
+ You can also set Netatalk to not create an .AppleDouble directory unless
+ it absolutely needs it, by setting the noadouble setting in
+ AppleVolumes.default.
+
+
+Q27: Files I create on my Samba shares are invisible on the Mac side.
+
+A: Have you checked the AppleVolumes(.default? .sytem? I don't remember
+ which one hides files!) file?
+
+ How long are the file names? Names longer than 31 BYTES (not characters)
+ are not visible on the Mac side. This is because some old MacOS's don't
+ accept long names, and some Finders crash when they encounter them.
+ Therefore Netatalk hides long filenames to prevent crashes. If you
+ prefer Netatalk to truncate the names, use the --with-mangling ./configure
+ option when compiling Netatalk.
+
+ The BYTES distiction is made because there exist doublebyte fonts too,
+ which limit names to 15 chars.
+
+
+Q27a: How can I set Netatalk to hide some files created on the Samba
+ (or Unix) sides?
+
+A: AppleVolumes(.system or .default?) allows you to hide certain files.
+ This might be a good thing to set on, say, .cshrc, ssh keys, and
+ the like.
+
+
+Q28: Files I create on my Netatalk shares are invisible on the PC side.
+
+Q28a: How can I set Samba to hide the Netatalk specific files (e.g.
+ .AppleDouble).
+
+A: Check your Samba veto files option in smb.conf. It's often useful
+ to hide files like .AppleDouble or the network trash folder here.
+
+ Does the mac file have a \ or / in it? Would this cause Samba to
+ not see the file?
+
+
+Q29: I compiled Samba with the --with-netatalk flag. What did that do?
+
+A: Nothing. Some code was written (by a Samba developer?), but as of
+ Fall 2001, Samba doesn't utilize it.
+
+
+Q30: What about the differences in naming schemes, and legal/illegal
+ characters between Windows, Macs, and Unix?
+
+A: Check out the documentation about the 'mswindows' flag in
+ AppleVolumes.default. For instance, having / or \ or : in a name is
+ especially bad, as they are path seperators on Unix, Windows, and MacOS,
+ respectively). Educating the end user is important for this problem.
+
+
+Q31: Where can I get the cnid-db (Berkely DB) software? (needed for
+ --with-did=cnid)
+
+A: First check to see if your Unix has a port or package. If not,
+ Berkeley DB is available at:
+
+ http://www.sleepycat.com/download.html
+
+Q32: What about security in Netatalk?
+
+A: Most of the security for Netatalk must be derived from the
+ security of the Unix server on which it runs. Directory permissions,
+ valid users, firewalls, IP filters, file integrity checkers, etc.
+ are all part of the equation. That said, it is possible to configure
+ Netatalk to minimize access, and close potential security holes.
+
+ These two flags are especially important:
+
+ --with-tcp-wrappers: enable TCP wrappers support.
+
+ Enables Wietse Venema's network logger, also known as tcpd or
+ LOG_TCP. These programs log the client host name of incoming
+ telnet, ftp, rsh, rlogin, finger etc. requests. Security
+ options are: access control per host, domain and/or service;
+ detection of host name spoofing or host address spoofing;
+ booby traps to implement an early-warning system. TCP
+ Wrappers can be gotten at:
+
+ ftp://ftp.porcupine.org/pub/security/
+
+ Note, if you use TCP Wrappers, it would be a good idea to set your
+ afpd.conf file to disable DDP, or accept connections only on TCP.
+ You can also configure afpd to only run on a certain port, which
+ you can then let through your IPFilter.
+
+ --with-ssl-dirs=[PATH]: specify path to OpenSSL installation.
+
+ NOTE: This is dependent on the same directory layout as the
+ source distribution of OpenSSL. That is: include/ and
+ lib/ to be on the same level. Many .rpm formats do not
+ have their files laid out in this format.
+ The OpenSSL Project is a collaborative effort to develop a
+ robust, commercial-grade, full-featured, and Open Source
+ toolkit implementing the Secure Sockets Layer (SSL v2/v3)
+ and Transport Layer Security (TLS v1) protocols as well as a
+ full-strength general purpose cryptography library.
+ This is required to enable DHX login support, which
+ will encrypt all of the passwords being sent across the
+ connection. (Some old Mac clients don't support this, check
+ this FAQ for the section on AppleShare clients.)
+ Check to see if your Unix has OpenSSL already, or
+ get everything at:
+
+ http://www.openssl.org/
+
+ --with-libgcrypt-dir=[PATH]: specify path to Libgcrypt installation.
+
+ NOTE: This is dependent on the same directory layout as the
+ source distribution of Libgcrypt. That is: include/ and
+ lib/ to be on the same level.
+ This is required to enable DHX2 login support, which
+ will encrypt all of the passwords being sent across the
+ connection. (Some old Mac clients don't support this, check
+ this FAQ for the section on AppleShare clients.)
+ Check to see if your Unix has Libgcrypt already, or
+ get everything at:
+
+ http://directory.fsf.org/project/libgcrypt/
+
+ Be aware that on the volumes that are shared, some of the
+ special folders (.AppleDesktop, "Network Trash Folder") get
+ assigned. A lot of these get created as world-writable (because that's
+ what the Mac clients are expecting them to be) which is often quite
+ undesirable from the Unix system administrator's point of view.
+ Documenting this behavior could be a somewhat daunting task, but
+ highly desirable.
+
+ Shares can be set to be read/write only by certain people and groups.
+
+ The Netatalk code has not been through a major code audit. However,
+ it's Open Source, so if you want to do said audit, contact the
+ Netatalk maintainers (which can be done through the SourceForge site).
+ Has anyone tried to run Netatalk in a chroot jail? If so, please
+ share your experiences with the mailing lists.
projects / netatalk.git / blobdiff