blocks|key|2597424|text|我发现了问题所在。原来是帕姆氏+auth模块问题！让我来描述一下我是如何找到解决方案的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2597425|上下文：|2597426|我设置了我的机器进行调试--也就是说，我打开了四个终端窗口。|2597427|1终端(本地机器)：这里，我正在执行ansible+prduction_server+-m+yum+-a+'name=vim+state=installed'+-b+-K+-u+username|unordered-list-item|CODE|2597428|第二终端(生产服务器)：在这里，我执行journalctl+-f+(系统宽日志)。|2597429|第三终端(生产服务器)：在这里，我执行了tail+-f+/var/log/secure+(用于sshd的日志)。|2597430|4终端(生产服务器)：这里，我正在编辑vi+/etc/pam.d/sudo文件。|2597431|每次我从1终端执行命令时，都会得到以下错误：|2597432|#+ansible+error+-+on+local+machine
Timeout+(7s)+waiting+for+privilege+escalation+prompt+error.|code-block|syntax|javascript|2597433|#+sshd+error+-+on+remote+machine
pam_unix(sudo:auth):+conversation+failed
pam_unix(sudo:auth):++[username]|2597434|我向我的同事展示了我的整个设置，他告诉我，这个错误必须使用"PAM“。坦率地说，这是我第一次听说帕姆。所以，我不得不读这个PAM教程。我发现，该错误与位于/etc/pam.d/sudo模块中的auth接口有关。在互联网上，我在这个pam_permit.so模块上结结巴巴地写着sufficient控制标志，解决了我的问题！|2597435|解决方案|2597436|基本上，我添加的是auth+sufficient+pam_permit.so行到/etc/pam.d/sudo文件中。请看下面的示例。|2597437|$+cat+/etc/pam.d/sudo
#%25PAM-1.0
#+Fixing+ssh+"auth+could+not+identify+password+for+[username]"
auth+++++++sufficient+++pam_permit.so

#+Below+is+original+config
auth+++++++include++++++system-auth
account++++include++++++system-auth
password+++include++++++system-auth
session++++optional+++++pam_keyinit.so+revoke
session++++required+++++pam_limits.so
session++++include++++++system-auth|2597438|结论：|2597439|我花了4天时间来解决这个问题。我偶然发现了许多不适合我的解决方案，从“ansible+host/config文件中的复制sudo密码”、"ldap特定配置“到从总是脾气暴躁的系统管理员那里得到建议！|2597440|注意：|2597441|由于我不是PAM方面的专家，所以我不知道此修复是否会影响系统的其他方面，所以请小心，不要盲目复制粘贴这段代码！不过，如果你是PAM专家，请与我们分享替代解决方案或投入。谢谢!|2597442|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Linux_PAM|1|2|https://linuxhint.com/linux_pam_tutorial/^0|G|4|C|3|0|0|0|0|0|3|I|27|0|0|4|J|D|0|0|4|K|N|0|0|3|J|I|0|4|3|0|0|0|25|F|2O|4|37|D|3U|A|1C|2|1|1P|5|2|0|0|9|T|14|F|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1T|8|@$9|1U|A|1V|B|C]]|D|@$9|1W|A|1X|1|1Y]]|E|$]]|$1|F|3|G|5|6|7|1Z|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|20|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|21|8|@$9|22|A|23|B|C]|$9|24|A|25|B|M]]|D|@]|E|$]]|$1|N|3|O|5|L|7|26|8|@$9|27|A|28|B|C]|$9|29|A|2A|B|M]]|D|@]|E|$]]|$1|P|3|Q|5|L|7|2B|8|@$9|2C|A|2D|B|C]|$9|2E|A|2F|B|M]]|D|@]|E|$]]|$1|R|3|S|5|L|7|2G|8|@$9|2H|A|2I|B|C]|$9|2J|A|2K|B|M]]|D|@]|E|$]]|$1|T|3|U|5|6|7|2L|8|@$9|2M|A|2N|B|C]]|D|@]|E|$]]|$1|V|3|W|5|X|7|2O|8|@]|D|@]|E|$Y|Z]]|$1|10|3|11|5|X|7|2P|8|@]|D|@]|E|$Y|Z]]|$1|12|3|13|5|6|7|2Q|8|@$9|2R|A|2S|B|C]|$9|2T|A|2U|B|C]|$9|2V|A|2W|B|M]|$9|2X|A|2Y|B|M]]|D|@$9|2Z|A|30|1|31]|$9|32|A|33|1|34]]|E|$]]|$1|14|3|15|5|6|7|35|8|@]|D|@]|E|$]]|$1|16|3|17|5|6|7|36|8|@$9|37|A|38|B|M]|$9|39|A|3A|B|M]]|D|@]|E|$]]|$1|18|3|19|5|X|7|3B|8|@]|D|@]|E|$Y|Z]]|$1|1A|3|1B|5|6|7|3C|8|@]|D|@]|E|$]]|$1|1C|3|1D|5|6|7|3D|8|@]|D|@]|E|$]]|$1|1E|3|1F|5|6|7|3E|8|@]|D|@]|E|$]]|$1|1G|3|1H|5|6|7|3F|8|@]|D|@]|E|$]]|$1|1I|3|-4|5|6|7|3G|8|@]|D|@]|E|$]]]|1J|$1K|$5|1L|1M|1N|E|$1O|1P]]|1Q|$5|1L|1M|1N|E|$1O|1P]]|1R|$5|1L|1M|1N|E|$1O|1S]]]]

