Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

All Finagle Laws may be bypassed by learning the simple art of doing without thinking.


computers / alt.os.linux.slackware / Re: Oauth 2.0

SubjectAuthor
* Oauth 2.0root
+* Re: Oauth 2.0Ben Collver
|`* Re: Oauth 2.0root
| `- Re: Oauth 2.0root
`* Re: Oauth 2.0#Paul
 `* Re: Oauth 2.0root
  `* Re: Oauth 2.0Henrik Carlqvist
   `* Re: Oauth 2.0root
    `* Re: Oauth 2.0Giovanni
     `* Re: Oauth 2.0Ralph Spitzner
      `* Re: Oauth 2.0Giovanni
       +- Re: Oauth 2.0Ralph Spitzner
       `* Re: Oauth 2.0Chris Vine
        `* Re: Oauth 2.0Chris Vine
         `- Re: Oauth 2.0Henrik Carlqvist

1
Oauth 2.0

<t4piio$ahf$1@dont-email.me>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1168&group=alt.os.linux.slackware#1168

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: NoEMail@home.org (root)
Newsgroups: alt.os.linux.slackware
Subject: Oauth 2.0
Date: Mon, 2 May 2022 21:31:05 -0000 (UTC)
Organization: Linux Advocacy
Lines: 6
Message-ID: <t4piio$ahf$1@dont-email.me>
Injection-Date: Mon, 2 May 2022 21:31:05 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="8a961801433ccdde24df7e59bb400921";
logging-data="10799"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19xQYCuraACq8rDYZmOBteuO18fAoD829g="
User-Agent: slrn/1.0.2 (Linux)
Cancel-Lock: sha1:0R+gZuj79XqLEyF+pSPkniz7HWw=
Mail-Copies-To: nobody
 by: root - Mon, 2 May 2022 21:31 UTC

I saw a reference to 7.x version of Fetchmail from GitHub, but now
I can't find it. I am pretty sure the Slackware packages for
fetchmail do not support the new authorization method. Is it
likely that a Slackware package will appear before the new OAuth
takes effect?

Re: Oauth 2.0

<slrnt70l62.2sv.bencollver@svadhyaya.localdomain>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1169&group=alt.os.linux.slackware#1169

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!news.niel.me!news.gegeweb.eu!gegeweb.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: bencollver@tilde.pink (Ben Collver)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Mon, 2 May 2022 22:01:52 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 9
Message-ID: <slrnt70l62.2sv.bencollver@svadhyaya.localdomain>
References: <t4piio$ahf$1@dont-email.me>
Injection-Date: Mon, 2 May 2022 22:01:52 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="3267dba077cac67420814d3bf17da5d8";
logging-data="27550"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/93kOhCGAJQ29EKkdK44AZW04vGeBcp0I="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:bCDPVHBljiZGnCRnFXAM6L/cGPA=
 by: Ben Collver - Mon, 2 May 2022 22:01 UTC

On 2022-05-02, root <NoEMail@home.org> wrote:
> I saw a reference to 7.x version of Fetchmail from GitHub, but now
> I can't find it. I am pretty sure the Slackware packages for
> fetchmail do not support the new authorization method. Is it
> likely that a Slackware package will appear before the new OAuth
> takes effect?

I don't know the answer to your question, but in case you need other
options, Slackware's getmail package supports OAuth 2.0

Re: Oauth 2.0

<7b57kixane.ln2@threeformcow.myzen.co.uk>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1171&group=alt.os.linux.slackware#1171

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!aioe.org!3GRggUvGWc6WgWU3JZzeYg.user.46.165.242.75.POSTED!not-for-mail
From: news20k.noreply@threeformcow.myzen.co.uk (#Paul)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Tue, 03 May 2022 09:22:31 +0100
Organization: Aioe.org NNTP Server
Message-ID: <7b57kixane.ln2@threeformcow.myzen.co.uk>
References: <t4piio$ahf$1@dont-email.me>
Injection-Info: gioia.aioe.org; logging-data="55163"; posting-host="3GRggUvGWc6WgWU3JZzeYg.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
User-Agent: tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.27 (x86_64))
X-Notice: Filtered by postfilter v. 0.9.2
 by: #Paul - Tue, 3 May 2022 08:22 UTC

