Rocksolid Light

Welcome to Rocksolid Light

mail  files  register  newsreader  groups  login

Message-ID:  

A right is not what someone gives you; it's what no one can take from you. -- Ramsey Clark

computers / news.software.readers / Re: [tin] first authorization failed, then pass

SubjectAuthor
* [tin] first authorization failed, then passLucLan
+* Re: [tin] first authorization failed, then passcandycanearter07
|`* Re: [tin] first authorization failed, then passLucLan
| `- Re: [tin] first authorization failed, then passcandycanearter07
+- Re: [tin] first authorization failed, then passUrs Janßen
`* Re: [tin] first authorization failed, then passUrs Janßen
 +- Re: [tin] first authorization failed, then passLucLan
 `- Re: [tin] first authorization failed, then passLucLan

1
[tin] first authorization failed, then pass

<url9fp$3beev$1@dont-email.me>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=2222&group=news.software.readers#2222

  copy link   Newsgroups: news.software.readers
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: address@is.invalid (LucLan)
Newsgroups: news.software.readers
Subject: [tin] first authorization failed, then pass
Date: Tue, 27 Feb 2024 18:26:01 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <url9fp$3beev$1@dont-email.me>
Injection-Date: Tue, 27 Feb 2024 18:26:01 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="9a3e4b7a6ce63b16be7a8f95d3f16801";
logging-data="3520991"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/TKteVSsxZQSspBrC759cI"
Cancel-Lock: sha1:LGVQEyVx/RMEoTzr+6VpubIFu1M=
 by: LucLan - Tue, 27 Feb 2024 18:26 UTC

Hello,

DO anyone know why the first authorization failed, then it pass?

Warning shown:

Authorization failed for user: XXX

My credentials are stored in ~/.newsauth
And I start application with: tin -TAag es

'es' is the shortname from ~/.tin/newsrctable

Thanks.

Re: [tin] first authorization failed, then pass

<urlems$3codj$1@dont-email.me>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=2224&group=news.software.readers#2224

  copy link   Newsgroups: news.software.readers
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: candycanearter07@candycanearter07.nomail.afraid (candycanearter07)
Newsgroups: news.software.readers
Subject: Re: [tin] first authorization failed, then pass
Date: Tue, 27 Feb 2024 19:55:08 -0000 (UTC)
Organization: the-candyden-of-code
Lines: 19
Message-ID: <urlems$3codj$1@dont-email.me>
References: <url9fp$3beev$1@dont-email.me>
Injection-Date: Tue, 27 Feb 2024 19:55:08 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="ae75ddaeb9526e94895bcecb51b3edab";
logging-data="3563955"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19E+DXzLzdHtfbQrIDd5u0yDxGOAMUDumD9aUXtiXvZ/g=="
User-Agent: slrn/pre1.0.4-9 (Linux)
Cancel-Lock: sha1:kIKmEzB3FmqciBz7FVZJfrWz/Yw=
 by: candycanearter07 - Tue, 27 Feb 2024 19:55 UTC

On 2024-02-27, LucLan <address@is.invalid> wrote:
> Hello,
>
> DO anyone know why the first authorization failed, then it pass?
>
> Warning shown:
>
> Authorization failed for user: XXX
>
> My credentials are stored in ~/.newsauth
> And I start application with: tin -TAag es
>
> 'es' is the shortname from ~/.tin/newsrctable
>
> Thanks.

Does it matter too much if it authenticates second try?
--
user <candycane> is generated from /dev/urandom

Re: [tin] first authorization failed, then pass