I've found the problem. It turned out to be <a href="https://en.wikipedia.org/wiki/Linux_PAM" rel="noreferrer">PAM's</a> auth module problem! Let me describe how I got to the solution.
<h3>Context:</h3>
I set up my machine for debugging - that is I had four terminal windows opened.
<ul>
<li>1st terminal (local machine): Here, I was executing <code>ansible prduction_server -m yum -a 'name=vim state=installed' -b -K -u username</code></li>
<li>2nd terminal (production server): Here, I executed <code>journalctl -f</code> (system wide log).</li>
<li>3rd terminal (production server): Here, I executed <code>tail -f /var/log/secure</code> (log for sshd).</li>
<li>4th terminal (production server): Here, I was editing <code>vi /etc/pam.d/sudo</code> file.</li>
</ul>
Every time, I executed command from 1st terminal I got this errors:
<pre class="lang-sh prettyprint-override"><code># ansible error - on local machine
Timeout (7s) waiting for privilege escalation prompt error.
</code></pre>
<pre class="lang-sh prettyprint-override"><code># sshd error - on remote machine
pam_unix(sudo:auth): conversation failed
pam_unix(sudo:auth): [username]
</code></pre>
I showed my entire setup to my colleague, and he told me that the error had to do something with &quot;PAM&quot;. Frankly, It was the first time that I've heard about <a href="https://en.wikipedia.org/wiki/Linux_PAM" rel="noreferrer">PAM</a>. So, I had to read this <a href="https://linuxhint.com/linux_pam_tutorial/" rel="noreferrer">PAM Tutorial</a>.
I figured out, that error relates to auth interface located in /etc/pam.d/sudo module. Diging over the internet, I stambled upon this <code>pam_permit.so</code> module with <code>sufficient</code> controll flag, that fixed my problem!
<h3>Solution</h3>
Basically, what I added was <code>auth sufficient pam_permit.so</code> line to <code>/etc/pam.d/sudo</code> file. Look at the example below.
<pre class="lang-sh prettyprint-override"><code>$ cat /etc/pam.d/sudo
#%PAM-1.0
# Fixing ssh &quot;auth could not identify password for [username]&quot;
auth sufficient pam_permit.so

# Below is original config
auth include system-auth
account include system-auth
password include system-auth
session optional pam_keyinit.so revoke
session required pam_limits.so
session include system-auth
</code></pre>
<h3>Conclusion:</h3>
I spent 4 days to arrive to this solution. I stumbled upon over a dozens solutions that did not worked for me, starting from &quot;duplicated sudo password in ansible hosts/config file&quot;, &quot;ldap specific configuration&quot; to getting advice from always grumpy system admins!
<h3>Note:</h3>
Since, I'm not expert in PAM, I'm not aware if this fix affects other aspects of the system, so be cautious over blindly copy pasting this code! However, if you are expert on PAM please share with us alternative solutions or input. Thanks!

blocks|key|1156038|text|当我试图用apache2重新启动sudo+service+apache2+restart时，我也遇到了同样的错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1156039|当登录到root时，我能够看到真正的错误与apache2的配置有关。几个月前，我删除了一个站点的SSL-证书文件，但没有禁用apache2中的站点。a2dissite成功了。|1156040|entityMap^0|G|S|0|22|9|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

I got the same error when I tried to restart apache2 with <code>sudo service apache2 restart</code>

When logging into root I was able to see the real error lied with the configuration of apache2. Turned out I removed a site's SSL-Certificate files a few months ago but didn't disable the site in apache2. <code>a2dissite</code> did the trick.