root <NoEMail@home.org> wrote:
> I saw a reference to 7.x version of Fetchmail from GitHub, but now
> I can't find it. I am pretty sure the Slackware packages for
> fetchmail do not support the new authorization method. Is it
> likely that a Slackware package will appear before the new OAuth
> takes effect?

FWIW, there's been some discussion of OAuth &etc on the fetchmail
mailing list recently.

#Paul

Re: Oauth 2.0

<t4rjk4$l3q$1@dont-email.me>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1173&group=alt.os.linux.slackware#1173

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: NoEMail@home.org (root)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Tue, 3 May 2022 16:01:08 -0000 (UTC)
Organization: Linux Advocacy
Lines: 5
Message-ID: <t4rjk4$l3q$1@dont-email.me>
References: <t4piio$ahf$1@dont-email.me>
<slrnt70l62.2sv.bencollver@svadhyaya.localdomain>
Injection-Date: Tue, 3 May 2022 16:01:08 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="208078db316677374d63bac93ff2e7c2";
logging-data="21626"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18KzZV3njPjS43Tf5au3a0DVVxEqjzZR8Q="
User-Agent: slrn/1.0.2 (Linux)
Cancel-Lock: sha1:z7WaN+B7Zz6N1YlG0/gPmsr2nYA=
 by: root - Tue, 3 May 2022 16:01 UTC

>
> I don't know the answer to your question, but in case you need other
> options, Slackware's getmail package supports OAuth 2.0

Thanks, I will look into getmail.

Re: Oauth 2.0

<t4rmoj$hn6$1@dont-email.me>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1174&group=alt.os.linux.slackware#1174

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: NoEMail@home.org (root)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Tue, 3 May 2022 16:54:43 -0000 (UTC)
Organization: Linux Advocacy
Lines: 41
Message-ID: <t4rmoj$hn6$1@dont-email.me>
References: <t4piio$ahf$1@dont-email.me>
<slrnt70l62.2sv.bencollver@svadhyaya.localdomain>
<t4rjk4$l3q$1@dont-email.me>
Injection-Date: Tue, 3 May 2022 16:54:43 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="208078db316677374d63bac93ff2e7c2";
logging-data="18150"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+VbulTMo2l3ov/1dCJpo4H8Yn+Ip22NfI="
User-Agent: slrn/1.0.2 (Linux)
Cancel-Lock: sha1:B6vMN/SL8JsBgCD6mLdxUTlUv1o=
 by: root - Tue, 3 May 2022 16:54 UTC

root <NoEMail@home.org> wrote:
>>
>> I don't know the answer to your question, but in case you need other
>> options, Slackware's getmail package supports OAuth 2.0
>
> Thanks, I will look into getmail.

getmail doesn't seem to work for me. I think I remember that
I switched to fetchmail some time ago because getmail stopped
working.

This is the .getmailrc file I am using:

[retriever]
type = SimplePOP3Retriever
server = pop.gmail.com
username = MYNAME
password = MYPASS
port = 995
[destination]
type = Maildir
#type = Mboxrd
path = /var/spool/mail/root
#[other-destination-1]
#type = Mboxrd
#path = /var/spool/mail/root
#user = root
[filter-3]
type = Filter_external
path = /root/bin/mailfilter
allow_root_commands = 1
ignore_stderr=true
##arguments = ('--message-from-stdin', '--remove-all-but-attachment-types=text/plain,text/rfc822')
#user = root

I had been using Mboxrd. I switched to Maildir and had to create
a number of directories before getmail would run. It still reports
no mail even though I know mail is waiting for me.

