Recent content by slipperygrey

dunno about "obsolete" -- web standards are generally designed to be backwards compatible and degrade gracefully it's not like this project is aiming to keep up with the latest multimedia, 3D accelerated canvas, enterprise grade requirement shenanigans :) I would chalk down the death of the...

the author of this project (kouta-kun) actually started a support request with Netatalk on this topic yesterday: https://github.com/Netatalk/netatalk/discussions/3149

FWIW, the author has given his permission to create derived work from his plugin and distribute under another license https://awesome.garden/@bytex64/116837837832445027 to his point, this is all based on an open standard, but still!

we have two hurdles to overcome to get bytex64's AURP dissector into Wireshark proper: it needs to be rewritten from Lua to C, as per the Wireshark Developer's Guide (unless we can make an argument that it absolutely has to be in Lua) bytex64 needs to apply a GPL-2.0-or-later compatible...

if it means we can leverage your work on the DDP stack for the small price of building some glue code and maintaining a protobuf, then it sounds like a fine tradeoff to me I only glanced through the code so maybe this is obvious, but I assume the tailtalk-broker would interface with atalkd...

I'm pleased to share my own mirror of the AFP Reference: https://afp.fyi/docs/reference/ My personal impetus for finally getting this cleaned up and published, rather than relying on the Wayback Machine copy, was that I kept finding blatant mistakes in the spec that needed correction. They are...

@Bolacore no butting in whatsoever, on the contrary I would say that it's beneficial to be running multiple PoCs in parallel to see what works best!

the commit is unambiguous with the intention: "Remove AppleTalk. Let it join hamradio in our out of tree protocol graveyard, I mean, repository."

@Bolacore just the fact that you have demonstrated a fully working DDP transport layer in userland is worth a lot, I think

you can ask @NJRoadfan if his A2SERVER fork is in good enough shape to test any RPi should run netatalk 4.5.0 well, you just have to compile it yourself unless you want to learn how to work with Docker containers, I wouldn't necessarily recommend that you go down that path – it is a good...

how did you start the AFP server -- via the netatalk controller daemon, or the afpd daemon directly? the former is the preferred way, because it will bring up the cnid_metad daemon for you (among other things) which is the daemon that orchestrates DBD database access through cnid_dbd daemon...

minor correction: "path" is indeed a legal option for the [Homes] section and will lead to this subdir being shared instead of the root of each user's home dir -- I leverage this option frequently since it's arguably preferable to sharing your entire home dir Ref...

@demik what driver are you using for your IISC? (i.e. in the Mac OS Chooser)

Impressive work, this will definitely come in handy when developing SCSI printer support in PiSCSI / BlueSCSI etc.

thanks for testing! indeed, the RandNum UAM has a special ritual that you have to do; do you know about the "afppasswd.key" trick for adding a layer of DES encryption on your local afppasswd file? it's well worth it to avoid keeping passwords in clear text on your file system (albeit in...