Created attachment 670336 [details] Diff between a working and non-working (default) launcher scripts Description of problem: The wrapper startup script /usr/libexec/netatalk/netatalk.sh defines which UAMs (auth methods) to load. UAMs are implemented as shared libraries and have been renamed in 2.2.3. For example, uamx_dhx2.so became two different UAMs: uamx_dhx2_pam.so and uamx_dhx2_passwd.so. However, the wrapper script still loads UAMs using the old names. Attached is a diff that explains the problem concisely. I've set severity to high because this bug renders the package unusable. (Unless, of course, I've missed something and this is not a bug at all.) Version-Release number of selected component (if applicable): 2.2.3 How reproducible: 100% Steps to Reproduce: 1. Try connecting to a share running with netatalk 2.2.3 Actual results: Authentication fails. Expected results: Authentication succeeds. Additional info: http://www.blog.10deam.com/2012/07/03/netatalk-2-2-2-updates-uam-naming-convention/
This bug is already fixed in netatalk 2.2.4. http://sourceforge.net/p/netatalk/code/ci/61eb0f4ddde2c15ca16ab9aaabce3aa5927b8e05/ http://sourceforge.net/mailarchive/message.php?msg_id=29331051 http://sourceforge.net/mailarchive/message.php?msg_id=29120702
A cause is that a symbolic link is not made. WORKAROUND: # cd /usr/lib[64]/atalk # ln -s uams_pam.so uams_clrtxt.so # ln -s uams_dhx_pam.so uams_dhx.so # ln -s uams_dhx2_pam.so uams_dhx2.so
Instead of creating symbolic links, I followed the instructions at: http://kolbusa.livejournal.com/108495.html This seems to have worked for me.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.