<urlf2b$1u4$1@nntp.de>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=2225&group=news.software.readers#2225

  copy link   Newsgroups: news.software.readers
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!news.cgarbs.de!nntp.de!.POSTED.akk21-int.akk.kit.edu!not-for-mail
From: urs@buil.tin.org (Urs Janßen)
Newsgroups: news.software.readers
Subject: Re: [tin] first authorization failed, then pass
Date: Tue, 27 Feb 2024 20:01:15 -0000 (UTC)
Organization: tin.org
Archive: no
Message-ID: <urlf2b$1u4$1@nntp.de>
References: <url9fp$3beev$1@dont-email.me>
Injection-Date: Tue, 27 Feb 2024 20:01:15 -0000 (UTC)
Injection-Info: nntp.de; posting-host="akk21-int.akk.kit.edu:2a00:1398:5:f602:cafe:cafe:cafe:21";
logging-data="1988"; mail-complaints-to="abuse@nntp.de"
User-Agent: tin/2.6.4-20240224 ("Banff") (Linux/5.10.0-25-amd64 (x86_64))
Cancel-Lock: sha1:/dqFXHdZMJoV8LEocQgTf3GauJI=
X-No-Archive: yes
X-No-HTML: yes
 by: Urs Janßen - Tue, 27 Feb 2024 20:01 UTC

In <url9fp$3beev$1@dont-email.me> on Tue, 27 Feb 2024 19:26:01,
LucLan wrote:
> Hello,
>
> DO anyone know why the first authorization failed, then it pass?

just a guess; you have space in the auth-data? that will fail with
AUTHINFO PLAIN whihc is tried before AUTHINFO USER e.g.

>>> [19:45:26.872766] AUTHINFO SASL PLAIN AGpvaG4AIGRvZQ==
<<< [19:45:26.879224] 481 generic failure
>>> [19:45:28.881885] AUTHINFO USER john
<<< [19:45:28.888510] 381 Enter password
>>> [19:45:28.888733] AUTHINFO PASS doe
<<< [19:45:28.898705] 281 Authentication succeeded

to check you could add "-vD 1" the the cmd.line opts _after_
reading the "SECURITY" section on the man-page; i.e. you might want to
start tin with $TMPDIR set to a secure location:
TMPDIR=$HOME tin -vD 1 -TAag es

Re: [tin] first authorization failed, then pass

<urlf4i$1u4$2@nntp.de>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=2226&group=news.software.readers#2226

  copy link   Newsgroups: news.software.readers
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!news.cgarbs.de!nntp.de!.POSTED.akk21-int.akk.kit.edu!not-for-mail
From: urs@buil.tin.org (Urs Janßen)
Newsgroups: news.software.readers
Subject: Re: [tin] first authorization failed, then pass
Supersedes: <urlf2b$1u4$1@nntp.de>
Date: Tue, 27 Feb 2024 20:02:26 -0000 (UTC)
Organization: tin.org
Archive: no
Message-ID: <urlf4i$1u4$2@nntp.de>
References: <url9fp$3beev$1@dont-email.me>
Injection-Date: Tue, 27 Feb 2024 20:02:26 -0000 (UTC)
Injection-Info: nntp.de; posting-host="akk21-int.akk.kit.edu:2a00:1398:5:f602:cafe:cafe:cafe:21";
logging-data="1988"; mail-complaints-to="abuse@nntp.de"
User-Agent: tin/2.6.4-20240224 ("Banff") (Linux/5.10.0-25-amd64 (x86_64))
Cancel-Lock: sha1:HgR0S8ejb9ycAdPYM5kQQiJj4Mo=
Cancel-Key: sha1:Jc0lOjM5LOtr2ADm6yxRybxQFHw=
X-No-Archive: yes
X-No-HTML: yes
 by: Urs Janßen - Tue, 27 Feb 2024 20:02 UTC

In <url9fp$3beev$1@dont-email.me> on Tue, 27 Feb 2024 19:26:01,
LucLan wrote:
> Hello,
>
> DO anyone know why the first authorization failed, then it pass?

just a guess; you have space in the auth-data? that will fail with
AUTHINFO PLAIN which is tried before AUTHINFO USER e.g.

>>> [19:45:26.872766] AUTHINFO SASL PLAIN AGpvaG4AIGRvZQ==
<<< [19:45:26.879224] 481 generic failure
>>> [19:45:28.881885] AUTHINFO USER john
<<< [19:45:28.888510] 381 Enter password
>>> [19:45:28.888733] AUTHINFO PASS doe
<<< [19:45:28.898705] 281 Authentication succeeded

to check you could add "-vD 1" the the cmd.line opts _after_
reading the "SECURITY" section of the man-page; i.e. you might want to
start tin with $TMPDIR set to a secure location:
TMPDIR=$HOME tin -vD 1 -TAag es

