On Sat 19 Apr 2025 at 11:40:52 (-0400), Greg Wooledge wrote:
> On Sat, Apr 19, 2025 at 08:12:02 -0700, pe...@easthope.ca wrote:
> > In https://wiki.debian.org/DotFiles the sixth paragraph states, "You
> > should therefore always have command source ~/.bashrc at the end of
&g
From: George at Clug
Date: Sun, 20 Apr 2025 23:55:22 +1000
> Please excuse my ignorance, but how did you manage to get the folder
> "/home/root/" when running "ls ~/.bash_profile" as root?
>
> To my knowledge root's home directory should be
From: Greg Wooledge
Date: Sat, 19 Apr 2025 11:40:52 -0400
> Just FYI, that page is essentially an older version of
> <https://mywiki.wooledge.org/DotFiles>.
Thanks. A much better document. Jonathan added a link to it.
https://wiki.debian.org/DotFiles
> If you wan
people get the best content
without duplication of effort.
If anyone has opinions on that course of action, the discussion page is
the place to share them: <https://wiki.debian.org/DotFiles/Discussion>.
I won't delete the page if there's unresolved objections, and I'll wait
On Sun 20 Apr 2025 at 23:55:22 (+1000), George at Clug wrote:
> On Sunday, 20-04-2025 at 01:12 pe...@easthope.ca wrote:
> > Debian 12 here, obtained by upgrading Debian 11.
> >
> > In https://wiki.debian.org/DotFiles the sixth paragraph states, "You
> > shou
On 20/04/2025 10:37, Greg Wooledge wrote:
On Sun, Apr 20, 2025 at 10:32:37 +0700, Max Nikulin wrote:
P.S. DotFiles does not mention that PATH may be set through /etc/login.defs.
I don't think this is true; it changed in Debian 10 when the shadow-utils
suite was dropped in favor of util-linux.
On Sunday, 20-04-2025 at 01:12 pe...@easthope.ca wrote:
> Hi,
>
> Debian 12 here, obtained by upgrading Debian 11.
>
> In https://wiki.debian.org/DotFiles the sixth paragraph states, "You
> should therefore always have command source ~/.bashrc at the end of
> your
On Sun, Apr 20, 2025 at 10:32:37 +0700, Max Nikulin wrote:
> P.S. DotFiles does not mention that PATH may be set through /etc/login.defs.
I don't think this is true; it changed in Debian 10 when the shadow-utils
suite was dropped in favor of util-linux.
hobbit:~$ man login.defs
[...]
BUGS
On 19/04/2025 22:12, peter wrote:
In https://wiki.debian.org/DotFiles the sixth paragraph states, "You
should therefore always have command source ~/.bashrc at the end of
your .bash_profile in order to force it to be read by a login shell."
# ls ~/.bash_profile
ls: cannot access &
On Sat, Apr 19, 2025 at 18:34:07 +0100, Jonathan Dowland wrote:
> Aside, with my "concerned about content licensing hat on"; and I note the
> paragraph on your wiki's front page. You are the principal but not sole
> author of the page on your site, I see; do you have a view on what license
> you co
My advice to OP would be: first of all, before considering improving the
page, is it worth keeping? Does it offer value? Second, I encourage you
to discuss suggestions on a wiki Discussion page. I've added a link for
one to the DotFiles page, it points here:
https://wiki.debian.org/Dot
On Sat, Apr 19, 2025 at 08:12:02 -0700, pe...@easthope.ca wrote:
> In https://wiki.debian.org/DotFiles the sixth paragraph states, "You
> should therefore always have command source ~/.bashrc at the end of
> your .bash_profile in order to force it to be read by a login shell.&qu
Hi,
Debian 12 here, obtained by upgrading Debian 11.
In https://wiki.debian.org/DotFiles the sixth paragraph states, "You
should therefore always have command source ~/.bashrc at the end of
your .bash_profile in order to force it to be read by a login shell."
# ls ~/.bash_profile
On Sun, Sep 03, 2023 at 01:35:14PM +0200, Marco wrote:
> Am 03.09.2023 um 10:06:15 Uhr schrieb Michael Kjörling:
>
> > On 3 Sep 2023 10:02 +0200, from m...@dorfdsl.de (Marco):
> > > Currently it seems that the mailing list management software isn't
> > > reacha
Am 03.09.2023 um 10:06:15 Uhr schrieb Michael Kjörling:
> On 3 Sep 2023 10:02 +0200, from m...@dorfdsl.de (Marco):
> > Currently it seems that the mailing list management software isn't
> > reachable via HTTPS port 443 or 80, I get a timeout. Port 25 is
> > reachable.
On 3 Sep 2023 10:02 +0200, from m...@dorfdsl.de (Marco):
> Currently it seems that the mailing list management software isn't
> reachable via HTTPS port 443 or 80, I get a timeout. Port 25 is
> reachable.
Worked fine for me at 10:05 UTC.
--
Michael Kjörling
Hello!
Currently it seems that the mailing list management software isn't
reachable via HTTPS port 443 or 80, I get a timeout. Port 25 is
reachable.
--
kind regard
Marco
ever seen anything to be gained
from comparing incoming and outgoing email configurations.
> "man stunnel" mentions "delay DNS lookup for connect option". No
> effect here.
>
> "@reboot root stunnel" in /etc/crontab starts a process after which
> the
I don't have the ability to read thoughts. [To know you're
going to the store for coffee cream.]
Incidentally, in Debian 11, POP3 works via stunnel. The only
difficulty is to automate stunnel startup for non-inetd operation.
Start stunnel at boot up.
"man stunnel" mentions "
Le 10/04/2023 à 21:37, Greg Wooledge a écrit :
On Mon, Apr 10, 2023 at 12:13:15PM -0700, pe...@easthope.ca wrote:
Name: hornby.islandhosting.com
Address: 158.69.159.172
As expected, login at https://hornby.islandhosting.com:2096 and at
https://mail.easthope.ca:2096 appear equivalent.
But
On Mon 10 Apr 2023 at 12:13:15 (-0700), pe...@easthope.ca wrote:
> [ … ]
Others have covered your "oddity", likely caused by a certificate
that seems normal.
> As expected, login at https://hornby.islandhosting.com:2096 and at
> https://mail.easthope.ca:2096 appear equival
Le 10 avril 2023 peter a écrit :
> "Warning: Potential Security Risk Ahead
>
> Firefox detected a potential security threat and did not continue to
> 158.69.159.172. If you visit this site, attackers could try to steal
> information like your passwords, emails, or credit card details.
>
> What can
Hello,
On Mon, Apr 10, 2023 at 12:13:15PM -0700, pe...@easthope.ca wrote:
> As expected, login at https://hornby.islandhosting.com:2096 and at
> https://mail.easthope.ca:2096 appear equivalent.
>
> But for URL https://158.69.159.172:2096 Firefox warns,
What told you to use the URL
a.
> Name: easthope.ca
> Address: 158.69.159.172
>
> As expected, login at https://hornby.islandhosting.com:2096 and at
> https://mail.easthope.ca:2096 appear equivalent.
>
> But for URL https://158.69.159.172:2096 Firefox warns,
>
> "Warning: Potential Sec
anonical name = easthope.ca.
> Name: easthope.ca
> Address: 158.69.159.172
>
> As expected, login at https://hornby.islandhosting.com:2096 and at
> https://mail.easthope.ca:2096 appear equivalent.
>
> But for URL https://158.69.159.172:2096 Firefox warns,
>
> "Warn
On Mon, Apr 10, 2023 at 12:13:15PM -0700, pe...@easthope.ca wrote:
> Name: hornby.islandhosting.com
> Address: 158.69.159.172
> As expected, login at https://hornby.islandhosting.com:2096 and at
> https://mail.easthope.ca:2096 appear equivalent.
>
> But for URL https://1
::
$ nslookup mail.easthope.ca
Server: 192.168.0.1
Address:192.168.0.1#53
Non-authoritative answer:
mail.easthope.cacanonical name = easthope.ca.
Name: easthope.ca
Address: 158.69.159.172
As expected, login at https://hornby.islandhosting.com:2096 and at
https
Hi,
Patrice Duroux wrote:
> I have done a little change to its content but then I realized that
> it is written that the list is generated from:
> https://salsa.debian.org/nodiscc2-guest/awesome-linuxaudio
>
> I think that it should be:
> https://salsa.debian.org/nodiscc/
Hi,
I have done a little change to its content but then I realized that
it is written that the list is generated from:
https://salsa.debian.org/nodiscc2-guest/awesome-linuxaudio
I think that it should be:
https://salsa.debian.org/nodiscc/awesome-linuxaudio
But the page shows currently a
On Tue, 7 Jun 2022 09:30:57 -0400
Amn wrote:
Hello Amn,
>I vote to remove this account from the list.
Except this list doesn't require one to subscribe to be able to post.
Best bet is, I suspect, to use a killfile.
--
Regards _
/ ) "The blindingly obvious is never immediately
a relationship with another man. He was subjected to
chemical castration as an alternative to going to prison.
https://en.wikinews.org/wiki/Alan_Turing_given_posthumous_pardon
Arne
00
> "sp...@caiway.net" wrote:
>
> > The ability for the British to decode German communication may possibly
> > have shortened the war by two years. In 1952, Turing was convicted of gross
> > indecency after he had a relationship wit
ross
> indecency after he had a relationship with another man. He was subjected to
> chemical castration as an alternative to going to prison.
>
> https://en.wikinews.org/wiki/Alan_Turing_given_posthumous_pardon
>
>
> Arne
>
The ability for the British to decode German communication may possibly have
shortened the war by two years. In 1952, Turing was convicted of gross
indecency after he had a relationship with another man. He was subjected to
chemical castration as an alternative to going to prison.
https
l mail machine and
> it would use PAM or suchlike to look up mail usernames and passwords rather
> than me having to maintain separate user/password files.
>
> What candidates are there for a standalone https authorisation server? Or a
> plug in module for an nginx instance running o
ke to look up mail usernames and passwords
rather than me having to maintain separate user/password files.
What candidates are there for a standalone https authorisation server?
Or a plug in module for an nginx instance running on the internal mail
server?
Thanks,
--
Jeremy
OpenPGP_sign
On Wed, 26 May 2021 20:55:16 +0200
deloptes wrote:
> James H. H. Lampert wrote:
>
> > At least the OP was polite enough to *ask* about posting ads, rather
> > than just *doing* it.
>
> Send him/her flowers :)
>
statue in every major city
James H. H. Lampert wrote:
> At least the OP was polite enough to *ask* about posting ads, rather
> than just *doing* it.
Send him/her flowers :)
The price is our souls, and we all agree that's too high.
Hmm. Isn't that also the price of anything sold at Wal-Mart?
* * *
At least the OP was polite enough to *ask* about posting ads, rather
than just *doing* it.
--
JHHL
On 5/25/21, Dan Ritter wrote:
> Valeriya Shiyan wrote:
>> Hi!
>>
>> I want to post a sponsored article with 1-2 dofollow links on your site
>> https://debian.org.
>>
>> Is it possible? What price?
>>
>> ---
>
> The price is our souls, and w
Valeriya Shiyan wrote:
> Hi!
>
> I want to post a sponsored article with 1-2 dofollow links on your site
> https://debian.org.
>
> Is it possible? What price?
>
> ---
The price is our souls, and we all agree that's too high.
-dsr-
Hi!
I want to post a sponsored article with 1-2 dofollow links on your site
https://debian.org.
Is it possible? What price?
---
On Thu, May 20, 2021 at 01:20:08PM +0100, Darac Marjal wrote:
> A great place to start is the SSL Labs Server Test -
> https://www.ssllabs.com/ssltest/analyze.html?d=ojs.lub.lu.se&latest -
> This will perform various handshakes with a HTTPS server a
On Fri, 21 May 2021 06:02:10 +
Bonno Bloksma wrote:
> Hi Celejar,
>
> >>> Although everything works properly for actual (human) users, a
> >>> coworker has informed me that some of his automated tests are
> >>> failing with invalid http
Hi Celejar,
>>> Although everything works properly for actual (human) users, a
>>> coworker has informed me that some of his automated tests are
>>> failing with invalid https certificate errors. I checked and, sure
>>> enough, it's not just hi
On Thu, 20 May 2021 13:20:08 +0100
Darac Marjal wrote:
>
> On 20/05/2021 12:03, d...@sherohman.org wrote:
> > Although everything works properly for actual (human) users, a coworker
> > has informed me that some of his automated tests are failing with
> > invalid http
On 20/05/2021 12:03, d...@sherohman.org wrote:
> Although everything works properly for actual (human) users, a coworker
> has informed me that some of his automated tests are failing with
> invalid https certificate errors. I checked and, sure enough, it's not
> just his tests:
Although everything works properly for actual (human) users, a coworker
has informed me that some of his automated tests are failing with
invalid https certificate errors. I checked and, sure enough, it's not
just his tests:
$ curl https://ojs.lub.lu.se
curl: (60) SSL certificate problem: u
On Thu, Apr 15, 2021 at 04:43:12PM +0100, piorunz wrote:
Of course, 404 error on https version of the website it a
great piece of content. Admins are doing great job.
On the root page, sure. Who knows if they're actively serving content
on a sub-path.
Anyway, it's easy to thr
On Thu, Apr 15, 2021 at 09:32:03AM -0400, Dan Ritter wrote:
Kenneth Parker wrote:
I use lighttpd for eyeblinkuniverse.com, with nano as my editor. I don't
quite understand the Certificates required for https. I guess it is time
for some lessons.
The easiest thing to do here is to in
On Fri, 2021-04-16 at 13:08 +1200, Richard Hector wrote:
> On 16/04/21 1:32 am, Dan Ritter wrote:
> > Last step: create a cron job to run once a week that does
> > this:
> >
> > certbot renew && \
> > cat /etc/letsencrypt/live/eyeblinkuniverse.com/privkey.pem \
> > /etc/letsencrypt/live/eyeblinkun
On 16/04/21 1:32 am, Dan Ritter wrote:
Last step: create a cron job to run once a week that does
this:
certbot renew && \
cat /etc/letsencrypt/live/eyeblinkuniverse.com/privkey.pem \
/etc/letsencrypt/live/eyeblinkuniverse.com/cert.pem > \
/etc/letsencrypt/live/eyeblinkuniverse/merged.pem && \
se
On 15/04/2021 15:49, Erwan David wrote:
If webadmin FORGETS to implement https in 2021, then he deserves losing
his job. 🤯
But nothing says that http:// and https:// must have
same content.
Of course, 404 error on https version of the website it a
great piece of content. Admins are doing
On Thu, 15 Apr 2021 09:31:11 -0300
Eduardo M KALINOWSKI wrote:
>
> On 15/04/2021 09:12, Celejar wrote:
> > On Thu, 15 Apr 2021 11:16:59 +0100
> > piorunz wrote:
> >
> >> On 15/04/2021 03:15, Celejar wrote:
> >>
> >>> http://www.daat.ac
Le 15/04/2021 à 16:16, piorunz a écrit :
On 15/04/2021 13:40, mett wrote:
So, indeed, some misconfiguration it seems.
Maybe they simply forget to redirect http to https.
Though I agree no need to shun them.
HTH
If webadmin FORGETS to implement https in 2021, then he deserves losing
his
On Thu, Apr 15, 2021, 9:32 AM Dan Ritter wrote:
> Kenneth Parker wrote:
> >
> > I use lighttpd for eyeblinkuniverse.com, with nano as my editor. I don't
> > quite understand the Certificates required for https. I guess it is time
> > for some lessons.
>
&
On 15/04/2021 13:40, mett wrote:
So, indeed, some misconfiguration it seems.
Maybe they simply forget to redirect http to https.
Though I agree no need to shun them.
HTH
If webadmin FORGETS to implement https in 2021, then he deserves losing
his job. 🤯
--
With kindest regards, piorunz
Kenneth Parker wrote:
>
> I use lighttpd for eyeblinkuniverse.com, with nano as my editor. I don't
> quite understand the Certificates required for https. I guess it is time
> for some lessons.
The easiest thing to do here is to install certbot.
Assuming that your web root is
2021-04-15 21:12 に Celejar さんは書きました:
On Thu, 15 Apr 2021 11:16:59 +0100
piorunz wrote:
On 15/04/2021 03:15, Celejar wrote:
>> It certainly works fine for me. I use https only mode for many months
>> now. Can you bring an example of a page which returns good page on http,
>>
On Thu, Apr 15, 2021 at 01:31:45PM +0100, Jonathan Dowland wrote:
On Thu, Apr 15, 2021 at 11:44:21AM +0100, Darac Marjal wrote:
If they don't support https, they shouldn't respond at all.
Perhaps they do, but not for the hostname being used here to access the
web server.
Although
On Thu, Apr 15, 2021 at 11:44:21AM +0100, Darac Marjal wrote:
If they don't support https, they shouldn't respond at all.
Perhaps they do, but not for the hostname being used here to access the
web server.
--
Please do not CC me, I am subscribed to the list.
👱🏻 Jonathan
On 15/04/2021 09:12, Celejar wrote:
On Thu, 15 Apr 2021 11:16:59 +0100
piorunz wrote:
On 15/04/2021 03:15, Celejar wrote:
http://www.daat.ac.il/
https://www.daat.ac.il/
Celejar
I can confirm the problem, by the way.
Their webserver is misconfigured. AFAIR, if they don't support
On Thu, 15 Apr 2021 11:16:59 +0100
piorunz wrote:
> On 15/04/2021 03:15, Celejar wrote:
>
> >> It certainly works fine for me. I use https only mode for many months
> >> now. Can you bring an example of a page which returns good page on http,
> >> but
On Thu, Apr 15, 2021 at 11:16:59AM +0100, piorunz wrote:
> TLS 2.0/3.0 only
Nitpick: TLS 1.2 and 1.3.
On 15/04/2021 11:16, piorunz wrote:
> On 15/04/2021 03:15, Celejar wrote:
>
>>> It certainly works fine for me. I use https only mode for many months
>>> now. Can you bring an example of a page which returns good page on
>>> http,
>>> but 404 error on ht
On 15/04/2021 03:15, Celejar wrote:
It certainly works fine for me. I use https only mode for many months
now. Can you bring an example of a page which returns good page on http,
but 404 error on https?
http://www.daat.ac.il/
https://www.daat.ac.il/
Celejar
Their webserver is misconfigured
> > > Hi,
> > > >
> > > > I recently switched to Firefox's native HTTPS-Only mode from the
> > > > HTTPS Everywhere extension, and I've just made the nasty discovery
> that
> > > > a bunch of links that had been returni
Kenneth Parker writes:
> On Wed, Apr 14, 2021 at 10:16 PM Celejar wrote:
>
> On Wed, 14 Apr 2021 22:57:01 +0100
> piorunz wrote:
>
> > On 14/04/2021 17:19, Celejar wrote:
> > > Hi,
> > >
> > > I recently switched to Firefox's na
On Wed, Apr 14, 2021 at 10:16 PM Celejar wrote:
> On Wed, 14 Apr 2021 22:57:01 +0100
> piorunz wrote:
>
> > On 14/04/2021 17:19, Celejar wrote:
> > > Hi,
> > >
> > > I recently switched to Firefox's native HTTPS-Only mode from the
> > >
On Wed, 14 Apr 2021 16:01:13 -0300
riveravaldez wrote:
> On 4/14/21, Celejar wrote:
> > Hi,
> >
> > I recently switched to Firefox's native HTTPS-Only mode from the
> > HTTPS Everywhere extension, and I've just made the nasty discovery that
> > a
On Wed, 14 Apr 2021 22:57:01 +0100
piorunz wrote:
> On 14/04/2021 17:19, Celejar wrote:
> > Hi,
> >
> > I recently switched to Firefox's native HTTPS-Only mode from the
> > HTTPS Everywhere extension, and I've just made the nasty discovery that
> > a
On Wed, Apr 14, 2021 at 16:01:13 -0300, riveravaldez wrote:
>
> Not sure if useful at all, but I've been using firefox-release (just running
> the binary from Mozilla) as main browser for years, and enabled HTTPS-
> Only Mode upon HTTPS Everywhere add-on/extension simply b
On 14/04/2021 17:19, Celejar wrote:
Hi,
I recently switched to Firefox's native HTTPS-Only mode from the
HTTPS Everywhere extension, and I've just made the nasty discovery that
a bunch of links that had been returning 404, which I had been assuming
were dead links, were actually perfe
On 4/14/21, Celejar wrote:
> Hi,
>
> I recently switched to Firefox's native HTTPS-Only mode from the
> HTTPS Everywhere extension, and I've just made the nasty discovery that
> a bunch of links that had been returning 404, which I had been assuming
> were dead li
Hi,
I recently switched to Firefox's native HTTPS-Only mode from the
HTTPS Everywhere extension, and I've just made the nasty discovery that
a bunch of links that had been returning 404, which I had been assuming
were dead links, were actually perfectly valid pages, which Firefo
It;s not https, it's JavaScript. Having to do ad-blockers, maybe.
Mark
On 10/15/2020 3:11 PM, Gene Heskett wrote:
On Thursday 15 October 2020 14:22:39 l0f...@tuta.io wrote:
Hi,
15 oct. 2020 à 18:26 de ghesk...@shentel.net:
But I've not been able to click on an "https&qu
On Thursday 15 October 2020 14:22:39 l0f...@tuta.io wrote:
> Hi,
>
> 15 oct. 2020 à 18:26 de ghesk...@shentel.net:
> > But I've not been able to click on an "https" link and have it work.
>
> Where is your link? I mean is it a link on a webpage or is it inside
38:44 Reco wrote:
>> > > >Hi.
>> > > >
>> > > > On Thu, Oct 15, 2020 at 12:26:52PM -0400, Gene Heskett wrote:
>> > > > > But I've not been able to click on an "https" link and have it
>> > > > > wor
Hi,
15 oct. 2020 à 18:26 de ghesk...@shentel.net:
> But I've not been able to click on an "https" link and have it work.
>
Where is your link? I mean is it a link on a webpage or is it inside a text
editor for example?
Can you share a working link and a bad one?
Best regards,
l0f4r0
gt; > >
> > > > On Thu, Oct 15, 2020 at 12:26:52PM -0400, Gene Heskett wrote:
> > > > > But I've not been able to click on an "https" link and have it
> > > > > work.
> > > >
> > > > Please provide an exact error me
> > But I've not been able to click on an "https" link and have it
> > > > work.
> > >
> > > Please provide an exact error message. Show, do not tell.
> >
> > No error msg, it just ignores the click.
>
> Now that is interesting.
On Thu, Oct 15, 2020 at 12:49:01PM -0400, Gene Heskett wrote:
> On Thursday 15 October 2020 12:38:44 Reco wrote:
>
> > Hi.
> >
> > On Thu, Oct 15, 2020 at 12:26:52PM -0400, Gene Heskett wrote:
> > > But I've not been able to click on an "https"
On Thursday 15 October 2020 12:38:44 Reco wrote:
> Hi.
>
> On Thu, Oct 15, 2020 at 12:26:52PM -0400, Gene Heskett wrote:
> > But I've not been able to click on an "https" link and have it work.
>
> Please provide an exact error message. Show, do not t
Hi.
On Thu, Oct 15, 2020 at 12:26:52PM -0400, Gene Heskett wrote:
> But I've not been able to click on an "https" link and have it work.
Please provide an exact error message. Show, do not tell.
Reco
e not been able to click on an "https" link and have it work.
Obviously I am missing the package that services the "s". Except it
does work with my banks https. They may be using an older version or ?
IDK.
Can anyone look in their crystal ball and tell me what pkg that might
Hi Greg,
> > How do I get in contact with somebody who can fix the problem in
> > Debian Buser and/ or the official Debian Buster arm32v7 Docker image?
>
> Looks a bit like <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923479>
> to me.
Thanks a lot! Yes, this
?
>
> I *think* that the problem is that these numbered links are missing.
>
> How do I get in contact with somebody who can fix the problem in
> Debian Buser and/ or the official Debian Buster arm32v7 Docker image?
Looks a bit like <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923479>
to me.
Hi Reco,
> > Yes, I have my own Dockerfile and I can add to it whatever I want. But
> > "dpkg-reconfigure ca-certificates" asks a lot of questions. And that
> > list from 1 to 128 might eventually change. So I am puzzled how to
> > automate that without human intervention.
>
> dpkg-reconfigure --d
Hi Greg,
> You... *think* it's there? Why not actually look?
>
> unicorn:~$ ls -l /etc/ssl/certs/4a6481c9.0
> lrwxrwxrwx 1 root root 27 Jul 14 2018 /etc/ssl/certs/4a6481c9.0 ->
> GlobalSign_Root_CA_-_R2.pem
>
> It takes a few seconds, and then you can remove all doubt.
Correct, the file is not
Hi Michael,
yes, I also tried "update-ca-certificates" and it doesn't work.
# curl https://www.google.com
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html
curl failed to verify the legitimacy of
> > > 1613 stat64("/etc/ssl/certs/4a6481c9.0", 0x7ec95160) = -1 ENOENT (No
> > > such file or directory)
> >
> > Presumably ca-certificates postinst script haven't run, because these
> > symlinks missing ain't normal.
>
> Ubuntu 18.04 on my PC gives more or less the same errors but succeeds.
> So
On Tue, May 05, 2020 at 08:44:43AM +0200, Mark Jonas wrote:
> Hi Reco,
>
> > > What now? How do I get this fixed in Debian and/ or the official
> > > container image?
> >
> > I was under the impression that you're creating your own docker
> > container anyway.
> > Add it to docker build file or wh
this is a
start:
https://hub.docker.com/_/debian/
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
signature.asc
Description: PGP signature
On 05/05/2020 07:44, Mark Jonas wrote:
Hi Reco,
What now? How do I get this fixed in Debian and/ or the official
container image?
I was under the impression that you're creating your own docker
container anyway.
Add it to docker build file or whatever it's called.
Yes, I have my own Dockerfil
Hi Reco,
> > What now? How do I get this fixed in Debian and/ or the official
> > container image?
>
> I was under the impression that you're creating your own docker
> container anyway.
> Add it to docker build file or whatever it's called.
Yes, I have my own Dockerfile and I can add to it whate
Hi.
On Tue, May 05, 2020 at 08:05:04AM +0200, Mark Jonas wrote:
> What now? How do I get this fixed in Debian and/ or the official
> container image?
I was under the impression that you're creating your own docker
container anyway.
Add it to docker build file or whatever it's called.
Rec
85 86
87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107
108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124
125 126 127 128
Updating certificates in /etc/ssl/certs...
128 added, 0 removed; done.
3. "curl https://www.google.com"; now succeeds
Hi.
On Mon, May 04, 2020 at 08:41:43PM +0200, Mark Jonas wrote:
> Hi Reco,
>
> > > I used the identical image to run the container on an amhf host
> > > (Raspberry Pi 3). So there is now no QEMU in the way.
> >
> > Curious. Just tested it with curl at Marvell Armada 385 (runs Debian 10,
>
n Exynos 5422 (also runs Debian 10, armhf), but
> it'll be the same.
Do you want to try the Docker image on one of these? Maybe the problem
is not Debian itself but only the official Debian Docker image?
> > curl https://www.google.com still fails on the armhf host. So QEMU is
> >
Hi Tomas,
> > Yes, "curl -k https:/www.google.com" succeeds.
>
> Then it's quite probable that the problem lies with certificate
> resolution. Either it doesn't find a trusted root cert to validate
> the server against, or the validation fails.
>
> You
1 - 100 of 693 matches
Mail list logo
