Astra linux ntlm авторизация

ntlm_auth(1) — Linux man page

This tool is part of the samba(7) suite.

ntlm_auth is a helper utility that authenticates users using NT/LM authentication. It returns 0 if the users is authenticated successfully and 1 if access was denied. ntlm_auth uses winbind to access the user and authentication data for a domain. This utility is only intended to be used by other programs (currently Squid and mod_ntlm_winbind)

Operational Requirements

The winbindd(8) daemon must be operational for many of these commands to function.

Some of these commands also require access to the directory winbindd_privileged in $LOCKDIR. This should be done either by running this command as root or providing group access to the winbindd_privileged directory. For security reasons, this directory should not be world-accessable.

Options

—helper-protocol=PROTO Operate as a stdio-based helper. Valid helper protocols are:

squid-2.4-basic Server-side helper for use with Squid 2.4’s basic (plaintext) authentication. squid-2.5-basic Server-side helper for use with Squid 2.5’s basic (plaintext) authentication. squid-2.5-ntlmssp Server-side helper for use with Squid 2.5’s NTLMSSP authentication.

Requires access to the directory winbindd_privileged in $LOCKDIR. The protocol used is described here: http://devel.squid-cache.org/ntlm/squid_helper_protocol.html. This protocol has been extended to allow the NTLMSSP Negotiate packet to be included as an argument to the YR command. (Thus avoiding loss of information in the protocol exchange). ntlmssp-client-1 Client-side helper for use with arbitrary external programs that may wish to use Samba’s NTLMSSP authentication knowledge.

This helper is a client, and as such may be run by any user. The protocol used is effectively the reverse of the previous protocol. A YR command (without any arguments) starts the authentication exchange. gss-spnego Server-side helper that implements GSS-SPNEGO. This uses a protocol that is almost the same as squid-2.5-ntlmssp, but has some subtle differences that are undocumented outside the source at this stage.

Requires access to the directory winbindd_privileged in $LOCKDIR. gss-spnego-client Client-side helper that implements GSS-SPNEGO. This also uses a protocol similar to the above helpers, but is currently undocumented. ntlm-server-1 Server-side helper protocol, intended for use by a RADIUS server or the ‘winbind’ plugin for pppd, for the provision of MSCHAP and MSCHAPv2 authentication.

This protocol consists of lines in the form: Parameter: value and Parameter:: Base64-encode value. The presence of a single period . indicates that one side has finished supplying data to the other. (Which in turn could cause the helper to authenticate the user).

Читайте также:  Driver development for linux

Currently implemented parameters from the external program to the helper are:

Username The username, expected to be in Samba’s unix charset . NT-Domain The user’s domain, expected to be in Samba’s unix charset . Full-Username The fully qualified username, expected to be in Samba’s unix charset and qualified with the winbind separator . LANMAN-Challenge The 8 byte LANMAN Challenge value, generated randomly by the server, or (in cases such as MSCHAPv2) generated in some way by both the server and the client. LANMAN-Response The 24 byte LANMAN Response value, calculated from the user’s password and the supplied LANMAN Challenge. Typically, this is provided over the network by a client wishing to authenticate. NT-Response The >= 24 byte NT Response calculated from the user’s password and the supplied LANMAN Challenge. Typically, this is provided over the network by a client wishing to authenticate. Password The user’s password. This would be provided by a network client, if the helper is being used in a legacy situation that exposes plaintext passwords in this way. Request-User-Session-Key Upon successful authenticaiton, return the user session key associated with the login. Request-LanMan-Session-Key Upon successful authenticaiton, return the LANMAN session key associated with the login. Warning Implementers should take care to base64 encode

any data (such as usernames/passwords) that may contain malicous user data, such as

a newline. They may also need to decode strings from

the helper, which likewise may have been base64 encoded..sp .5v —username=USERNAME Specify username of user to authenticate —domain=DOMAIN Specify domain of user to authenticate —workstation=WORKSTATION Specify the workstation the user authenticated from —challenge=STRING NTLM challenge (in HEXADECIMAL) —lm-response=RESPONSE LM Response to the challenge (in HEXADECIMAL) —nt-response=RESPONSE NT or NTLMv2 Response to the challenge (in HEXADECIMAL) —password=PASSWORD User’s plaintext password

If not specified on the command line, this is prompted for when required.

For the NTLMSSP based server roles, this parameter specifies the expected password, allowing testing without winbindd operational. —request-lm-key Retrieve LM session key —request-nt-key Request NT key —diagnostics Perform Diagnostics on the authentication chain. Uses the password from —password or prompts for one. —require-membership-of= Require that a user be a member of specified group (either name or SID) for authentication to succeed. -d|—debuglevel=level level is an integer from 0 to 10. The default value if this parameter is not specified is 0.

The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day-to-day running — it generates a small amount of information about operations carried out.

Читайте также:  How to check swap linux

Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic.

Note that specifying this parameter here will override the smb.conf.5.html# parameter in the smb.conf file. -V|—version Prints the program version number. -s|—configfile The file specified contains the configuration details required by the server. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. See smb.conf for more information. The default configuration file name is determined at compile time. -l|—log-basename=logdirectory Base directory name for log/debug files. The extension «.progname» will be appended (e.g. log.smbclient, log.smbd, etc. ). The log file is never removed by the client. -?|—help Print a summary of command line options.

Example Setup

To setup ntlm_auth for use by squid 2.5, with both basic and NTLMSSP authentication, the following should be placed in the squid.conf file.