Re: [tin] first authorization failed, then pass

<urmmqa$3nqfi$1@dont-email.me>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=2234&group=news.software.readers#2234

  copy link   Newsgroups: news.software.readers
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: address@is.invalid (LucLan)
Newsgroups: news.software.readers
Subject: Re: [tin] first authorization failed, then pass
Date: Wed, 28 Feb 2024 07:19:38 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 20
Message-ID: <urmmqa$3nqfi$1@dont-email.me>
References: <url9fp$3beev$1@dont-email.me> <urlems$3codj$1@dont-email.me>
Injection-Date: Wed, 28 Feb 2024 07:19:38 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="9db62bc8ead3f332b91c86eb67f6ae85";
logging-data="3926514"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX191JcxSEbS5bfTlWO4D8/HM"
Cancel-Lock: sha1:un2axS5YGg/mYL1+GuWg3vcI2Pg=
 by: LucLan - Wed, 28 Feb 2024 07:19 UTC

candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:
> On 2024-02-27, LucLan <address@is.invalid> wrote:
>> Hello,
>>
>> DO anyone know why the first authorization failed, then it pass?
>>
>> Warning shown:
>>
>> Authorization failed for user: XXX
>>
>> My credentials are stored in ~/.newsauth
>> And I start application with: tin -TAag es
>>
>> 'es' is the shortname from ~/.tin/newsrctable
>>
>> Thanks.
>
> Does it matter too much if it authenticates second try?

Just a little bit.

Re: [tin] first authorization failed, then pass

<urn730$3s957$1@dont-email.me>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=2235&group=news.software.readers#2235

  copy link   Newsgroups: news.software.readers
Path: i2pn2.org!i2pn.org!usenet.goja.nl.eu.org!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: address@is.invalid (LucLan)
Newsgroups: news.software.readers
Subject: Re: [tin] first authorization failed, then pass
Date: Wed, 28 Feb 2024 11:57:20 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 29
Message-ID: <urn730$3s957$1@dont-email.me>
References: <url9fp$3beev$1@dont-email.me> <urlf4i$1u4$2@nntp.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 28 Feb 2024 11:57:20 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="9db62bc8ead3f332b91c86eb67f6ae85";
logging-data="4072615"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18wYioaUmwKsKWHZQBrmpqy"
Cancel-Lock: sha1:36htcJKuw7SDuB8NMpGNf2JlPU8=
 by: LucLan - Wed, 28 Feb 2024 11:57 UTC

Urs Janßen <urs@buil.tin.org> wrote:
> In <url9fp$3beev$1@dont-email.me> on Tue, 27 Feb 2024 19:26:01,
> LucLan wrote:
>> Hello,
>>
>> DO anyone know why the first authorization failed, then it pass?
>
> just a guess; you have space in the auth-data? that will fail with
> AUTHINFO PLAIN which is tried before AUTHINFO USER e.g.
>
>>>> [19:45:26.872766] AUTHINFO SASL PLAIN AGpvaG4AIGRvZQ==
> <<< [19:45:26.879224] 481 generic failure
>>>> [19:45:28.881885] AUTHINFO USER john
> <<< [19:45:28.888510] 381 Enter password
>>>> [19:45:28.888733] AUTHINFO PASS doe
> <<< [19:45:28.898705] 281 Authentication succeeded
>
> to check you could add "-vD 1" the the cmd.line opts _after_
> reading the "SECURITY" section of the man-page; i.e. you might want to
> start tin with $TMPDIR set to a secure location:
> TMPDIR=$HOME tin -vD 1 -TAag es

Thank you, sir, for your answer.

I tried to start tin with -vD 1, but:
Option not enabled. Recompile with -DDEBUG.
Another bad flag in the AUR package.

Re: [tin] first authorization failed, then pass

