Daniel Markstedt

When working on the 3.2.0 release notes, I was reminded that we have a fix for macOS generated EA metadata with https://github.com/Netatalk/netatalk/pull/575 – closing this PR for now while evaluating...

Sure, go for it. It seems Sonarcloud complains about this?

Looks good to me. Only question is the wolfcrypt header. I'm not sure what those data types are, and if it was me I'd leave them as-is. :)

@dgsga Sorry it's taking a while to wrap my head around this changeset. I trust your judgement of course, but I also want to internalize the logic changes.

@NJRoadfan One more task for this ticket is to update the documentation. At least the papd.conf(5) man page talks about using PPD files with CUPS.

Right, so I think this behavior should be captured in the docs, for instance.

For the record, I tweaked the papd docs slightly while merging https://github.com/Netatalk/netatalk/pull/1374 to explain the new PPD behavior.

It would be helpful to see the actual metadata assigned to the offending files/dirs. F.e. "/mnt/tank/home/stefan/.DS_Store" Compare the use of `getfaddr` in https://github.com/Netatalk/netatalk/issues/236#issuecomment-1657068707

@NJRoadfan Last year we worked through several "invalid metadata EA" reports and made the checking more forgiving in certain areas. A recurring one for directories was 0 length comment I...

> Okay, probably not the most elegant solution. I started removing ext attributes metadata from files. Then afpd will create them again. The following command does this recursively. Use it...