blocks|key|1967106|text|假设lukas用户是一个本地帐户，您应该看看pam_unix.so模块是如何在您的system-auth+pam文件中声明的。但是关于用户帐户和pam配置的更多信息对于一个特定的答案是必要的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1967107|虽然添加了auth，但是足够的pam_permit.so足以获得访问。除了最不安全的测试环境之外，不推荐在任何情况下使用它。来自pam_permit手册页：|1967108|pam\_permit+is+a+PAM+module+that+always+permit+access.+It+does+nothing++++else.|blockquote|1967109|因此，以这种方式添加足以进行身份验证的pam_permit.so将完全绕过所有用户的安全性。|1967110|entityMap^0|2|5|M|B|15|B|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|X|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|N|$]]

Assuming the lukas user is a local account, you should look at how the pam_unix.so module is declared in your system-auth pam file. But more information about the user account and pam configuration is necessary for a specific answer.

<hr>

While adding auth sufficient pam_permit.so is enough to gain access. Using it in anything but the most insecure test environment would not be recommended. From the pam_permit man page:

<blockquote>
<pre><code> pam_permit is a PAM module that always permit access. It does nothing
 else.
</code></pre>
</blockquote>

So adding pam_permit.so as sufficient for authentication in this manner will completely bypass the security for all users.

blocks|key|2597532|text|自从使用pacman将sudo升级到1.9.4版本后，我就犯了这个错误。我没有注意到pacman提供了一个新的sudoers文件。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2597533|我只需要合并/etc/sudoers.pacnew。有关更多细节，请参见这里：帕斯维特|2597534|我知道这并没有回答最初的问题(它涉及Centos系统)，但是这是Google在错误信息方面的最高结果，所以我想我会把我的解决方案留在这里，以防有人偶然发现这个问题来自基于Arch+Linux的操作系统。|2597535|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.archlinux.org/index.php/Pacman/Pacnew_and_Pacsave^0|1J|7|0|6|J|13|4|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|H|3|I|5|6|7|10|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

I had this error since upgrading sudo to version 1.9.4 with pacman. I hadn't noticed that pacman had provided a new <code>sudoers</code> file.
I just needed to merge <code>/etc/sudoers.pacnew</code>.
See here for more details: <a href="https://wiki.archlinux.org/index.php/Pacman/Pacnew_and_Pacsave" rel="nofollow noreferrer">https://wiki.archlinux.org/index.php/Pacman/Pacnew_and_Pacsave</a>
I know that this doesn't answer the original question (which pertains to a Centos system), but this is the top Google result for the error message, so I thought I'd leave my solution here in case anyone stumbles across this problem coming from an Arch Linux based operating system.

blocks|key|2597601|text|我发现自己也处于同样的境地，把头发扯掉了。在我的例子中，隐藏在sudoers文件末尾的一行是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2597602|%25sudo+ALL=(ALL:ALL)+ALL|code-block|syntax|javascript|2597603|这就撤销了它之前的授权。如果您没有使用sudo组，那么可以安全地删除这一行。|2597604|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Found myself in the same situation, tearing my hair out. In my case, hidden toward the end of the sudoers file, there was the line:
<pre><code>%sudo ALL=(ALL:ALL) ALL
</code></pre>
This undoes authorizations that come before it. If you're not using the sudo group then this line can safely be deleted.

I'm using ansible to provision my Centos 7 produciton cluster. Unfortunately, execution of below command results with ansible <code>Tiemout</code> and Linux Pluggable Authentication Modules (pam) <code>error conversation failed</code>. 

The same ansible command works well, executed against virtual lab mad out of vagrant boxes.

<h3>Ansible Command</h3>

<pre class="lang-sh prettyprint-override"><code>$ ansible master_server -m yum -a 'name=vim state=installed' -b -K -u lukas -vvvv
123.123.123.123 | FAILED! =&gt; {
 "msg": "Timeout (7s) waiting for privilege escalation prompt: \u001b[?1h\u001b=\r\r"
}

</code></pre>

<h3>SSHd Log</h3>

<pre class="lang-sh prettyprint-override"><code># /var/log/secure
Aug 26 13:36:19 master_server sudo: pam_unix(sudo:auth): conversation failed
Aug 26 13:36:19 master_server sudo: pam_unix(sudo:auth): auth could not identify password for [lukas]
</code></pre>

pam_unix(sudo:auth): conversation failed, auth could not identify password for [username]

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在使用ansible来提供我的Centos 7产品集群。不幸的是，执行以下命令的结果是使用ansible Tiemout和(pam) error conversation failed。同样的ansible命令运行良好，可以在流浪汉盒之外的虚拟实验室中执行。不可接受的命令$ ansible master_serve...

问pam_unix(sudo: auth )：会话失败，auth无法识别[用户名]的密码
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问pam_unix(sudo: auth )：会话失败，auth无法识别[用户名]的密码EN