Please help, I haven't done anything with mail in over a decade.

Re: Oauth 2.0

<t4rt35$c3t$1@dont-email.me>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1175&group=alt.os.linux.slackware#1175

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: NoEMail@home.org (root)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Tue, 3 May 2022 18:42:46 -0000 (UTC)
Organization: Linux Advocacy
Lines: 26
Message-ID: <t4rt35$c3t$1@dont-email.me>
References: <t4piio$ahf$1@dont-email.me>
<7b57kixane.ln2@threeformcow.myzen.co.uk>
Injection-Date: Tue, 3 May 2022 18:42:46 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="208078db316677374d63bac93ff2e7c2";
logging-data="12413"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18SABUisBLgeChWg/sFW4POrWWtvz0TilE="
User-Agent: slrn/1.0.2 (Linux)
Cancel-Lock: sha1:x6oOuf4ozB8mKTnWeBrXvKjNaIY=
 by: root - Tue, 3 May 2022 18:42 UTC

#Paul <news20k.noreply@threeformcow.myzen.co.uk> wrote:
> root <NoEMail@home.org> wrote:
>> I saw a reference to 7.x version of Fetchmail from GitHub, but now
>> I can't find it. I am pretty sure the Slackware packages for
>> fetchmail do not support the new authorization method. Is it
>> likely that a Slackware package will appear before the new OAuth
>> takes effect?
>
> FWIW, there's been some discussion of OAuth &etc on the fetchmail
> mailing list recently.
>
> #Paul

There is a new version of fetchmail:
fetchmail-git-156d9cf5813241706bc7cffb17aaaae3a3fa8226.zip

but it will not make because:

configure: error: Your SSL library is too old and does not support TLS v1.3. Upgrade.

So I tried updating and upgrading all my packages for 14.2 and
I still do not get the required TLS version.

For now I am dead in the water.

Re: Oauth 2.0

<t4t2oi$5n7$1@dont-email.me>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1179&group=alt.os.linux.slackware#1179

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Henrik.Carlqvist@deadspam.com (Henrik Carlqvist)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Wed, 4 May 2022 05:25:38 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <t4t2oi$5n7$1@dont-email.me>
References: <t4piio$ahf$1@dont-email.me>
<7b57kixane.ln2@threeformcow.myzen.co.uk> <t4rt35$c3t$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 4 May 2022 05:25:38 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="4e1fcd685b9f1caedbcdf23f8181d721";
logging-data="5863"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/to28pLG2xXFUghNxJHIq9"
User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508
git://git.gnome.org/pan2)
Cancel-Lock: sha1:QNS844vw4pQfwI0W4kHyjinr1u4=
 by: Henrik Carlqvist - Wed, 4 May 2022 05:25 UTC

On Tue, 03 May 2022 18:42:46 +0000, root wrote:
> So I tried updating and upgrading all my packages for 14.2 and I still
> do not get the required TLS version.
>
> For now I am dead in the water.

Even though Slackware 14.2 with its age of almost 6 years is still being
maintained, it only gives security updates to packages where the upstream
providers gives releases which still works with Slackware 14.2. A number
of packages like mozilla-firefox no longer comes with updates for 14.2.

A few weeks ago there was a security update for 14.2 were version 1.0.2u
of openssl was rebuilt. At the same time 15.0 was upgraded to version
1.1.1n. Since version 1.1.1 openssl is supposed to have support for TLS
v1.3.

Version 1.0.2 of openssl is now EOL and maybe there is some reason that
14.2 sticks to that version. If you are lucky you might be able to
compile some 1.1.1 version yourself and get it working on 14.2.
Otherwise, if you really need TLS v1.3, you might need to upgrade your
Slackware installation to 15.0.

m v h Henrik

Re: Oauth 2.0

