search for: authreqd

Hi all, I just ran into a problem with rsync-2.6.0. Communication is between two Linux hosts. One host boots, detects the first, runs rsync to copy all data, and then shuts down again (to have a backup for the main server). In the environment during boot, in which rsync is running in client mode, neither USER nor LOGNAME variables are set. In this case, authenticate.c:auth_client gets passed

...tandard way to use kerberos. My idea is not too have a full pam implementation, juste a different way to authenticate users than the secret file and md4 challenge. I made a little experiment and it worked well. What I've done is changing the challenge command. Instead of sending @RSYNCD: AUTHREQD <challenge>, it just send "@RSYNCD: GSSAPI. Then gssapi bytes are exchanged and the user principal is returned instead of the rsync login. So the changes are small. Before submiting a full patch, I seek advice, do you think it's a good way to do that ? Some configuration files...

...return -1; } *************** *** 84,99 **** p = strchr(path,'/'); if (p) *p = 0; ! io_printf(fd,"%s\n",path); if (p) *p = '/'; while (1) { ! if (!read_line(fd, line, sizeof(line)-1)) { return -1; } if (strncmp(line,"@RSYNCD: AUTHREQD ",18) == 0) { ! auth_client(fd, user, line+18); continue; } --- 111,126 ---- p = strchr(path,'/'); if (p) *p = 0; ! io_printf(f_out,"%s\n",path); if (p) *p = '/'; while (1) { ! if (!read_line(f_in, line, sizeof(line)-1)) { retu...

Hi! I'm unable to write with remote rsync in daemon mode. ********* My configuration: rsync 2.6.2 Linux 2.4.20-alt16-up (ALTLinux www.altlinux.org) (There is owl-patch in ALTLinux-kernel) ========== /etc/rsyncd.conf ============= log file = /var/log/rsync [routers] comment = Our Backups path = /mnt/backup/routers uid = archiver gid = archiver use chroot = true read only = false list = true