Network security.

UUCP, like any other application, has compromised safety. Some of the highlights of his security, it is quite limited in what it can do, and therefore is more difficult to get to do something he should not, she has been there and most of the bugs its been discovered, analyzed and fixed, and because networks are made up UUCP links to other armies of the case, it is not possible to directly contact someone on Host B and take advantage of this connection to do something bad.

On the other hand, UUCP UUCP usually works with a user account system wide and password. Any system that has a connection to another UUCP must know the password for the account or nuucp uucp. Identification of a home beyond this point have always been little more than a matter of faith that the host is that it claims to be, and that connection is allowed at that time. Recently, there has been an additional layer of authentication, where both hosts must have the same number sequence, which is a number that is incremented each time a connection is established.

Therefore, if I run the host B, I know the password on the host uucp A. If so, I want to go home for C, I would have to conclude, identified as C, I hope at some point A, which will allow it, and try to guess the correct sequence number of the session. Even though this is not a small attack, it is considered very safe.