auth_param ntlm program ntlm_auth --helper-protocol=squid-2.5-ntlmssp auth_param basic program ntlm_auth --helper-protocol=squid-2.5-basic auth_param basic children 5 auth_param basic realm Squid proxy-caching web server auth_param basic credentialsttl 2 hours 

This example assumes that ntlm_auth has been installed into your path, and that the group permissions on winbindd_privileged are as described above. To setup ntlm_auth for use by squid 2.5 with group limitation in addition to the above example, the following should be added to the squid.conf file.

auth_param ntlm program ntlm_auth --helper-protocol=squid-2.5-ntlmssp --require-membership-of='WORKGROUP\Domain Users' auth_param basic program ntlm_auth --helper-protocol=squid-2.5-basic --require-membership-of='WORKGROUP\Domain Users' 

Troubleshooting

If you’re experiencing problems with authenticating Internet Explorer running under MS Windows 9X or Millennium Edition against ntlm_auth’s NTLMSSP authentication helper (—helper-protocol=squid-2.5-ntlmssp), then please read the Microsoft Knowledge Base article #239869 and follow instructions described there.

Version

This man page is correct for version 3 of the Samba suite.

Author

The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed.

The ntlm_auth manpage was written by Jelmer Vernooij and Andrew Bartlett.

Источник

Настройка аутентификации NTLM в Apache2

В репозиториях Astra Linux Special Edition РУСБ.10015-01 (очередное обновление 1.7) пакет libapache2-mod-auth-ntlm-winbind отсутствует.

NTLM — встроенный в операционные системы семейства Microsoft Windows протокол сетевой аутентификации. Широко применяется в различных сервисах на их базе и используется версиями Microsoft Windows вплоть до Windows 10 включительно.

С самого изобретения протоколы NTLMv1 и NTLMv2 подвергались множеству нападений и демонстрировали широкий спектр серьёзных уязвимостей. В настоящее время рекомендуется использовать авторизацию через Kerberos.

Читайте также:  Adding crontab in linux

Описание стенда

  • имеется настроенный контроллер домена Windows AD:
    • имя winserver.windom.ex
    • адрес 10.0.2.20;
    • администратор домена
      • имя administrator
      • пароль 1234567890
      • winuser@windom.ex
      • пароль 0987654321

      Ввод в домен

      Действия выполняются на web-сервере. Ввод в домен выполняется с помощью инструмента astra-winbind.

      1. Перед вводом в домен настроить разрешение имен на использование контроллера DNS в качестве сервера DNS;
      2. Установить пакеты:

      Создание тестового сайта

      Для создания тестового сайта использовался сценарий из статьи Служба мониторинга ИБП APC apcupsd:

      При работе в Astra Linux Special Edition с включенным МРД в файле /etc/apache2/apache2.conf установить параметру Astra Mode значение off.

      sudo apt install apcupsd apcupsd-cgi apache2
      sudo a2enmod cgi
      sudo systemctl restart apache2
      firefox localhost/cgi-bin/apcupsd/multimon.cgi

      В результате выполнения сценария будет запущен web-браузер firefox со страницей статуса ИБП (если ИБП не подключен или не обнаружен — то с соответствующим сообщением об ошибке, не влияющем на использование сайта в качестве примера).

      Настройка аутентификации с помощью пакета libapache2-mod-auth-ntlm-winbind

      Установка пакета

      Проверка работы аутентификации

      1. Для первичной проверки можно использовать базовую версию протокола аутентификации, указав имена домена и пользователя и пароль пользователя:

      ntlm_auth —protocol=squid-2.5-ntlmssp —domain= <имя_домена>—username= —password=
      NT_STATUS_OK: The operation completed successfully. (0x0)

      ntlm_auth —protocol=squid-2.5-ntlmssp —domain= <имя_домена>—username= —password=
      NT_STATUS_NO_SUCH_USER: The specified account does not exist. (0xc0000064)

      Включение требования аутентификации на тестовом web-сайте

      Источник

      Клиент не подключается к домену

      Клиент не подключается к домену через f ly-admin-ad-client , astra-winbind или astra-ad-sssd-client .

      Диагностика

      • Проверить список доменов на экране входа — будут отображаться домены, которые пользователю не нужны.
        При попытке входа в нужный домен выводится ошибка вида:

      Возможная причина: Большое число дочерних доменов . Перейти к решению.

      Failed to join domain: failed to lookup DC info for domain '' over rpc: The request is not supported

      Возможная причина: Запрещена NTLM-аутентификация на контроллере домена . Перейти к решению.

      "Couldn't get kerberos ticket for: user@xxxxxxxxxx: KDC reply did not match expectations"

      Возможная причина: Имя домена указано в нижнем регистре . Перейти к решению.

      Bad SMB2 signature for message [0000] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 . . [0000] DB E7 09 DA 72 82 F9 CC D3 0E 4C 0A 11 3C 89 70 . r. ..L.. A process has requested access to an object but has not been granted those access rights.

      Возможная причина: Один IP-адрес у контроллера домена и клиента . Перейти к решению.

      Failed to join domain: failed to lookup DC info for domain 'windom.loc' over rpc: The transport connection has been reset. ! Joining the domain windom.loc failed realm: Не удалось присоединиться к области: Joining the domain windom.loc failed проблемы установки. подробности в файле /var/log/realmd-install.log
      Get-SmbServerConfiguration

      Источник

Оцените статью
Adblock
detector