Dearie
> Sent: Wednesday, March 02, 2022 at 12:16 AM
> From: "David Wright"
> To: debian-user@lists.debian.org
> Subject: Re: Authentication failed after su-
>
Please allow me to snip off large chunks of your tips in my reply.
> Substantively, they'
>
> $ su -l -c "wpa_passphrase myssid my_very_secret_passphrase >
> /etc/wpa_supplicant/wpa_supplicant.conf"
>
> The above command doesn't work in Debian 11. The output is:
>
> su: Authentication failed.
>
> In addition to yours, What are the valid comm
On Tue, 1 Mar 2022 10:28:32 +0100
Sven Hartge wrote:
> > What should I do to resolve the issue?
>
> Use sudo.
>
> wpa_passphrase JupiterRising 1234567890 | sudo tee
> /etc/wpa_supplicant/wpa_supplicant.conf
That will work. Another way to do it is to provide a password for root.
Something lik
Mein Schatzi
> Sent: Tuesday, March 01, 2022 at 5:28 PM
> From: "Sven Hartge"
> To: debian-user@lists.debian.org
> Subject: Re: Authentication failed after su-
>
>
> Use sudo.
>
> wpa_passphrase JupiterRising 1234567890 | sudo tee
> /etc/wpa_supplicant/w
Stella Ashburne wrote:
>> From: "Dan Ritter"
>>> In a terminal, I typed:
>>>
>>> username@hostname:~$ su -l -c "wpa_passphrase JupiterRising 1234567890 >
>>> /etc/wpa_supplicant/wpa_supplicant.conf"
>>> Password:
>>> su: Authentication failure
>> That means that you failed to give the root pas
Dearie
> Sent: Tuesday, March 01, 2022 at 5:47 AM
> From: "Bob McGowan"
> To: debian-user@lists.debian.org
> Subject: Re: Authentication failed after su-
>
> On 2/28/22 13:09, Dan Ritter wrote:
> > sudo su - -l -c "rest of the line"
>
> Some co
Dearie
> Sent: Tuesday, March 01, 2022 at 7:13 AM
> From: "Dan Ritter"
> To: "Stella Ashburne"
> Cc: debian-user@lists.debian.org
> Subject: Re: Authentication failed after su-
>
> >
> > In a terminal, I typed:
> >
> > username
On 2/28/22 13:09, Dan Ritter wrote:
sudo su - -l -c "rest of the line"
Some comments on this, without knowing just how it failed:
1. There is no reason I can see to using both 'sudo' and 'su'
together. By default, they both let you run a command as the root user.
2. Using both '-' and '-
Stella Ashburne wrote:
> > Sent: Tuesday, March 01, 2022 at 5:09 AM
> > From: "Dan Ritter"
> > To: "Stella Ashburne"
> > Cc: debian-user@lists.debian.org
> > Subject: Re: Authentication failed after su-
> >
> > Stella Ashburne
Dearie
> Sent: Tuesday, March 01, 2022 at 5:09 AM
> From: "Dan Ritter"
> To: "Stella Ashburne"
> Cc: debian-user@lists.debian.org
> Subject: Re: Authentication failed after su-
>
> Stella Ashburne wrote:
> > sudo su - -l -c "rest of the line&q
Stella Ashburne wrote:
> sudo su - -l -c "rest of the line"
>
> It didn't work
Copy and paste the actual error; they contain real information
to help us figure out what is happening.
-dsr-
Dearie
Thanks for your offer of help; however.
> Sent: Tuesday, March 01, 2022 at 3:10 AM
> From: "Andrew M.A. Cater"
> To: debian-user@lists.debian.org
> Subject: Re: Authentication failed after su-
>
>
> If you use sudo: prefix the above command with s
gt;
> su -l -c "wpa_passphrase myssid my_very_secret_passphrase >
> /etc/wpa_supplicant/wpa_supplicant.conf"
>
> The output of the terminal is: Authentication failed
>
> Any solution(s) please?
>
> Best regards.
>
> Stella
>
If you use sudo: prefix
plicant.conf"
The output of the terminal is: Authentication failed
Any solution(s) please?
Best regards.
Stella
;s assumed that server is not
> who the user intended to get to, and the connection is failed.
>
> In a web browser, this is what prompts the big red "This site isn't who
> they say they are, are you sure you trust them?" messages.
>
>>
>> WA
d.
In a web browser, this is what prompts the big red "This site isn't who
they say they are, are you sure you trust them?" messages.
>
> WARNING: Server hostname does not match certificate
>
> -- Mutt: SSL Certificate check (certificate 2 of 2 in chain)
> SASL authentic
The report ends with these lines.
Do you only get this problem with that site (the one that has it's SSL
wrongly configured so I can't check it)?
>
> WARNING: Server hostname does not match certificate
>
> -- Mutt: SSL Certificate check (certificate 2 of 2 in chain)
>
SL Certificate check (certificate 2 of 2 in chain)
SASL authentication failed
My interpretation is that mutt, or SASL on behalf of mutt, got
a certificate from websitewelcome. That certificate is authenticated
by a root certificate from COMODO. SASL found that
On 01/03/14 13:59, Peter Easthope wrote:
> In accord to https://wiki.debian.org/Mutt, these four lines are in .muttrc.
>
> set smtp_url = "smtps://pe...@easthope.ca:465" # ESMTP with TLS
> set smtp_pass="_"
> set from="pe...@easthope.ca"
> set realname="Pete"
>
> A test message yields th
rver hostname does not match certificate
-- Mutt: SSL Certificate check (certificate 2 of 2 in chain)
SASL authentication failed
--
Telephone 1 360 639 0202. Bcc: peter at easthope.ca "http://carnot.yi.org/ "
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a
El 2012-01-16 a las 14:40 -0500, tony baldwin escribió:
(resending to the list)
> On Sat, January 14, 2012 4:55 pm, Camaleón wrote:
> > On Sat, 14 Jan 2012 15:26:30 -0500, tony baldwin wrote:
> >
> >> On Sat, January 14, 2012 12:41 pm, Camaleón wrote:
> >
> > (...)
> >
> >>> Tony, I would forget
On Sat, 14 Jan 2012 15:26:30 -0500, tony baldwin wrote:
> On Sat, January 14, 2012 12:41 pm, Camale�n wrote:
(...)
>> Tony, I would forget about the SSL part until you have configured your
>> Postfix to be in a workable state (sending/receiving e-mails with no
>> errors). Afterwards, you can sta
On Sat, January 14, 2012 12:41 pm, Camale�n wrote:
> On Tue, 10 Jan 2012 20:09:21 -0500, Tony Baldwin wrote:
>
>> On Tue, Jan 10, 2012 at 08:01:17PM -0500, Tony Baldwin wrote:
>>> On Tue, Jan 10, 2012 at 05:21:24PM -0500, Tony Baldwin wrote:
>>> > On Tue, Jan 10, 2012 at 09:35:58PM +, Camaleón
On Tue, 10 Jan 2012 20:09:21 -0500, Tony Baldwin wrote:
> On Tue, Jan 10, 2012 at 08:01:17PM -0500, Tony Baldwin wrote:
>> On Tue, Jan 10, 2012 at 05:21:24PM -0500, Tony Baldwin wrote:
>> > On Tue, Jan 10, 2012 at 09:35:58PM +, Camaleón wrote:
>> > > On Tue, 10 Jan 2012 13:12:25 -0500, Tony Ba
On Tue, Jan 10, 2012 at 08:01:17PM -0500, Tony Baldwin wrote:
> On Tue, Jan 10, 2012 at 05:21:24PM -0500, Tony Baldwin wrote:
> > On Tue, Jan 10, 2012 at 09:35:58PM +, Camaleón wrote:
> > > On Tue, 10 Jan 2012 13:12:25 -0500, Tony Baldwin wrote:
> > >
> > > > On Tue, Jan 10, 2012 at 01:05:16PM
On Tue, Jan 10, 2012 at 05:21:24PM -0500, Tony Baldwin wrote:
> On Tue, Jan 10, 2012 at 09:35:58PM +, Camaleón wrote:
> > On Tue, 10 Jan 2012 13:12:25 -0500, Tony Baldwin wrote:
> >
> > > On Tue, Jan 10, 2012 at 01:05:16PM -0500, Tony Baldwin wrote:
> > >> On Tue, Jan 10, 2012 at 04:58:06PM +0
On Tue, Jan 10, 2012 at 09:35:58PM +, Camaleón wrote:
> On Tue, 10 Jan 2012 13:12:25 -0500, Tony Baldwin wrote:
>
> > On Tue, Jan 10, 2012 at 01:05:16PM -0500, Tony Baldwin wrote:
> >> On Tue, Jan 10, 2012 at 04:58:06PM +, Camaleón wrote:
>
> (...)
>
> >> Okay, at this point, I am gettin
On Tue, 10 Jan 2012 13:12:25 -0500, Tony Baldwin wrote:
> On Tue, Jan 10, 2012 at 01:05:16PM -0500, Tony Baldwin wrote:
>> On Tue, Jan 10, 2012 at 04:58:06PM +, Camaleón wrote:
(...)
>> > Mmmm, my guess is that your are having problems (or at least "one" of
>> > the problems, the other can b
On Tue, Jan 10, 2012 at 01:05:16PM -0500, Tony Baldwin wrote:
> On Tue, Jan 10, 2012 at 04:58:06PM +, Camaleón wrote:
> > On Mon, 09 Jan 2012 17:51:13 -0500, Tony Baldwin wrote:
> >
> > > I followed directions here:
> > > http://library.linode.com/email/postfix/dovecot-mysql-debian-6-squeeze#s
en when choosing
> > (o) accept once // no (a) accept all option here //
> > I get
> > Sasl authentication failed.
> >
> > The one thing that I question is this: hostname on the server gives me
> > $hostnamethatIassigned
> > hostname -f on that server give
either on that server or from home, collect mail from my
> domain with mutt, but when I try to send mail, I get a warning that the
> certificate hostname doesn't match the server, and, even when choosing
> (o) accept once // no (a) accept all option here //
> I get
> Sasl authen
>
> I can now, either on that server or from home, collect mail from my
> domain with mutt, but when I try to send mail, I get a warning that the
> certificate hostname doesn't match the server,
> and, even when choosing (o) accept once
> // no (a) accept all option here //
when I try to send mail, I get a warning that the
certificate hostname doesn't match the server,
and, even when choosing (o) accept once
// no (a) accept all option here //
I get
Sasl authentication failed.
The one thing that I question is this:
hostname on the server giv
On Sat, 2006-10-14 at 10:03 +0800, loveboy wrote:
> Hi,
> I updated all my software in this mornig.But when I reboot,all
> of the boot procedure is fine.But when I enter the user name, it
> display "Authentication failure". Can you help me?
>
Just an idea: during the upgrade your locale (an
Hi,I updated all my software in this mornig.But when I reboot,all of the boot procedure is fine.But when I enter the user name, it display "Authentication failure". Can you help me?
3G 时 代 来 临 了，坚 决 对 传 统 邮 箱 说 不 ！
新 一 代 极 速 3G 邮 箱 闪 亮 登 场 ，280 兆 网 盘 免 费 送 ！ 点 击 此 处 注 册
Hi All,
I have find the reason of the problem.
In our network are two PPPoE servers: cross and spider. I'm registered
in cross, but "pon dsl-provider" try to connect me to spider.
How can i explain to my pppoe client to use "cross" server??
pppd[7046]: Connect: ppp0 <--> eth0
Mar 12 23:01:37 localhost pppd[7046]: Couldn't increase MTU to 1500
Mar 12 23:01:37 localhost pppd[7046]: Couldn't increase MRU to 1500
Mar 12 23:01:40 localhost pppd[7046]: CHAP authentication failed: Invalid!!
Mar 12 23:01:40 localhost pppd[7
Hi All, I have problems with PPPOE.
It's my /etc/ppp/chap-secrets file:# Secrets for authentication using CHAP# client server secret IP addresses"my_login" * "my_password"I think I had that message too, many moons ago. The problem? I mixed up the username and password. Try flipping them.
How did y
Mar 2 12:30:54 localhost pppd[3346]: Couldn't increase MTU to 1500
Mar 2 12:30:54 localhost pppd[3346]: Couldn't increase MRU to 1500
Try to use MRU and MTU 1492 or 1452 as PPPoE requires
MIchal Sedlak
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Con
alhost pppd[3346]: Couldn't increase MTU to 1500
Mar 2 12:30:54 localhost pppd[3346]: Couldn't increase MRU to 1500
Mar 2 12:30:54 localhost pppd[3346]: Couldn't increase MRU to 1500
Mar 2 12:30:57 localhost pppd[3346]: CHAP authentication failed: Invalid!!
Mar 2 12:30:57 localhost pppd[3346]
e56bd43969a6f290ef2e077>, name = "robert210"]
> >Dec 29 20:40:30 ifi pppd[793]: rcvd [LCP EchoRep id=0x0 magic=0x0]
> >Dec 29 20:40:31 ifi pppd[793]: rcvd [CHAP Failure id=0x1 "\000"]
> >Dec 29 20:40:31 ifi pppd[793]: Remote message: ^@
> >Dec 29 20:4
:30 ifi pppd[793]: sent [CHAP Response id=0x1
<8b7464067e56bd43969a6f290ef2e077>, name = "robert210"]
Dec 29 20:40:30 ifi pppd[793]: rcvd [LCP EchoRep id=0x0 magic=0x0]
Dec 29 20:40:31 ifi pppd[793]: rcvd [CHAP Failure id=0x1 "\000"]
Dec 29 20:40:31 ifi pppd[793]: Remote message: ^@
Dec 29 20:4
=0x1
<8b7464067e56bd43969a6f290ef2e077>, name = "robert210"]
Dec 29 20:40:30 ifi pppd[793]: rcvd [LCP EchoRep id=0x0 magic=0x0]
Dec 29 20:40:31 ifi pppd[793]: rcvd [CHAP Failure id=0x1 "\000"]
Dec 29 20:40:31 ifi pppd[793]: Remote message: ^@
Dec 29 20:40:31 ifi pppd[79
> | Do you think it would be productive to contact the maintainer?
>
> Probaly not. LaMont knows he chroots the daemons for the debian
> package (it's a conscious change from the defaults Wietse ships
> postfix with).
He may know but I sure didn't. It would have helped a lot to at least mention
s
On Fri, Jan 09, 2004 at 09:51:09PM -0500, Michael B Allen wrote:
| Thanks as usual Derrick. I got it working. I believe the problem was
| that postfix opens the pwcheck UNIX domain socket in
| /var/spool/postfix/var/run/pwcheck whereas the pwcheck daemon opens
| it in /var/run/pwcheck.
Aha. That
Thanks as usual Derrick. I got it working. I believe the problem was that postfix
opens the pwcheck UNIX domain socket in /var/spool/postfix/var/run/pwcheck whereas
the pwcheck daemon opens it in /var/run/pwcheck. The postfix-tls package does not
create these directories and the necessary link. Thi
On Fri, Jan 09, 2004 at 06:15:45AM -0500, Michael B Allen wrote:
|
| > I've just installed postfix-tls but it will not authenticate users with SASL. The
| > error is simply "SASL LOGIN authentication failed" but that's it.
|
| Mmm, if I trace the pwcheck daemon it
> I've just installed postfix-tls but it will not authenticate users with SASL. The
> error is simply "SASL LOGIN authentication failed" but that's it.
Mmm, if I trace the pwcheck daemon it opens a UNIX domain socket
/var/state/pwcheck/pwcheck and waits. When I send
I've just installed postfix-tls but it will not authenticate users with SASL. The
error is simply "SASL LOGIN authentication failed" but that's it. I have verbose
logging on. Is there any way to get more information from the SASL module?
I took a trace and see that postfix is
> Shall the new user be allowed to create databases? (y/n) y
> Shall the new user be allowed to create more new users? (y/n) y
> CREATE USER
> [EMAIL PROTECTED]:$ exit
> exit
> --
>
> Now, as user:
> -----
> $create
create more new users? (y/n) y
CREATE USER
[EMAIL PROTECTED]:$ exit
exit
--
Now, as user:
-
$createdb js
psql: IDENT authentication failed for user 'js'
createdb: database creation failed
js-23:21:12-~$
-
Why
Quoteth Olafur Jens Sigurdsson on Wed, Sep 29, 1999 at 10:31:01PM +:
> On 25. September 1999, Wiz wrote:
> > When i dial to my ISP i get "PAP authentication failed".
> > Whats wrong and how do i fix it?
> >
> > I use pppd, chat and have a dynamic IP-adres
On 25. September 1999, Anthony Campbell wrote:
> On 25 Sep 1999, Joakim Svensson wrote:
> > I have the same problem !
> > Started today. hmmm
> > If you solve it please let me know
> > /Joakim
> >
> >
>
> Have you tried putting "noauth" in /etc/ppp/options.ttySx?
>
> I have to do this to make t
On 25. September 1999, Wiz wrote:
> When i dial to my ISP i get "PAP authentication failed".
> Whats wrong and how do i fix it?
>
> I use pppd, chat and have a dynamic IP-adress.
>
> Sep 25 10:11:23 wizard pppd[136]: Remote message: Password validation failure
>
On 25 Sep 1999, Joakim Svensson wrote:
> I have the same problem !
> Started today. hmmm
> If you solve it please let me know
> /Joakim
>
>
Have you tried putting "noauth" in /etc/ppp/options.ttySx?
I have to do this to make things work.
Anthony
--
Anthony Campbell - running Linux Debian 2.
I have the same problem !
Started today. hmmm
If you solve it please let me know
/Joakim
Wiz writes:
> When i dial to my ISP i get "PAP authentication failed". Whats wrong and
> how do i fix it?
Your ISP requires PAP authentication: that authentication is failing. That
may be because you have configured ppp wrong or because your password is
incorrect. IF you
When i dial to my ISP i get "PAP authentication failed".
Whats wrong and how do i fix it?
I use pppd, chat and have a dynamic IP-adress.
The Log file:
Sep 25 10:11:17 wizard chat[138]: send (ppp^M)
Sep 25 10:11:17 wizard chat[138]: expect (~)
Sep 25 10:11:17 wizard chat[138]: >ppp^M
58 matches
Mail list logo
