AFP from a Synology NAS

[ironborn65]

I have enabled AFP back in the Synology(*)

Initially all the files in the shared folder were sit archives, or hqx or disk images.
By chance I expanded a sit file in the shared folder from a connected Mac and to my surprise data and resource forks were preserved.
I can leave the uncompressed applications and take or put them from the connected Macs with ease.
When back in a modern Mac the uncompressed files (MacPing in this case) are shown like this:

I can now download the sit files from Basilisk II from a modern Mac and save the uncompressed app in the NAS AFP shared folder.
Which is perfect to me, quick and easy, stil I don't understand the magic under the hood.

(*) I prefer not to spend time in compiling, deploying, runing and config Netatalk, it's just me, I know it's not in comfort zone, I prefer to play with the macs instead, so I will live with the v3.

 

[nightingale]

Curious if this broke for you recently? I'm using an AFP share on my Synology for backup on my older macs, and just connect through TCP/IP. Never occurred to me to try that until I read this post. It worked flawlessly until the last update, and now I get this when I try to log in:



Seems there was an update to netatalk on the Synology. Are you having the same issue?

I found an article that explains how to re-enable legacy authentication, but I don't think you can manually edit the netatalk config file on a Synology: https://www.moria.us/blog/2021/03/mac-classic-hardware

 

[slipperygrey]

Curious if this broke for you recently? I'm using an AFP share on my Synology for backup on my older macs, and just connect through TCP/IP. Never occurred to me to try that until I read this post. It worked flawlessly until the last update, and now I get this when I try to log in:

View attachment 59717

Seems there was an update to netatalk on the Synology. Are you having the same issue?

I found an article that explains how to re-enable legacy authentication, but I don't think you can manually edit the netatalk config file on a Synology: https://www.moria.us/blog/2021/03/mac-classic-hardware

Are you able to check which version of openssl is used on your system after the update? There's a known issue where openssl 3.0 broke compatibility with the DHX UAM, which is what OS9 and other earlier Mac OS versions default to for authentication. See https://github.com/Netatalk/netatalk/issues/358

The workaround is to disable DHX, and use clrtxt and/or randnum UAMs (as your article alludes to)... OR to recompile netatalk with libressl or wolfssl.

Note that the DHX2 UAM is not affected by this issue. So later OSX and macOS versions can still authenticate with netatalk 3.1 out of the box.

 

[CTB]

I have had numerous Synology updates break my AFP server setup either via authentication or even making all my old uncompressed files useless. In the end I setup Netatalk 2.2.X on a RaspberryPi and have never had a problem. Also very easy to backup as I occasionally clone the SD card.