<t4tdgf$fug$1@dont-email.me>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1180&group=alt.os.linux.slackware#1180

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: NoEMail@home.org (root)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Wed, 4 May 2022 08:29:03 -0000 (UTC)
Organization: Linux Advocacy
Lines: 21
Message-ID: <t4tdgf$fug$1@dont-email.me>
References: <t4piio$ahf$1@dont-email.me>
<7b57kixane.ln2@threeformcow.myzen.co.uk> <t4rt35$c3t$1@dont-email.me>
<t4t2oi$5n7$1@dont-email.me>
Injection-Date: Wed, 4 May 2022 08:29:03 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="a6cf0b676d43915bc11023879be8e924";
logging-data="16336"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+dHVdtdQBmvG44vK5UesGthJl3P6sZRjg="
User-Agent: slrn/1.0.2 (Linux)
Cancel-Lock: sha1:QF9V6pEkrQyhQbHNfdhLev1Vx0M=
 by: root - Wed, 4 May 2022 08:29 UTC

Henrik Carlqvist <Henrik.Carlqvist@deadspam.com> wrote:
> Even though Slackware 14.2 with its age of almost 6 years is still being
> maintained, it only gives security updates to packages where the upstream
> providers gives releases which still works with Slackware 14.2. A number
> of packages like mozilla-firefox no longer comes with updates for 14.2.
>
> A few weeks ago there was a security update for 14.2 were version 1.0.2u
> of openssl was rebuilt. At the same time 15.0 was upgraded to version
> 1.1.1n. Since version 1.1.1 openssl is supposed to have support for TLS
> v1.3.
>
> Version 1.0.2 of openssl is now EOL and maybe there is some reason that
> 14.2 sticks to that version. If you are lucky you might be able to
> compile some 1.1.1 version yourself and get it working on 14.2.
> Otherwise, if you really need TLS v1.3, you might need to upgrade your
> Slackware installation to 15.0.
>
> m v h Henrik

Thanks for responding Henrik. I came to the same conclusion and
am now trying out 15.0.

Re: Oauth 2.0

<t50ac9$rje$1@milena.home.net.it>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1181&group=alt.os.linux.slackware#1181

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!usenet.goja.nl.eu.org!2.eu.feeder.erje.net!feeder.erje.net!news.uzoreto.com!dotsrc.org!filter.dotsrc.org!news.dotsrc.org!not-for-mail
From: lsodgf0@home.net.it (Giovanni)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Thu, 5 May 2022 12:54:01 +0200
Organization: G. Falzoni Home Network
Message-ID: <t50ac9$rje$1@milena.home.net.it>
References: <t4piio$ahf$1@dont-email.me>
<7b57kixane.ln2@threeformcow.myzen.co.uk> <t4rt35$c3t$1@dont-email.me>
<t4t2oi$5n7$1@dont-email.me> <t4tdgf$fug$1@dont-email.me>
Reply-To: gfalzoni@inwind.it
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 20
NNTP-Posting-Host: 0b537a3e.news.sunsite.dk
X-Trace: 1651748044 news.sunsite.dk 700 gfalzoni@inwind.it/151.20.187.249:57634
X-Complaints-To: staff@sunsite.dk
 by: Giovanni - Thu, 5 May 2022 10:54 UTC

On 5/4/22 10:29, root wrote:
> Thanks for responding Henrik. I came to the same conclusion and
> am now trying out 15.0.

Last week I started working on porting openssl-1.1.1n from 15.0 to 14.2
to get TLS 1.3 on 14.2

Using slackbuild from 15.0 the package compiles correctly but I haven't
yet installed and tested.

As soon as I'll have some spare time I'll will try to load it in my test
installation on virtualbox. I'm still confused on how to install the
new package. Any suggestion welcomed.

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
< http://giovanni.homelinux.net/ >

Re: Oauth 2.0

