nicevorti.blogg.se

Netatalk 3.1 set user password
Netatalk 3.1 set user password








Or - use something like FUSE and sshfs (not AFP, but it's trivial to setup). Then in macOS, in Finder, use the Connect to Server and connect to: afp://127.0.0.1:10548

netatalk 3.1 set user password

This will start an ssh tunnel in the background tunneling from 10548 on your local machine to port 548 on the server. You can start an SSH tunnel as follows: ssh -f -N -L 10548::548 -i Traffic out on the wire is SSH encrypted, and authed using your cert. It's still not secure, and still using password-based auth, but it's limiting that traffic to within the machine itself. If you linux sys admin wants to use passwordless auth, then you're limited to setting up kerberos.Īlternatively, you could do something like setup an ssh tunnel to connect to the server, and send your AFP traffic through it, and just have the server listen on localhost, limited to accepting local requests. I don't think this is possible (authentication with OpenSSL cert), based on the linux man page, and the Apple tech documentation listing out authentication methods. This differs from Automatically mount AFP for Time Machine (without saving a password in plaintext) in that that answer has the server using a password, but then the Mac side pulls that password directly from the keychain. None of these in this MacWork Link seem to work without a password. My mount_afp command doesn't seem to work. But Mac Finder always asks for a password.

netatalk 3.1 set user password

So theoretically you'd think it would support the same public key login that SSH supports as well. The login for the AFP volume via netatalk is the SSH username:password.

#Netatalk 3.1 set user password Patch#

However I just set up netatalk to have an AFP volume. 0, although a newer version should also work however, the patch file has only been tested with version 3.1.0.

netatalk 3.1 set user password

So they're set up and my Mac can SSH to my Linux server with no password, np. It's fine and convenient for SSH access as it forces me to set up authorized_keys, which are so convenient once you set them up. I'm not going to be allowed to change that. My Linux server does not allow SSH login with password because I have /etc/ssh/sshd_config with "PasswordAuthentication no".








Netatalk 3.1 set user password