search for: troyan

...ries in /bin (that is /bin/something) when in single user mode. Binaries from /bin are dynamically linked and if run chrooted to /tmp , library loader will look for /tmp/etc/ld.so.conf and /tmp/lib/lib*.so . If you are attacked by an intruder, who knows what you have in your scripts, he may put his Troyan horses to those locations. "~root/" or "~user/" seem to be safier. Bash takes user''s home directory from /etc/passwd. When run in a script executed by bash, which was chrooted to /tmp , the /tmp/etc/passwd is consulted. Conclusions 1. Don''t use "~/&quot...

Hello, I have a few users that are often hit by a trojan virus that steals e-mail user and password. Having a very little (if not null) power on their machines, I need to be able to block the outgoing mail wich is handled by postfix via dovecot SASL. Blocking it at dovecot level would be optimal, for the virus doesn't necessarily use the e-mail of the user as its from, just the user and

...ies in /bin (that is /bin/something) when in single user mode. Binaries from /bin are dynamically linked and if run chrooted to /tmp , library loader will look for /tmp/etc/ld.so.conf and /tmp/lib/lib*.so . If you are attacked by an intruder, who knows what you have in your scripts, he may put his Troyan horses to those locations. "~root/" or "~user/" seem to be safier. Bash takes user's home directory from /etc/passwd. When run in a script executed by bash, which was chrooted to /tmp , the /tmp/etc/passwd is consulted. Conclusions 1. Don't use "~/" in sec...