<urngli$3u45j$1@dont-email.me>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=2238&group=news.software.readers#2238

  copy link   Newsgroups: news.software.readers
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: address@is.invalid (LucLan)
Newsgroups: news.software.readers
Subject: Re: [tin] first authorization failed, then pass
Date: Wed, 28 Feb 2024 14:40:50 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 32
Message-ID: <urngli$3u45j$1@dont-email.me>
References: <url9fp$3beev$1@dont-email.me> <urlf4i$1u4$2@nntp.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 28 Feb 2024 14:40:50 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="9db62bc8ead3f332b91c86eb67f6ae85";
logging-data="4133043"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19wTYv8M9umMTkIck9qki9S"
Cancel-Lock: sha1:8/67gPkAJ9Vzwy74gdVubCCrbng=
 by: LucLan - Wed, 28 Feb 2024 14:40 UTC

Urs Janßen <urs@buil.tin.org> wrote:
> In <url9fp$3beev$1@dont-email.me> on Tue, 27 Feb 2024 19:26:01,
> LucLan wrote:
>> Hello,
>>
>> DO anyone know why the first authorization failed, then it pass?
>
> just a guess; you have space in the auth-data? that will fail with
> AUTHINFO PLAIN which is tried before AUTHINFO USER e.g.
>
>>>> [19:45:26.872766] AUTHINFO SASL PLAIN AGpvaG4AIGRvZQ==
> <<< [19:45:26.879224] 481 generic failure
>>>> [19:45:28.881885] AUTHINFO USER john
> <<< [19:45:28.888510] 381 Enter password
>>>> [19:45:28.888733] AUTHINFO PASS doe
> <<< [19:45:28.898705] 281 Authentication succeeded
>
> to check you could add "-vD 1" the the cmd.line opts _after_
> reading the "SECURITY" section of the man-page; i.e. you might want to
> start tin with $TMPDIR set to a secure location:
> TMPDIR=$HOME tin -vD 1 -TAag es

you are right:

>>> [14:31:41.360913] AUTHINFO SASL PLAIN xxx
<<< [14:31:41.401144] 481 user not found
>>> [14:31:43.403122] AUTHINFO USER xxx
<<< [14:31:43.445158] 381 Enter password
>>> [14:31:43.445373] AUTHINFO PASS xxx
<<< [14:31:44.065638] 281 Authentication succeeded

Thank again.

Re: [tin] first authorization failed, then pass

<urntq4$12bd$1@dont-email.me>

  copy mid

https://news.novabbs.org/computers/article-flat.php?id=2242&group=news.software.readers#2242

  copy link   Newsgroups: news.software.readers
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: candycanearter07@candycanearter07.nomail.afraid (candycanearter07)
Newsgroups: news.software.readers
Subject: Re: [tin] first authorization failed, then pass
Date: Wed, 28 Feb 2024 18:25:08 -0000 (UTC)
Organization: the-candyden-of-code
Lines: 25
Message-ID: <urntq4$12bd$1@dont-email.me>
References: <url9fp$3beev$1@dont-email.me> <urlems$3codj$1@dont-email.me>
<urmmqa$3nqfi$1@dont-email.me>
Injection-Date: Wed, 28 Feb 2024 18:25:08 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="bcc2938c91bfdb63ab6b677b3a9adc0f";
logging-data="35181"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18Uex3sPvsH6vazT1MmcjxENXUVUk5S3su7xBVvligI1A=="
User-Agent: slrn/pre1.0.4-9 (Linux)
Cancel-Lock: sha1:pz037CrS5N4Uvw0BGmERMOUricU=
 by: candycanearter07 - Wed, 28 Feb 2024 18:25 UTC

LucLan <address@is.invalid> wrote at 07:19 this Wednesday (GMT):
> candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:
>> On 2024-02-27, LucLan <address@is.invalid> wrote:
>>> Hello,
>>>
>>> DO anyone know why the first authorization failed, then it pass?
>>>
>>> Warning shown:
>>>
>>> Authorization failed for user: XXX
>>>
>>> My credentials are stored in ~/.newsauth
>>> And I start application with: tin -TAag es
>>>
>>> 'es' is the shortname from ~/.tin/newsrctable
>>>
>>> Thanks.
>>
>> Does it matter too much if it authenticates second try?
>
> Just a little bit.

fair
--
user <candycane> is generated from /dev/urandom

1
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor