mtchang / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 0 forks source link

Netatalk is compiled with shadow support #920

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install & configure netatalk
2. connect to afpd using a user account

What is the expected output? What do you see instead?
To authenticate correctly.

Instead it shows this:
Jul 24 09:44:35.511040 afpd[1326] {dsi_tcp.c:210} (I:DSI): AFP/TCP session from 
192.168.1.20:54722
Jul 24 09:44:35.513791 afpd[1326] {uams_dhx_passwd.c:107} (I:UAMS): dhx login: 
bogdan
Jul 24 09:44:35.514139 afpd[1326] {uams_dhx_passwd.c:113} (I:UAMS): no shadow 
passwd entry for bogdan

It works fine if I add the user manually to /etc/shadow but after a reboot the 
file is gone. 

What version of the product are you using? On what operating system?
3.4.3.6-064 firmware
entware netatalk (2.2.4-1)

Original issue reported on code.google.com by ice.bog...@gmail.com on 24 Jul 2013 at 7:52

GoogleCodeExporter commented 9 years ago
Try to add user "bogdan" via WebUI: USB Application - Network Neighborhood 
Share.

Original comment by andy.pad...@gmail.com on 24 Jul 2013 at 1:17

GoogleCodeExporter commented 9 years ago
I already have the user there.

Original comment by ice.bog...@gmail.com on 24 Jul 2013 at 1:19

GoogleCodeExporter commented 9 years ago
Hmm, afpd force used /etc/shadow, but firmware not used this.

You can fill /etc/shadow from script /etc/storage/started_script.sh. This 
script called after router initialized and started.

Original comment by andy.pad...@gmail.com on 24 Jul 2013 at 1:39

GoogleCodeExporter commented 9 years ago
Good ideea. Thank you.

Original comment by ice.bog...@gmail.com on 24 Jul 2013 at 1:42