Hello,
DO anyone know why the first authorization failed, then it pass?
<<< [19:45:26.879224] 481 generic failure[19:45:26.872766] AUTHINFO SASL PLAIN AGpvaG4AIGRvZQ==
<<< [19:45:28.888510] 381 Enter password[19:45:28.881885] AUTHINFO USER john
<<< [19:45:28.898705] 281 Authentication succeeded[19:45:28.888733] AUTHINFO PASS doe
Hello,
DO anyone know why the first authorization failed, then it pass?
<<< [19:45:26.879224] 481 generic failure[19:45:26.872766] AUTHINFO SASL PLAIN AGpvaG4AIGRvZQ==
<<< [19:45:28.888510] 381 Enter password[19:45:28.881885] AUTHINFO USER john
<<< [19:45:28.898705] 281 Authentication succeeded[19:45:28.888733] AUTHINFO PASS doe
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.
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?
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.879224] 481 generic failure[19:45:26.872766] AUTHINFO SASL PLAIN AGpvaG4AIGRvZQ==
<<< [19:45:28.888510] 381 Enter password[19:45:28.881885] AUTHINFO USER john
<<< [19:45:28.898705] 281 Authentication succeeded[19:45:28.888733] AUTHINFO PASS doe
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
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.879224] 481 generic failure[19:45:26.872766] AUTHINFO SASL PLAIN AGpvaG4AIGRvZQ==
<<< [19:45:28.888510] 381 Enter password[19:45:28.881885] AUTHINFO USER john
<<< [19:45:28.898705] 281 Authentication succeeded[19:45:28.888733] AUTHINFO PASS doe
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
<<< [14:31:41.401144] 481 user not found[14:31:41.360913] AUTHINFO SASL PLAIN xxx
<<< [14:31:43.445158] 381 Enter password[14:31:43.403122] AUTHINFO USER xxx
<<< [14:31:44.065638] 281 Authentication succeeded[14:31:43.445373] AUTHINFO PASS xxx
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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 481 |
Nodes: | 16 (2 / 14) |
Uptime: | 19:36:53 |
Calls: | 9,542 |
Calls today: | 2 |
Files: | 13,653 |
Messages: | 6,140,029 |