<t50ddj$ast$1@dont-email.me>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1182&group=alt.os.linux.slackware#1182

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!news.niel.me!news.gegeweb.eu!gegeweb.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: rasp@spitzner.org (Ralph Spitzner)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Thu, 5 May 2022 13:46:06 +0200
Organization: A noiseless patient Spider
Lines: 11
Message-ID: <t50ddj$ast$1@dont-email.me>
References: <t4piio$ahf$1@dont-email.me>
<7b57kixane.ln2@threeformcow.myzen.co.uk> <t4rt35$c3t$1@dont-email.me>
<t4t2oi$5n7$1@dont-email.me> <t4tdgf$fug$1@dont-email.me>
<t50ac9$rje$1@milena.home.net.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 5 May 2022 11:45:55 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="f60d90295ec2b11574ebb0c620a2fbd5";
logging-data="11165"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/6rEFCNjCW5TU/3nFdVlf8rdTkWZr48MQ="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Firefox/68.0 SeaMonkey/2.53.11.1
Cancel-Lock: sha1:WEvedtPb81WtiBOgJtDIo9beYyw=
In-Reply-To: <t50ac9$rje$1@milena.home.net.it>
 by: Ralph Spitzner - Thu, 5 May 2022 11:46 UTC

Giovanni wrote on 5/5/22 12:54 PM:

> Using slackbuild from 15.0 the package compiles correctly but I haven't yet installed and tested.
>
> As soon as I'll have some spare time I'll will try to load it in my test installation on virtualbox.  I'm still confused on how to install the new package.  Any suggestion welcomed.

just try upgradepkg ?

-rasp

Re: Oauth 2.0

<t50koq$98j$1@milena.home.net.it>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1183&group=alt.os.linux.slackware#1183

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!aioe.org!news.uzoreto.com!dotsrc.org!filter.dotsrc.org!news.dotsrc.org!not-for-mail
From: lsodgf0@home.net.it (Giovanni)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Thu, 5 May 2022 15:51:22 +0200
Organization: G. Falzoni Home Network
Message-ID: <t50koq$98j$1@milena.home.net.it>
References: <t4piio$ahf$1@dont-email.me>
<7b57kixane.ln2@threeformcow.myzen.co.uk> <t4rt35$c3t$1@dont-email.me>
<t4t2oi$5n7$1@dont-email.me> <t4tdgf$fug$1@dont-email.me>
<t50ac9$rje$1@milena.home.net.it> <t50ddj$ast$1@dont-email.me>
Reply-To: gfalzoni@inwind.it
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 29
NNTP-Posting-Host: ce2b864c.news.sunsite.dk
X-Trace: 1651758685 news.sunsite.dk 706 gfalzoni@inwind.it/151.20.187.249:58692
X-Complaints-To: staff@sunsite.dk
 by: Giovanni - Thu, 5 May 2022 13:51 UTC

On 5/5/22 13:46, Ralph Spitzner wrote:
> Giovanni wrote on 5/5/22 12:54 PM:
>
>> Using slackbuild from 15.0 the package compiles correctly but I
>> haven't yet installed and tested.
>>
>> As soon as I'll have some spare time I'll will try to load it in my
>> test installation on virtualbox.  I'm still confused on how to install
>> the new package.  Any suggestion welcomed.
>
> just try upgradepkg ?
>
>
>     -rasp
>

Not a good idea, unless you relink every program using old libraries.
I need TLS 1.3 mainly for fetchmail that I upgraded to 6.4.27 but
compiled with openssl 1.0.2 and now I'd like to upgrade also openssl.

I need to understand if new and old version of openssl can be installed
at the same time.

Ciao
Giovanni
--
A computer is like an air conditioner,
it stops working when you open Windows.
< http://giovanni.homelinux.net/ >

Re: Oauth 2.0

<t50q2p$n96$1@dont-email.me>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1184&group=alt.os.linux.slackware#1184

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: rasp@spitzner.org (Ralph Spitzner)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Thu, 5 May 2022 17:22:11 +0200
Organization: A noiseless patient Spider
Lines: 18
Message-ID: <t50q2p$n96$1@dont-email.me>
References: <t4piio$ahf$1@dont-email.me>
<7b57kixane.ln2@threeformcow.myzen.co.uk> <t4rt35$c3t$1@dont-email.me>
<t4t2oi$5n7$1@dont-email.me> <t4tdgf$fug$1@dont-email.me>
<t50ac9$rje$1@milena.home.net.it> <t50ddj$ast$1@dont-email.me>
<t50koq$98j$1@milena.home.net.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 5 May 2022 15:22:01 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="f60d90295ec2b11574ebb0c620a2fbd5";
logging-data="23846"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19rX1E601xWbg5ZWZOXi6lz+YI+6d1FQjQ="
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
Firefox/68.0 SeaMonkey/2.53.12
Cancel-Lock: sha1:7n2JlYxc4VZs4TaVV7RPGALkkPY=
In-Reply-To: <t50koq$98j$1@milena.home.net.it>
 by: Ralph Spitzner - Thu, 5 May 2022 15:22 UTC

Giovanni wrote on 5/5/22 3:51 PM:

> Not a good idea, unless you relink every program using old libraries.
> I need TLS 1.3 mainly for fetchmail that I upgraded to 6.4.27 but compiled with openssl 1.0.2 and now I'd like to upgrade also openssl.
>
> I need to understand if new and old version of openssl can be installed at the same time.
>
> Ciao
> Giovanni

unless they've changed the api, old call should still be there, Ionly had problems the other way around..
(newer programs, older libraries)
of course there are programs which want to open a lisomething.x.y.so explicityly
so for testing you could just copy over the new .so's alongside the old ones, run ldconfig and see what program picks up which....
just a thaught...

-rasp

Re: Oauth 2.0

<20220505195737.e4b347f7f1c4c91310edcddc@cvine--nospam--.freeserve.co.uk>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1185&group=alt.os.linux.slackware#1185

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!aioe.org!RdTm+m5ipZMOEay9p1UdJw.user.46.165.242.75.POSTED!not-for-mail
From: chris@cvine--nospam--.freeserve.co.uk (Chris Vine)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Thu, 5 May 2022 19:57:37 +0100
Organization: Aioe.org NNTP Server
Message-ID: <20220505195737.e4b347f7f1c4c91310edcddc@cvine--nospam--.freeserve.co.uk>
References: <t4piio$ahf$1@dont-email.me>
<7b57kixane.ln2@threeformcow.myzen.co.uk>
<t4rt35$c3t$1@dont-email.me>
<t4t2oi$5n7$1@dont-email.me>
<t4tdgf$fug$1@dont-email.me>
<t50ac9$rje$1@milena.home.net.it>
<t50ddj$ast$1@dont-email.me>
<t50koq$98j$1@milena.home.net.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Injection-Info: gioia.aioe.org; logging-data="30279"; posting-host="RdTm+m5ipZMOEay9p1UdJw.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
X-Notice: Filtered by postfilter v. 0.9.2
X-Newsreader: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-unknown-linux-gnu)
 by: Chris Vine - Thu, 5 May 2022 18:57 UTC

On Thu, 5 May 2022 15:51:22 +0200
Giovanni <lsodgf0@home.net.it> wrote:
> On 5/5/22 13:46, Ralph Spitzner wrote:
> > Giovanni wrote on 5/5/22 12:54 PM:
> >
> >> Using slackbuild from 15.0 the package compiles correctly but I
> >> haven't yet installed and tested.
> >>
> >> As soon as I'll have some spare time I'll will try to load it in my
> >> test installation on virtualbox.  I'm still confused on how to install
> >> the new package.  Any suggestion welcomed.
> >
> > just try upgradepkg ?
> >
> >
> >     -rasp
> >
>
> Not a good idea, unless you relink every program using old libraries.
> I need TLS 1.3 mainly for fetchmail that I upgraded to 6.4.27 but
> compiled with openssl 1.0.2 and now I'd like to upgrade also openssl.
>
> I need to understand if new and old version of openssl can be installed
> at the same time.

Some libraries do allow multiple versions of the same library to be
installed and linked to concurrently, as they mangle function names to
include the version number in the function name (icu4c is an example
of this), but most do not.

The problem you have is that if you have a binary which links directly
or (by virtue of linking with other libraries) indirectly to two
versions of a particular library such as openssl which reuses the same
function names, it is a matter of luck as to which function version the
linker in fact links up with. The result is that your binary is likely
to crash from time to time in puzzling ways.

I have no idea what the position is with openssl, but assuming it does
not mangle names you will need to ensure that no library that your
home-compiled fetchmail links with attempts to link with a different
version of openssl than openssl-1.1.

Re: Oauth 2.0

<20220505201959.e392f5ce073a2757ede9fd8b@cvine--nospam--.freeserve.co.uk>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1186&group=alt.os.linux.slackware#1186

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!aioe.org!RdTm+m5ipZMOEay9p1UdJw.user.46.165.242.75.POSTED!not-for-mail
From: chris@cvine--nospam--.freeserve.co.uk (Chris Vine)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Thu, 5 May 2022 20:19:59 +0100
Organization: Aioe.org NNTP Server
Message-ID: <20220505201959.e392f5ce073a2757ede9fd8b@cvine--nospam--.freeserve.co.uk>
References: <t4piio$ahf$1@dont-email.me>
<7b57kixane.ln2@threeformcow.myzen.co.uk>
<t4rt35$c3t$1@dont-email.me>
<t4t2oi$5n7$1@dont-email.me>
<t4tdgf$fug$1@dont-email.me>
<t50ac9$rje$1@milena.home.net.it>
<t50ddj$ast$1@dont-email.me>
<t50koq$98j$1@milena.home.net.it>
<20220505195737.e4b347f7f1c4c91310edcddc@cvine--nospam--.freeserve.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Info: gioia.aioe.org; logging-data="50010"; posting-host="RdTm+m5ipZMOEay9p1UdJw.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org";
X-Notice: Filtered by postfilter v. 0.9.2
X-Newsreader: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-unknown-linux-gnu)
 by: Chris Vine - Thu, 5 May 2022 19:19 UTC

On Thu, 5 May 2022 19:57:37 +0100
Chris Vine <chris@cvine--nospam--.freeserve.co.uk> wrote:
> On Thu, 5 May 2022 15:51:22 +0200
> Giovanni <lsodgf0@home.net.it> wrote:
> > I need to understand if new and old version of openssl can be installed
> > at the same time.
>
> Some libraries do allow multiple versions of the same library to bef
> installed and linked to concurrently, as they mangle function names toe
> include the version number in the function name (icu4c is an example
> of this), but most do not.
>
> The problem you have is that if you have a binary which links directly
> or (by virtue of linking with other libraries) indirectly to two
> versions of a particular library such as openssl which reuses the same
> function names, it is a matter of luck as to which function version the
> linker in fact links up with. The result is that your binary is likely
> to crash from time to time in puzzling ways.
>
> I have no idea what the position is with openssl, but assuming it does
> not mangle names you will need to ensure that no library that your
> home-compiled fetchmail links with attempts to link with a different
> version of openssl than openssl-1.1.

By the way, the above answers the question you asked.

But there is a further point about how you compile fetchmail against
openssl-1.1 when you want to retain openssl-1.0 as your "system"
version. Probably the best way is to install openssl-1.1 in a
different prefix such as /opt/openssl-1.1, and when compiling fetchmail
set PKG_CONFIG_PATH to first look in /opt/openssl-1.1/lib64/pkgconfig
and set LD_LIBRARY_PATH to /opt/openssl-4.1/lib64. When running
fetchmail you would also need to set LD_LIBRARY_PATH, say by starting
fetchmail via a shell script.

Re: Oauth 2.0

<t52c9a$qod$1@dont-email.me>

 copy mid

https://www.rocksolidbbs.com/computers/article-flat.php?id=1187&group=alt.os.linux.slackware#1187

 copy link   Newsgroups: alt.os.linux.slackware
Path: i2pn2.org!i2pn.org!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Henrik.Carlqvist@deadspam.com (Henrik Carlqvist)
Newsgroups: alt.os.linux.slackware
Subject: Re: Oauth 2.0
Date: Fri, 6 May 2022 05:38:50 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 39
Message-ID: <t52c9a$qod$1@dont-email.me>
References: <t4piio$ahf$1@dont-email.me>
<7b57kixane.ln2@threeformcow.myzen.co.uk> <t4rt35$c3t$1@dont-email.me>
<t4t2oi$5n7$1@dont-email.me> <t4tdgf$fug$1@dont-email.me>
<t50ac9$rje$1@milena.home.net.it> <t50ddj$ast$1@dont-email.me>
<t50koq$98j$1@milena.home.net.it>
<20220505195737.e4b347f7f1c4c91310edcddc@cvine--nospam--.freeserve.co.uk>
<20220505201959.e392f5ce073a2757ede9fd8b@cvine--nospam--.freeserve.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 6 May 2022 05:38:50 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="0de8516076e8f01ba9cc0975db2081d7";
logging-data="27405"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18QcQ/oSLp6W7U8wpHVqwbl"
User-Agent: Pan/0.139 (Sexual Chocolate; GIT bf56508
git://git.gnome.org/pan2)
Cancel-Lock: sha1:UxT8cjmfYjZSIAbscuwqDz/P9NA=
 by: Henrik Carlqvist - Fri, 6 May 2022 05:38 UTC

On Thu, 05 May 2022 20:19:59 +0100, Chris Vine wrote:
> Probably the best way is to install openssl-1.1 in a different
> prefix such as /opt/openssl-1.1, and when compiling fetchmail set
> PKG_CONFIG_PATH to first look in /opt/openssl-1.1/lib64/pkgconfig and
> set LD_LIBRARY_PATH to /opt/openssl-4.1/lib64. When running fetchmail
> you would also need to set LD_LIBRARY_PATH, say by starting fetchmail
> via a shell script.

Yes, that will probably be neccessary, on Slackware 14.2
"ldd /usr/bin/fetchmail" shows:

linux-vdso.so.1 (0x00007ffe78bc2000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f98e49ac000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f98e4791000)
libssl.so.1 => /lib64/libssl.so.1 (0x00007f98e451d000)
libcrypto.so.1 => /lib64/libcrypto.so.1 (0x00007f98e40c5000)
libc.so.6 => /lib64/libc.so.6 (0x00007f98e3cfc000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f98e3af7000)
/lib64/ld-linux-x86-64.so.2 (0x0000557b6be1a000)

So fetchmail is dynamically linked to /lib64/libssl.so.1 which is a
symbolic link to libssl.so.1.0.0 which comes from the openssl-1.0.2u
(which by the way was updated again just some day ago)

If you are lucky, fetchmail and other applications will work better out-
of-the box with the new 1.1 versions of the dynamic libraries from
openssl-1.1, but maybe something will break. If so, there is no better
suggestion than to install then newer version of openssl in another
prefix and recompile selected applications against the newer version.
Maybe you want to statically link those recompiled applications to avoid
the need to set LD_LIBRARY_PATH before running the recompiled
applications.

You will not be able to have both versions of openssl installed next to
each other in their ordinary directory structure as they probably both
want to use the symbolic link libssl.so.1 and they probably both want to
use the same header files in /usr/include/openssl.

regards Henrik

1
server_pubkey.txt

rocksolid light 0.9.7
clearnet tor