× Few antiviral products inadequately detect 3proxy as Trojan.Daemonize, Backdoor.Daemonize, etc and many detect 3proxy as a PUA (potentially unwanted program). It may cause browser warning on download page. 3proxy is not trojan or backdoor and contains no functionality except described in documentation. Clear explanation of this fact is given, for example, in Microsoft's article.

3proxy_crypt

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
EXAMPLE
NOTES
BUGS
SEE ALSO
AUTHORS

NAME

3proxy_crypt - utility to generate encrypted passwords for 3proxy

SYNOPSIS

3proxy_crypt password
3proxy_crypt salt password

DESCRIPTION

3proxy_crypt is a utility to generate encrypted password hashes for use with 3proxy configuration. Encrypted passwords allow the system to avoid storing passwords in cleartext in configuration files.

When invoked with a single argument, it produces an NT password hash (MD4-based, suitable for NTLM authentication). The output is prefixed with NT:.

When invoked with two arguments (salt and password), it produces a BLAKE2b password hash. The salt length is limited to 64 characters. The output is prefixed with CR:.

The resulting hash can be used in the 3proxy configuration file with the users directive instead of a cleartext password.

OPTIONS

password

Cleartext password to encrypt.

salt

Salt string for BLAKE2b hashing (max 64 characters).

EXAMPLE

Generate NT password hash:

3proxy_crypt MySecretPassword

Result:

NT:3F7E6D8D96E8E7A9B0C1D2E3F4A5B6C7

Generate BLAKE2b password hash with salt:

3proxy_crypt MySalt MySecretPassword

Result:

CR:$3$MySalt$...

Using in 3proxy.cfg:

users user1:CR:$3$MySalt$...

NOTES

The NT hash uses the RSA MD4 Message-Digest Algorithm. The BLAKE2b hash uses the BLAKE2 cryptographic hash function.

When a password hash is prefixed with NT: or CR:, 3proxy uses the corresponding algorithm to verify passwords instead of comparing cleartext strings.

BUGS

Report all bugs to [email protected]

AUTHORS

3proxy is designed by Vladimir Dubrovin <[email protected]>