* thorso...@lavabit.com <thorso...@lavabit.com>: > Hi, > > Do you see any problems with this [1] guide? > > "Note: by changing the saslauthd path other applications that use > saslauthd may be affected." [1] > > How to check that I won't break other apps?
They fail? If you tell saslauthd to establish the authentication socket in a non default location you will have to tell all applications where that new location is or they will fail. The question is: Do you have any applications except for Postfix smtpd server that would need to use saslauthd as password verification service? If you don't, ignore the note and go on. > Also, I have some problems with this command: > > $ sudo dpkg-statoverride --force --update \ > > --add root sasl 755 /var/spool/postfix/var/run/saslauthd/ > dpkg-statoverride: warning: stripping trailing / > dpkg-statoverride: warning: An override for > '/var/spool/postfix/var/run/saslauthd' already exists, but --force > specified so will be ignored. That's a typical case of working against the system and breaking it. If you do an 'ls -ld ...' on the socket dir you will note it belongs to the group sasl and the group may access files in the dir. Add postfix to the sasl group: % adduser postfix sasl Then restart Postfix. Now Postfix' smtpd server is allowed to access the authentication socket. > How to run the command? Don't! Tell the author to fix his br0ken docs. And while you are at it, tell him there's no need to use vi when all he wants to do is _read_ a file. He can do with less and his system will be more secure - from him. ;) p@rick -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich
