after a substantial development cycle, #netatalk v4.5.0 is now out of beta and ready for daily use

this the most feature-packed release from this project in a decade; to loosely quote the release notes:

making Finder search (i.e. Spotlight) usable out of the box, rebuilding the AFP directory cache for much larger and faster workloads, and tightening security across authentication, filesystem handling, parsers, and build defaults, bringing a new SRP authentication UAM, a pluggable Spotlight backend architecture, a modernized afpstats interface, and many portability improvements for Unix-like platforms like NetBSD and OpenBSD...

...and an additional 22 CVEs fixed

there is too much to list here, so check out the release notes for all the details:

https://netatalk.io/4.5/ReleaseNotes4.5.0

Netatalk Release Notes - 4.5.0

Netatalk Wiki

breaking news: #netatalk 4.4.3 is available, to which you should upgrade your deployments as soon as possible

this project has been hit recently by 4 security researchers independently filing (AI assisted) security vulnerabilities in quick succession; out of what ended up as 38 CVEs, we have decided to patch 20 of them in the stable branch.

the rest are either spurious or not exploitable / security sensitive at all

release notes: https://netatalk.io/4.4/ReleaseNotes4.4.3

security advisories: https://netatalk.io/security

Netatalk Release Notes - 4.4.3

Netatalk Wiki

@smallsco @theirongiant @nikdoof indeed, editing the wrong config file is a recurring pitfall (that I myself have fallen into more often than I like to admit) which is why I made sure there was a section on this in the Troubleshooting guide

the #netatalk build system does default to /usr/local/etc for config files, because this is the FHS compliant location for user installed software, and this has been the case since at least netatalk v3.2.0 (when we moved to meson)

a downstream packager can then customize this location to comply with the filesystem scheme of their particular OS distribution, which Debian does for example with /etc/netatalk

this is why you typically get totally different software installation paths with a binary package vs. building from source code, which can be obnoxious but an unavoidable quirk of Unix-like operating systems that you have to get used to

if you take a look at the Netatalk Compilation guide: https://netatalk.io/compilation

the Debian build example includes "-Dwith-pkgconfdir-path=/etc/netatalk" so that you get the customary config file path on that particular OS

HTH!

Netatalk - Compile Netatalk from Source

Netatalk Wiki

#netatalk #GlobalTalk - @kylew01 : did you read my latest edit about discovering the location of the actual in-use config file?

Now that I have #netatalk compiled for the Raspberry Pi, I'm now struggling to get any folder shared and advertised over AppleTalk, or AFP, for that matter. This is for #GlobalTalk.

edit : GOD DAMN IT. The documentation fails to mention that I should be editing THIS file:

/usr/local/etc/afp.conf.

I spent hours editing /etc/netatalk/afp.conf, and thought I was going insane.

I've been over the netatalk documentation multiple times last night. I tried setting log level to "default:debug9" but the journal isn't being spammed with events like I expect. So I don't even know where to start troubleshooting - permissions, an incorrect setting, etc.

The RPi is registered on my AppleTalk network just fine; I can see the device from my AIR Mac. It has a valid network number, and I can send AppleTalk echo packets to it with MacPing Pro (AT, not TCP).

Suggestions?

#GlobalTalk I cannot get meson setup to build #netatalk 4.4.2 because it thinks there's no database system available. I have installed both sqlite3 and mysql/mariadb, and I can't tell if Berkeley DB (dbd) is installed or even possible on this platform.

What am I missing?

Is this a known problem on Raspberry Pi's? I have a 3B+ running the latest Pi OS 13 (Trixie), released April 21. Is there a compatibility issue? Should I try an older version of Netatalk (4.3) or the 4.5 beta? Or is the OS too new and something broke the Netatalk build process? Or do I really need to configure a fully functional database ?

We had a fun breakthrough in #netatalk in recent days: the SRP (Secure Remote Password) user authentication method is now reverse engineered and supported by the open source AFP server.

Apple quietly added SRP to the AFP protocol some time in 2010 (our testing indicates OSX 10.7 Lion) but never acknowledged or documented it.

SRP caught my eye since it would offer roughly twice as strong encryption as DHX2 which is the final "official" UAM from Apple.

Luckily, SRP is an open standard and not an Apple proprietary technology: described in RFCs 2945 and 5054. So the reverse engineering was straight-forward, using consumer products that are known to support SRP, then brute force a few dozen potential parameters afforded by RFC 5054.

I did this write-up about the protocol and cryptographic mechanism as a sort of community specification.

https://netatalk.io/spec/SRP_UAM

The upcoming Netatalk v4.5 will support SRP!

Netatalk - AFP SRP User Authentication Method

Netatalk Wiki

#netatalk 4.5.0 beta is now available for adventurous users

https://netatalk.io/4.5/ReleaseNotes4.5.0beta

we have introduced advanced ARC cache and a wide range of deep optimizations that speed up file operations, especially noticeably when you enumerate a large number of files, i.e. when browsing a remote volume

see the new manual chapter on caching for instructions to to configure optimal cache for your deployment

https://github.com/Netatalk/netatalk/blob/main/doc/manual/Dircache.md

this is also the version where the friendly new color volume icons for Classic Mac OS announced a few weeks ago are fully functional

we've made a lot of changes under the hood, therefore this beta release to give you all a chance to poke around with it before we roll out a production ready version 🤞🏼

Netatalk Release Notes - 4.5.0beta

Netatalk Wiki

Сломал моск об #netatalk #afp
Есть две шары. Одна авторизованная, вторая только гости. Работает или одна или другая
PS зато кириллицу настроил как надо (MAC_CYRILLIC ←→ UTF-8)
UPD кажется дело в клиенте: нельзя к одной шаре подключаться с разными id. Двойной логин не работает ни на старом маке, ни на новом
We have a #netatalk dropbox for #marchintosh ! Usual method - delete everything and start again. The apparent reason for the problem was wrong permissions on the hidden directories inside the shares. Many thanks to those who helped! (PS Send me stuff - EtriNet :) )