This is probably the wrong group to ask, but I will start here and then follow any pointers to where I should ask my question... I am running Leap 15.4 with the KDE/Plasma desktop. There is a bug, reported and fixed/resolved - https://bugs.kde.org/show_bug.cgi?id=453280 which is bugging me now. This was resolved last year (June) and I am wondering when this fix will show up in an update for my system? It is annoying to have to log out and log back in whenever this problem shows up on my systems, so I thought I would ask and hopefully get an update soon that fixes it. Marc... -- *"The Truth is out there" - Spooky* *_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . * Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (/This email is digitally signed and the OpenPGP electronic signature is added as an attachment. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the OpenPGP signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)
Organization: Ptilopteri in Pandemonium * Marc Chamberlin <marc@marcchamberlin.com> [01-18-23 17:01]:
This is probably the wrong group to ask, but I will start here and then follow any pointers to where I should ask my question...
I am running Leap 15.4 with the KDE/Plasma desktop. There is a bug, reported and fixed/resolved - https://bugs.kde.org/show_bug.cgi?id=453280 which is bugging me now. This was resolved last year (June) and I am wondering when this fix will show up in an update for my system? It is annoying to have to log out and log back in whenever this problem shows up on my systems, so I thought I would ask and hopefully get an update soon that fixes it.
Marc...
--
*"The Truth is out there" - Spooky*
*_ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . *
Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before!
(/This email is digitally signed and the OpenPGP electronic signature is added as an attachment. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the OpenPGP signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)
[-- Error: unable to create PGP subprocess! --] you might do something about that unenforcable signature, Marc https://software.opensuse.org/package/kscreen5 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Organization: Ptilopteri in Pandemonium
* Marc Chamberlin <marc@marcchamberlin.com> [01-18-23 17:01]:
I am running Leap 15.4 with the KDE/Plasma desktop. There is a bug, reported and fixed/resolved - https://bugs.kde.org/show_bug.cgi?id=453280 which is bugging me now. This was resolved last year (June) and I am wondering when this fix will show up in an update for my system? It is annoying to have to log out and log back in whenever this problem shows up on my systems, so I thought I would ask and hopefully get an update soon that fixes it.
Marc...
[-- Error: unable to create PGP subprocess! --] Patrick - I will try to remember to remove the signature from my
On 1/18/23 14:08, Patrick Shanahan wrote: postings to this news list, but cannot guarantee I will always remember to do so. (getting older ;-) ) As for the error message you are getting about the PGP subprocess, my internet Google searches suggests the problem is on your end and that you are missing some PGP libraries that allow your email client (Thunderbird?) to verify my PGP signature automagically.
you might do something about that unenforcable signature, Marc
Thanks for the link, I have installed kscreen5 on my systems, will see if this resolves the problem. (So far, looking promising) Marc...
* Marc Chamberlin <marc@marcchamberlin.com> [01-22-23 12:47]:
Organization: Ptilopteri in Pandemonium
* Marc Chamberlin <marc@marcchamberlin.com> [01-18-23 17:01]:
I am running Leap 15.4 with the KDE/Plasma desktop. There is a bug, reported and fixed/resolved - https://bugs.kde.org/show_bug.cgi?id=453280 which is bugging me now. This was resolved last year (June) and I am wondering when this fix will show up in an update for my system? It is annoying to have to log out and log back in whenever this problem shows up on my systems, so I thought I would ask and hopefully get an update soon that fixes it.
Marc...
[-- Error: unable to create PGP subprocess! --] Patrick - I will try to remember to remove the signature from my postings to
you might do something about that unenforcable signature, Marc
Thanks for the link, I have installed kscreen5 on my systems, will see if
On 1/18/23 14:08, Patrick Shanahan wrote: this news list, but cannot guarantee I will always remember to do so. (getting older ;-) ) As for the error message you are getting about the PGP subprocess, my internet Google searches suggests the problem is on your end and that you are missing some PGP libraries that allow your email client (Thunderbird?) to verify my PGP signature automagically. this resolves the problem. (So far, looking promising) Marc...
[-- Error: unable to create PGP subprocess! --] I really do not care about gpg/pgp errors as I can see no reason to inflate list raffic by including them. and it goes on and on, a single line of reply attached to an 800 line quote with a 1000 line header and 50 lines of signature and added lines declaring gpg/pgp. it's all just more traffic. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Patrick Shanahan composed on 2023-01-22 13:05 (UTC-0500):
I really do not care about gpg/pgp errors as I can see no reason to inflate list raffic by including them. and it goes on and on, a single line of reply attached to an 800 line quote with a 1000 line header and 50 lines of signature and added lines declaring gpg/pgp. it's all just more traffic.
Which you could reduce yourself by trimming what you quote down to a relevant level. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2023-01-18 23:08, Patrick Shanahan wrote:
Organization: Ptilopteri in Pandemonium
(/This email is digitally signed and the OpenPGP electronic signature is added as an attachment. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the OpenPGP signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)
[-- Error: unable to create PGP subprocess! --]
you might do something about that unenforcable signature, Marc
Works fine here. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [01-22-23 15:40]:
On 2023-01-18 23:08, Patrick Shanahan wrote:
Organization: Ptilopteri in Pandemonium
(/This email is digitally signed and the OpenPGP electronic signature is added as an attachment. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the OpenPGP signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like./)
[-- Error: unable to create PGP subprocess! --]
you might do something about that unenforcable signature, Marc
Works fine here.
-- Cheers / Saludos,
Carlos E. R. (from 15.4 x86_64 at Telcontar)
really, not commenting nor really concerned about gpg/pgp, wasted electrons in this forum. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Carlos E. R. wrote:
On 2023-01-18 23:08, Patrick Shanahan wrote:
[-- Error: unable to create PGP subprocess! --]
you might do something about that unenforcable signature, Marc
Works fine here.
Doesn't work here - I dare say it depends on whether local support has been set up. -- Per Jessen, Zürich (-0.9°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-23 11:16, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-18 23:08, Patrick Shanahan wrote:
[-- Error: unable to create PGP subprocess! --]
you might do something about that unenforcable signature, Marc
Works fine here.
Doesn't work here - I dare say it depends on whether local support has been set up.
Patrick is using Mutt, which is ancient software, and I am using Thunderbird, which uses a very new implementation; although Marc uses an old version, I don't know if it is old enough to use enigmail implementation. Alpine has a problem with Thunderbird: alpine uses inline pgp, which Th does not support, and uses attached signature, which alpine does not support. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
Patrick is using Mutt, which is ancient software, and I am using Thunderbird, which uses a very new implementation; although Marc uses an old version, I don't know if it is old enough to use enigmail implementation.
Alpine has a problem with Thunderbird: alpine uses inline pgp, which Th does not support, and uses attached signature, which alpine does not support.
All in all, it sounds like a really good argument for not using PGP on mailing list traffic :-) -- Per Jessen, Zürich (0.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-23 12:56, Per Jessen wrote:
Carlos E. R. wrote:
Patrick is using Mutt, which is ancient software, and I am using Thunderbird, which uses a very new implementation; although Marc uses an old version, I don't know if it is old enough to use enigmail implementation.
Alpine has a problem with Thunderbird: alpine uses inline pgp, which Th does not support, and uses attached signature, which alpine does not support.
All in all, it sounds like a really good argument for not using PGP on mailing list traffic :-)
I can't. Long ago, people impersonated me, sending mail with my name and address, and people thought it was me insulting listers. Since then, I always sign my emails. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-01-23 12:56, Per Jessen wrote:
Carlos E. R. wrote:
Patrick is using Mutt, which is ancient software, and I am using Thunderbird, which uses a very new implementation; although Marc uses an old version, I don't know if it is old enough to use enigmail implementation.
Alpine has a problem with Thunderbird: alpine uses inline pgp, which Th does not support, and uses attached signature, which alpine does not support.
All in all, it sounds like a really good argument for not using PGP on mailing list traffic :-)
I can't.
We were talking about the general idea. Your signature is only 10-12 lines, I don't imagine many people having a serious issue with that, (even if it mostly doesn't work). Your two new postings from about 30mins ago looks good to me, knode said the signature was valid, but untrusted. Your replies in this thread are not recognised as having any signature, it just appears as an attachment.
Long ago, people impersonated me, sending mail with my name and address, and people thought it was me insulting listers. Since then, I always sign my emails.
Which brings you virtually nothing when it doesn't work in many/most cases. See above. -- Per Jessen, Zürich (-0.3°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-23 13:15, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 12:56, Per Jessen wrote:
Carlos E. R. wrote:
Patrick is using Mutt, which is ancient software, and I am using Thunderbird, which uses a very new implementation; although Marc uses an old version, I don't know if it is old enough to use enigmail implementation.
Alpine has a problem with Thunderbird: alpine uses inline pgp, which Th does not support, and uses attached signature, which alpine does not support.
All in all, it sounds like a really good argument for not using PGP on mailing list traffic :-)
I can't.
We were talking about the general idea. Your signature is only 10-12 lines, I don't imagine many people having a serious issue with that, (even if it mostly doesn't work).
Your two new postings from about 30mins ago looks good to me, knode said the signature was valid, but untrusted. Your replies in this thread are not recognised as having any signature, it just appears as an attachment.
Long ago, people impersonated me, sending mail with my name and address, and people thought it was me insulting listers. Since then, I always sign my emails.
Which brings you virtually nothing when it doesn't work in many/most cases. See above.
When it doesn't work, the fault is mostly at the receiver side, not mine. But of course, even the openSUSE key server is broken. cer@Elesar:~> gpg --keyserver keyserver.opensuse.org --search-keys 0xF62B7584 gpg: error searching keyserver: No name gpg: keyserver search failed: No name cer@Elesar:~> (example command taken from <https://news.opensuse.org/2016/12/06/announcing-opensuses-gpg-key-server-keyserver-opensuse-org/> -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
Carlos E. R. wrote:
On 2023-01-23 13:15, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 12:56, Per Jessen wrote:
Carlos E. R. wrote:
Patrick is using Mutt, which is ancient software, and I am using Thunderbird, which uses a very new implementation; although Marc uses an old version, I don't know if it is old enough to use enigmail implementation.
Alpine has a problem with Thunderbird: alpine uses inline pgp, which Th does not support, and uses attached signature, which alpine does not support.
All in all, it sounds like a really good argument for not using PGP on mailing list traffic :-)
I can't.
We were talking about the general idea. Your signature is only 10-12 lines, I don't imagine many people having a serious issue with that, (even if it mostly doesn't work).
Your two new postings from about 30mins ago looks good to me, knode said the signature was valid, but untrusted. Your replies in this thread are not recognised as having any signature, it just appears as an attachment.
Long ago, people impersonated me, sending mail with my name and address, and people thought it was me insulting listers. Since then, I always sign my emails.
Which brings you virtually nothing when it doesn't work in many/most cases. See above.
When it doesn't work, the fault is mostly at the receiver side, not mine.
You might not like it, but it's actually 100% your fault - for your use of PGP to work (which is important to you), people have to make an effort, but that is something you impose on them. Anyway, by all means add those 10-12 lines, although we are allowed to wonder why.
But of course, even the openSUSE key server is broken.
cer@Elesar:~> gpg --keyserver keyserver.opensuse.org --search-keys 0xF62B7584 gpg: error searching keyserver: No name gpg: keyserver search failed: No name
See my signature. -- Per Jessen, Zürich (0.2°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-23 17:54, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 13:15, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 12:56, Per Jessen wrote:
Carlos E. R. wrote:
Patrick is using Mutt, which is ancient software, and I am using Thunderbird, which uses a very new implementation; although Marc uses an old version, I don't know if it is old enough to use enigmail implementation.
Alpine has a problem with Thunderbird: alpine uses inline pgp, which Th does not support, and uses attached signature, which alpine does not support.
All in all, it sounds like a really good argument for not using PGP on mailing list traffic :-)
I can't.
We were talking about the general idea. Your signature is only 10-12 lines, I don't imagine many people having a serious issue with that, (even if it mostly doesn't work).
Your two new postings from about 30mins ago looks good to me, knode said the signature was valid, but untrusted. Your replies in this thread are not recognised as having any signature, it just appears as an attachment.
Long ago, people impersonated me, sending mail with my name and address, and people thought it was me insulting listers. Since then, I always sign my emails.
Which brings you virtually nothing when it doesn't work in many/most cases. See above.
When it doesn't work, the fault is mostly at the receiver side, not mine.
You might not like it, but it's actually 100% your fault - for your use of PGP to work (which is important to you), people have to make an effort, but that is something you impose on them.
No, it is people's choice not to repair their configurations so that it works for them.
Anyway, by all means add those 10-12 lines, although we are allowed to wonder why.
But of course, even the openSUSE key server is broken.
cer@Elesar:~> gpg --keyserver keyserver.opensuse.org --search-keys 0xF62B7584 gpg: error searching keyserver: No name gpg: keyserver search failed: No name
See my signature.
I know. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
Carlos E. R. wrote:
On 2023-01-23 17:54, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 13:15, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 12:56, Per Jessen wrote:
Carlos E. R. wrote:
> Patrick is using Mutt, which is ancient software, and I am using > Thunderbird, which uses a very new implementation; although Marc > uses an old version, I don't know if it is old enough to use > enigmail implementation. > > Alpine has a problem with Thunderbird: alpine uses inline pgp, > which Th does not support, and uses attached signature, which > alpine does not support.
All in all, it sounds like a really good argument for not using PGP on mailing list traffic :-)
I can't.
We were talking about the general idea. Your signature is only 10-12 lines, I don't imagine many people having a serious issue with that, (even if it mostly doesn't work).
Your two new postings from about 30mins ago looks good to me, knode said the signature was valid, but untrusted. Your replies in this thread are not recognised as having any signature, it just appears as an attachment.
Long ago, people impersonated me, sending mail with my name and address, and people thought it was me insulting listers. Since then, I always sign my emails.
Which brings you virtually nothing when it doesn't work in many/most cases. See above.
When it doesn't work, the fault is mostly at the receiver side, not mine.
You might not like it, but it's actually 100% your fault - for your use of PGP to work (which is important to you), people have to make an effort, but that is something you impose on them.
No, it is people's choice not to repair their configurations so that it works for them.
So, _I_ am at fault for _your_ PGP usage causing weird error messages on my system? Not my kind of logic, but let's not pursue that here. -- Per Jessen, Zürich (0.0°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-23 18:40, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 17:54, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 13:15, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 12:56, Per Jessen wrote: > Carlos E. R. wrote:
...
When it doesn't work, the fault is mostly at the receiver side, not mine.
You might not like it, but it's actually 100% your fault - for your use of PGP to work (which is important to you), people have to make an effort, but that is something you impose on them.
No, it is people's choice not to repair their configurations so that it works for them.
So, _I_ am at fault for _your_ PGP usage causing weird error messages on my system? Not my kind of logic, but let's not pursue that here.
You could ask for help to make your system to accept PGP keys ;-) -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
* Carlos E. R. <robin.listas@telefonica.net> [01-23-23 12:51]:
On 2023-01-23 18:40, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 17:54, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 13:15, Per Jessen wrote:
Carlos E. R. wrote: > On 2023-01-23 12:56, Per Jessen wrote: > > Carlos E. R. wrote:
...
When it doesn't work, the fault is mostly at the receiver side, not mine.
You might not like it, but it's actually 100% your fault - for your use of PGP to work (which is important to you), people have to make an effort, but that is something you impose on them.
No, it is people's choice not to repair their configurations so that it works for them.
So, _I_ am at fault for _your_ PGP usage causing weird error messages on my system? Not my kind of logic, but let's not pursue that here.
You could ask for help to make your system to accept PGP keys ;-)
why?
-- Cheers / Saludos,
Carlos E. R.
(from Elesar, using openSUSE Leap 15.4)
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Carlos E. R. wrote:
On 2023-01-23 18:40, Per Jessen wrote:
So, _I_ am at fault for _your_ PGP usage causing weird error messages on my system? Not my kind of logic, but let's not pursue that here.
You could ask for help to make your system to accept PGP keys ;-)
Despite the somewhat unusual idea of me having to do something to accommodate you, maybe I'll take you up on it. What do I need to do to knode, primarily to avoid this (see attached). -- Per Jessen, Zürich (0.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-23 19:57, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 18:40, Per Jessen wrote:
So, _I_ am at fault for _your_ PGP usage causing weird error messages on my system? Not my kind of logic, but let's not pursue that here.
You could ask for help to make your system to accept PGP keys ;-)
Despite the somewhat unusual idea of me having to do something to accommodate you, maybe I'll take you up on it.
What do I need to do to knode, primarily to avoid this (see attached).
LOL. Migrate to Thunderbird :-D :-P AFAIK, Knode does not support pgp/mime. <https://lists.gnupg.org/pipermail/gnupg-users/2003-June/018755.html> -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
* Carlos E. R. <robin.listas@telefonica.net> [01-23-23 12:25]:
On 2023-01-23 17:54, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 13:15, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 12:56, Per Jessen wrote:
Carlos E. R. wrote:
> Patrick is using Mutt, which is ancient software, and I am using > Thunderbird, which uses a very new implementation; although Marc > uses an old version, I don't know if it is old enough to use > enigmail implementation. > > Alpine has a problem with Thunderbird: alpine uses inline pgp, > which Th does not support, and uses attached signature, which > alpine does not support.
All in all, it sounds like a really good argument for not using PGP on mailing list traffic :-)
I can't.
We were talking about the general idea. Your signature is only 10-12 lines, I don't imagine many people having a serious issue with that, (even if it mostly doesn't work).
Your two new postings from about 30mins ago looks good to me, knode said the signature was valid, but untrusted. Your replies in this thread are not recognised as having any signature, it just appears as an attachment.
Long ago, people impersonated me, sending mail with my name and address, and people thought it was me insulting listers. Since then, I always sign my emails.
Which brings you virtually nothing when it doesn't work in many/most cases. See above.
When it doesn't work, the fault is mostly at the receiver side, not mine.
You might not like it, but it's actually 100% your fault - for your use of PGP to work (which is important to you), people have to make an effort, but that is something you impose on them.
No, it is people's choice not to repair their configurations so that it works for them.
why should I spend time repairing something I believe has no worth, only detriment.
Anyway, by all means add those 10-12 lines, although we are allowed to wonder why.
But of course, even the openSUSE key server is broken.
cer@Elesar:~> gpg --keyserver keyserver.opensuse.org --search-keys 0xF62B7584 gpg: error searching keyserver: No name gpg: keyserver search failed: No name
See my signature.
I know.
-- Cheers / Saludos,
Carlos E. R.
(from Elesar, using openSUSE Leap 15.4)
and your's is "excessive". -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Carlos E. R. wrote:
But of course, even the openSUSE key server is broken.
cer@Elesar:~> gpg --keyserver keyserver.opensuse.org --search-keys 0xF62B7584 gpg: error searching keyserver: No name gpg: keyserver search failed: No name
It's not broken, it's gone: https://status.opensuse.org/incidents/182 -- Per Jessen, Zürich (1.0°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-23 18:15, Per Jessen wrote:
Carlos E. R. wrote:
But of course, even the openSUSE key server is broken.
cer@Elesar:~> gpg --keyserver keyserver.opensuse.org --search-keys 0xF62B7584 gpg: error searching keyserver: No name gpg: keyserver search failed: No name
It's not broken, it's gone: https://status.opensuse.org/incidents/182
Google still finds it. But good to know. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
Carlos E. R. wrote:
On 2023-01-23 18:15, Per Jessen wrote:
Carlos E. R. wrote:
But of course, even the openSUSE key server is broken.
cer@Elesar:~> gpg --keyserver keyserver.opensuse.org --search-keys 0xF62B7584 gpg: error searching keyserver: No name gpg: keyserver search failed: No name
It's not broken, it's gone: https://status.opensuse.org/incidents/182
Google still finds it.
I don't know what google finds, "keyserver.opensuse.org" is gone from our DNS, I checked it just earlier. -- Per Jessen, Zürich (0.6°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-23 18:33, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 18:15, Per Jessen wrote:
Carlos E. R. wrote:
But of course, even the openSUSE key server is broken.
cer@Elesar:~> gpg --keyserver keyserver.opensuse.org --search-keys 0xF62B7584 gpg: error searching keyserver: No name gpg: keyserver search failed: No name
It's not broken, it's gone: https://status.opensuse.org/incidents/182
Google still finds it.
I don't know what google finds, "keyserver.opensuse.org" is gone from our DNS, I checked it just earlier.
cer@Elesar:~> host keyserver.opensuse.org Host keyserver.opensuse.org not found: 3(NXDOMAIN) cer@Elesar:~> Right. Then the gpg command issues a misleading error message: "No name". Anyway, I tried several PGP servers and none works (meaning none finds keys). #keyserver hkp://keys.gnupg.net #keyserver http://http-keys.gnupg.net #keyserver ldap://keyserver.pgp.com #keyserver mailto:pgp-public-keys@keys.nl.pgp.net keyserver https://keyserver.ubuntu.com # Removed from service. #keyserver hkp://keyserver.opensuse.org Oh, the ubuntu server responds now, albeit very slowly: cer@Elesar:~> gpg2 --keyserver https://keyserver.ubuntu.com --search-keys 0xF62B7584 gpg: data source: https://162.213.33.9:443 (1) key 2D9DA383F62B7584 Keys 1-1 of 1 for "0xF62B7584". Enter number(s), N)ext, or Q)uit > gpg: no valid OpenPGP data found. gpg: Total number processed: 0 cer@Elesar:~> Now it finds my keys, but fails to import them: cer@Elesar:~> gpg2 --keyserver https://keyserver.ubuntu.com --recv-keys 0xB533181C6D8D47D5 gpg: no valid OpenPGP data found. gpg: Total number processed: 0 cer@Elesar:~> So, all PGP servers I know are broken, which is what I said. I will have to add "or do not exist anymore". -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
* Carlos E. R. <robin.listas@telefonica.net> [01-23-23 13:04]:
On 2023-01-23 18:33, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 18:15, Per Jessen wrote:
Carlos E. R. wrote:
But of course, even the openSUSE key server is broken.
cer@Elesar:~> gpg --keyserver keyserver.opensuse.org --search-keys 0xF62B7584 gpg: error searching keyserver: No name gpg: keyserver search failed: No name
It's not broken, it's gone: https://status.opensuse.org/incidents/182
Google still finds it.
I don't know what google finds, "keyserver.opensuse.org" is gone from our DNS, I checked it just earlier.
cer@Elesar:~> host keyserver.opensuse.org Host keyserver.opensuse.org not found: 3(NXDOMAIN) cer@Elesar:~>
Right. Then the gpg command issues a misleading error message: "No name".
Anyway, I tried several PGP servers and none works (meaning none finds keys).
#keyserver hkp://keys.gnupg.net #keyserver http://http-keys.gnupg.net #keyserver ldap://keyserver.pgp.com #keyserver mailto:pgp-public-keys@keys.nl.pgp.net keyserver https://keyserver.ubuntu.com
# Removed from service. #keyserver hkp://keyserver.opensuse.org
Oh, the ubuntu server responds now, albeit very slowly:
cer@Elesar:~> gpg2 --keyserver https://keyserver.ubuntu.com --search-keys 0xF62B7584 gpg: data source: https://162.213.33.9:443 (1) key 2D9DA383F62B7584 Keys 1-1 of 1 for "0xF62B7584". Enter number(s), N)ext, or Q)uit > gpg: no valid OpenPGP data found. gpg: Total number processed: 0 cer@Elesar:~>
Now it finds my keys, but fails to import them:
cer@Elesar:~> gpg2 --keyserver https://keyserver.ubuntu.com --recv-keys 0xB533181C6D8D47D5 gpg: no valid OpenPGP data found. gpg: Total number processed: 0 cer@Elesar:~>
So, all PGP servers I know are broken, which is what I said. I will have to add "or do not exist anymore".
then why persist?
-- Cheers / Saludos,
Carlos E. R.
(from Elesar, using openSUSE Leap 15.4)
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Carlos E. R. wrote:
So, all PGP servers I know are broken, which is what I said.
You did? Well, not being much of a PGP user, I can't add much - maybe look for some new servers? I think the German c't magazine has one, for instance. -- Per Jessen, Zürich (0.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-23 19:12, Per Jessen wrote:
Carlos E. R. wrote:
So, all PGP servers I know are broken, which is what I said.
You did?
Well, not being much of a PGP user, I can't add much - maybe look for some new servers? I think the German c't magazine has one, for instance.
No, it is a known issue. There was an attack on them some years back, filling them up to capacity with garbage data. Data that by design can not be deleted. <https://threatpost.com/pgp-ecosystem-targeted-in-poisoning-attacks/146240/> 5 jul 2019 «PGP Ecosystem Targeted in ‘Poisoning’ Attacks Two researchers are being singled out in what are called PGP poisoning or flood attacks that render the authentication tool unusable for victims. A long-feared attack vector used against Pretty Good Privacy, the framework used to authenticate and keep email messages private, is being exploited for the first time. The attack, which takes aim at keyserver verification directories, makes it impossible for Pretty Good Privacy (PGP) to work properly for those targeted in attacks. Unknown adversaries have singled out two recognized experts in the field of OpenPGP email encryption, Robert Hansen and Daniel Gillmor, in a series of targeted attacks. OpenPGP refers to the standard that uses the cryptographic privacy and authentication program PGP. “In the last week of June 2019 unknown actors deployed a certificate spamming attack against two high-profile contributors in the OpenPGP community… This attack exploited a defect in the OpenPGP protocol itself in order to ‘poison’ [Hansen] and [Gillmor’s] OpenPGP certificates,” wrote Hansen in a technical description of the attacks.» <https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f> <https://www.rossde.com/PGP/pgp_keyserv.html> «NOTE WELL:Many key servers have stopped synchronizing with each other because of hostile attacks. These attacks involve uploading fraudulent public keys and valid public keys with fraudulent signatures. There might even be cause to reject using key servers at all. For details, see SKS Keyserver Network Under Attack. In checking my own public keys on various key servers, I now see unknown signatures. In many cases, the public key of the signer is NOT on the server. The best protection against injury from a fraudulent public keys is to practice what is described in the Web of Trust. After all, few key servers authenticate the public keys uploaded to them. Instead, they accept all uploads. Thus, a user must separately authenticate any public key obtained from a key server.» -> <https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f> SKS Keyserver Network Under Attack So the only thing people can do is share their keys manually, attaching them to email. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
* Carlos E. R. <robin.listas@telefonica.net> [01-23-23 13:23]:
On 2023-01-23 19:12, Per Jessen wrote:
Carlos E. R. wrote:
So, all PGP servers I know are broken, which is what I said.
You did?
Well, not being much of a PGP user, I can't add much - maybe look for some new servers? I think the German c't magazine has one, for instance.
No, it is a known issue. There was an attack on them some years back, filling them up to capacity with garbage data. Data that by design can not be deleted.
<https://threatpost.com/pgp-ecosystem-targeted-in-poisoning-attacks/146240/>
5 jul 2019
«PGP Ecosystem Targeted in ‘Poisoning’ Attacks
Two researchers are being singled out in what are called PGP poisoning or flood attacks that render the authentication tool unusable for victims.
A long-feared attack vector used against Pretty Good Privacy, the framework used to authenticate and keep email messages private, is being exploited for the first time. The attack, which takes aim at keyserver verification directories, makes it impossible for Pretty Good Privacy (PGP) to work properly for those targeted in attacks.
Unknown adversaries have singled out two recognized experts in the field of OpenPGP email encryption, Robert Hansen and Daniel Gillmor, in a series of targeted attacks. OpenPGP refers to the standard that uses the cryptographic privacy and authentication program PGP.
“In the last week of June 2019 unknown actors deployed a certificate spamming attack against two high-profile contributors in the OpenPGP community… This attack exploited a defect in the OpenPGP protocol itself in order to ‘poison’ [Hansen] and [Gillmor’s] OpenPGP certificates,” wrote Hansen in a technical description of the attacks.»
<https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f>
<https://www.rossde.com/PGP/pgp_keyserv.html>
«NOTE WELL:Many key servers have stopped synchronizing with each other because of hostile attacks. These attacks involve uploading fraudulent public keys and valid public keys with fraudulent signatures. There might even be cause to reject using key servers at all. For details, see SKS Keyserver Network Under Attack.
In checking my own public keys on various key servers, I now see unknown signatures. In many cases, the public key of the signer is NOT on the server.
The best protection against injury from a fraudulent public keys is to practice what is described in the Web of Trust. After all, few key servers authenticate the public keys uploaded to them. Instead, they accept all uploads. Thus, a user must separately authenticate any public key obtained from a key server.»
-> <https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f>
SKS Keyserver Network Under Attack
So the only thing people can do is share their keys manually, attaching them to email.
ah, great! more worthless electrons :(
-- Cheers / Saludos,
Carlos E. R.
(from Elesar, using openSUSE Leap 15.4)
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Carlos E. R. wrote:
So the only thing people can do is share their keys manually, attaching them to email.
Okay - but surely not on every email :-) -- Per Jessen, Zürich (0.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-23 19:47, Per Jessen wrote:
Carlos E. R. wrote:
So the only thing people can do is share their keys manually, attaching them to email.
Okay - but surely not on every email :-)
Me, only on request. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
Am 23.01.23 um 19:47 schrieb Per Jessen:
Carlos E. R. wrote:
So the only thing people can do is share their keys manually, attaching them to email.
Okay - but surely not on every email :-)
well in thunderbird 102.x is a option that do exactly this until the receifer did anwer with encrypt mails. "sign automatically my not encrypt mails" + "put key to signed mails" simoN
-- www.becherer.de ----------------------------------------------- - Das ist die vorlaeufig endgueltige Version! - Herbert C. Maier Dipl.-Ing. (FH) -----------------------------------------------
On 2023-01-23 19:56, Simon Becherer wrote:
Am 23.01.23 um 19:47 schrieb Per Jessen:
Carlos E. R. wrote:
So the only thing people can do is share their keys manually, attaching them to email.
Okay - but surely not on every email :-)
well in thunderbird 102.x is a option that do exactly this until the receifer did anwer with encrypt mails.
"sign automatically my not encrypt mails" + "put key to signed mails"
Yes. And it may even be the default. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
Simon Becherer wrote:
Am 23.01.23 um 19:47 schrieb Per Jessen:
Carlos E. R. wrote:
So the only thing people can do is share their keys manually, attaching them to email.
Okay - but surely not on every email :-)
well in thunderbird 102.x is a option that do exactly this until the receifer did anwer with encrypt mails.
"sign automatically my not encrypt mails" + "put key to signed mails"
Thanks for that - interesting option, albeit it could easily end up being quite annoying I would say. Btw, your pgp signature didn't work either - the issue to seems to be that it was sent as an attachment. -- Per Jessen, Zürich (0.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-23 20:03, Per Jessen wrote:
Simon Becherer wrote:
Am 23.01.23 um 19:47 schrieb Per Jessen:
Carlos E. R. wrote:
So the only thing people can do is share their keys manually, attaching them to email.
Okay - but surely not on every email :-)
well in thunderbird 102.x is a option that do exactly this until the receifer did anwer with encrypt mails.
"sign automatically my not encrypt mails" + "put key to signed mails"
Thanks for that - interesting option, albeit it could easily end up being quite annoying I would say.
Btw, your pgp signature didn't work either - the issue to seems to be that it was sent as an attachment.
Yes. AFAI, intentionally, the Thunderbird people decided to not support inline signatures when they dropped Enigmail and changed to internal code. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
On Mon, 23 Jan 2023 19:47:58 +0100 Per Jessen <per@jessen.ch> wrote:
Carlos E. R. wrote:
So the only thing people can do is share their keys manually, attaching them to email.
Okay - but surely not on every email :-)
Didn't this thread start because somebody was doing exactly that? In any case though, if I impersonate Carlos then sign the message with a key of my own (which I haven't publically acknowledged) and send the public key with the message, doesn't that defeat the whole point of signing messages? You have to use some other channel to distribute the keys - e.g. a web of trust.
On 2023-01-23 22:11, Dave Howorth wrote:
On Mon, 23 Jan 2023 19:47:58 +0100 Per Jessen <> wrote:
Carlos E. R. wrote:
So the only thing people can do is share their keys manually, attaching them to email.
Okay - but surely not on every email :-)
Didn't this thread start because somebody was doing exactly that?
In any case though, if I impersonate Carlos then sign the message with a key of my own (which I haven't publically acknowledged) and send the public key with the message, doesn't that defeat the whole point of signing messages?
Yes. In my case, though, then I'd say that my key is the same one for over a decade, while the new "forged" key is recent. I could be believed or not.
You have to use some other channel to distribute the keys - e.g. a web of trust.
No, it works in parallel, when PGP is involved. You have to sign the keys of the people that you personally meet, and upload this data to the keyservers for others to import. <https://en.wikipedia.org/wiki/Web_of_trust> Problem is that the servers are dead. PGP is dying. The other method is using certificates issued by an authority (S/MIME, PKCS). But the resulting signatures are quite bigger than PGP (I just did a quick test, and my signature for a blank email is 7KB). <https://en.wikipedia.org/wiki/S/MIME> <https://en.wikipedia.org/wiki/PKCS> -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [01-23-23 17:53]:
On 2023-01-23 22:11, Dave Howorth wrote:
On Mon, 23 Jan 2023 19:47:58 +0100 Per Jessen <> wrote:
Carlos E. R. wrote:
So the only thing people can do is share their keys manually, attaching them to email.
Okay - but surely not on every email :-)
Didn't this thread start because somebody was doing exactly that?
In any case though, if I impersonate Carlos then sign the message with a key of my own (which I haven't publically acknowledged) and send the public key with the message, doesn't that defeat the whole point of signing messages?
Yes.
In my case, though, then I'd say that my key is the same one for over a decade, while the new "forged" key is recent. I could be believed or not.
You have to use some other channel to distribute the keys - e.g. a web of trust.
No, it works in parallel, when PGP is involved. You have to sign the keys of the people that you personally meet, and upload this data to the keyservers for others to import.
<https://en.wikipedia.org/wiki/Web_of_trust>
Problem is that the servers are dead. PGP is dying.
The other method is using certificates issued by an authority (S/MIME, PKCS). But the resulting signatures are quite bigger than PGP (I just did a quick test, and my signature for a blank email is 7KB).
<https://en.wikipedia.org/wiki/S/MIME> <https://en.wikipedia.org/wiki/PKCS>
-- Cheers / Saludos,
Carlos E. R. (from 15.4 x86_64 at Telcontar)
another reason not to utilize certificates for such trivial matters as list traffic. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
* Carlos E. R. <robin.listas@telefonica.net> [01-23-23 06:36]:
On 2023-01-23 11:16, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-18 23:08, Patrick Shanahan wrote:
[-- Error: unable to create PGP subprocess! --]
you might do something about that unenforcable signature, Marc
Works fine here.
Doesn't work here - I dare say it depends on whether local support has been set up.
Patrick is using Mutt, which is ancient software, and I am using Thunderbird, which uses a very new implementation; although Marc uses an old version, I don't know if it is old enough to use enigmail implementation.
please define "ancient software". yes, mutt is > 27 years of age but my last update: Build Date : Mon 05 Dec 2022 12:06:19 PM EST ie: it is constantly improving. so what if it doesn't work with particular worthless incantations. you constantly have difficulties with your choice of thunderbird as you frequently relate here. when was the last time I expressed difficulties with my usage of mutt mail client?
Alpine has a problem with Thunderbird: alpine uses inline pgp, which Th does not support, and uses attached signature, which alpine does not support.
-- Cheers / Saludos,
Carlos E. R. (from 15.4 x86_64 at Telcontar)
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Paka, et al -- ...and then Patrick Shanahan said... % * Carlos E. R. <robin.listas@telefonica.net> [01-23-23 06:36]: % > % > Patrick is using Mutt, which is ancient software, and I am using ... % % please define "ancient software". yes, mutt is > 27 years of age but my % last update: Build Date : Mon 05 Dec 2022 12:06:19 PM EST % ie: it is constantly improving. [snip] +1 ... or maybe +10 or +100 :-) UNIX is ancient, too; I'd put elm and PINE there. Linux is by now fairly long in the tooth, and I'd put mutt in that range. So, yeah, maybe ancient ... but *good*. HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt
On 2023-01-23 20:51, David T-G wrote:
Paka, et al --
...and then Patrick Shanahan said... % * Carlos E. R. <> [01-23-23 06:36]: % > % > Patrick is using Mutt, which is ancient software, and I am using ... % % please define "ancient software". yes, mutt is > 27 years of age but my % last update: Build Date : Mon 05 Dec 2022 12:06:19 PM EST % ie: it is constantly improving. [snip]
+1 ... or maybe +10 or +100 :-)
UNIX is ancient, too; I'd put elm and PINE there. Linux is by now fairly long in the tooth, and I'd put mutt in that range. So, yeah, maybe ancient ... but *good*.
I didn't say otherwise... only that it is ancient ;-) But it's support of PGP may not be working or may not exist. Similar to Alpine's. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
* Carlos E. R. <robin.listas@telefonica.net> [01-23-23 14:55]:
On 2023-01-23 20:51, David T-G wrote:
Paka, et al --
...and then Patrick Shanahan said... % * Carlos E. R. <> [01-23-23 06:36]: % > % > Patrick is using Mutt, which is ancient software, and I am using ... % % please define "ancient software". yes, mutt is > 27 years of age but my % last update: Build Date : Mon 05 Dec 2022 12:06:19 PM EST % ie: it is constantly improving. [snip]
+1 ... or maybe +10 or +100 :-)
UNIX is ancient, too; I'd put elm and PINE there. Linux is by now fairly long in the tooth, and I'd put mutt in that range. So, yeah, maybe ancient ... but *good*.
I didn't say otherwise... only that it is ancient ;-)
But it's support of PGP may not be working or may not exist. Similar to Alpine's.
that I cannot be bothered to configure mutt for gpg/pgp, is not an indication in any way that the ancient mutt cannot handle it. it says that I DO NOT CARE. for the most part, I find it a waste of resources.
-- Cheers / Saludos,
Carlos E. R.
(from Elesar, using openSUSE Leap 15.4)
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 2023-01-23 21:06, Patrick Shanahan wrote:
* Carlos E. R. <> [01-23-23 14:55]:
On 2023-01-23 20:51, David T-G wrote:
Paka, et al --
...and then Patrick Shanahan said... % * Carlos E. R. <> [01-23-23 06:36]: % > % > Patrick is using Mutt, which is ancient software, and I am using ... % % please define "ancient software". yes, mutt is > 27 years of age but my % last update: Build Date : Mon 05 Dec 2022 12:06:19 PM EST % ie: it is constantly improving. [snip]
+1 ... or maybe +10 or +100 :-)
UNIX is ancient, too; I'd put elm and PINE there. Linux is by now fairly long in the tooth, and I'd put mutt in that range. So, yeah, maybe ancient ... but *good*.
I didn't say otherwise... only that it is ancient ;-)
But it's support of PGP may not be working or may not exist. Similar to Alpine's.
that I cannot be bothered to configure mutt for gpg/pgp, is not an indication in any way that the ancient mutt cannot handle it. it says that I DO NOT CARE. for the most part, I find it a waste of resources.
Fine, but then do not complain when we use PGP and your Mutt displays garbage. That's not our problem, it is yours. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [01-23-23 17:56]:
On 2023-01-23 21:06, Patrick Shanahan wrote:
* Carlos E. R. <> [01-23-23 14:55]:
On 2023-01-23 20:51, David T-G wrote:
Paka, et al --
...and then Patrick Shanahan said... % * Carlos E. R. <> [01-23-23 06:36]: % > % > Patrick is using Mutt, which is ancient software, and I am using ... % % please define "ancient software". yes, mutt is > 27 years of age but my % last update: Build Date : Mon 05 Dec 2022 12:06:19 PM EST % ie: it is constantly improving. [snip]
+1 ... or maybe +10 or +100 :-)
UNIX is ancient, too; I'd put elm and PINE there. Linux is by now fairly long in the tooth, and I'd put mutt in that range. So, yeah, maybe ancient ... but *good*.
I didn't say otherwise... only that it is ancient ;-)
But it's support of PGP may not be working or may not exist. Similar to Alpine's.
that I cannot be bothered to configure mutt for gpg/pgp, is not an indication in any way that the ancient mutt cannot handle it. it says that I DO NOT CARE. for the most part, I find it a waste of resources.
Fine, but then do not complain when we use PGP and your Mutt displays garbage. That's not our problem, it is yours.
-- Cheers / Saludos,
Carlos E. R. (from 15.4 x86_64 at Telcontar)
you took it as I was "complaining" about the gpg/pgp sig which was not the case. I was commenting about the uninforcable signature semi-legal statements. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Carlos E. R. wrote:
On 2023-01-23 21:06, Patrick Shanahan wrote:
that I cannot be bothered to configure mutt for gpg/pgp, is not an indication in any way that the ancient mutt cannot handle it. it says that I DO NOT CARE. for the most part, I find it a waste of resources.
Fine, but then do not complain when we use PGP and your Mutt displays garbage. That's not our problem, it is yours.
Nonetheless _caused_ by those who are using a dying system (according to yourself). When it works, it still requires effort on behalf of the user to validate the information, so it does seem a bit pointless on a mailing list. -- Per Jessen, Zürich (0.2°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Am 24.01.23 um 09:36 schrieb Per Jessen:
Carlos E. R. wrote:
On 2023-01-23 21:06, Patrick Shanahan wrote:
Nonetheless _caused_ by those who are using a dying system (according to yourself).
"dying": here a server who uses a working technology for keys (describtion in german only, maybe you have to use some translation utility) in short its a keyserver not made with the software SKS its written with the software Hagrid (language "rust") people envolved from known software: Enigmail, Openkeychain und Sequoia. they validate the keys/the upload. and as i read you are able to delete keys there. (because of the eu law) -> the informations i gave here are not validated by me. its only a short english describtion what i have read there. https://keys.openpgp.org/about/news#2019-06-12-launch https://keys.openpgp.org/ https://keys.openpgp.org/about/usage insert this as keyserver: hkps://keys.openpgp.org simoN -- www.becherer.de ----------------------------------------------- - Das ist die vorlaeufig endgueltige Version! - Herbert C. Maier Dipl.-Ing. (FH) -----------------------------------------------
Am 24.01.23 um 10:29 schrieb Simon Becherer:
insert this as keyserver:
hkps://keys.openpgp.org
simoN
Some more servers (working will find here:) https://www.liquidweb.com/kb/is-gpg-still-useful-in-todays-insecure-world/ -- www.becherer.de ----------------------------------------------- - Das ist die vorlaeufig endgueltige Version! - Herbert C. Maier Dipl.-Ing. (FH) -----------------------------------------------
On 1/24/23 03:54, Simon Becherer wrote:
Am 24.01.23 um 10:29 schrieb Simon Becherer:
insert this as keyserver:
hkps://keys.openpgp.org
simoN
Some more servers (working will find here:) https://www.liquidweb.com/kb/is-gpg-still-useful-in-todays-insecure-world/
I get this little thing in Firefox that says "OpenPGP" with some messages. When I click on it [ which is "never" ] I get the attached message. I ignore it. There is a 99.9+% chance that I am just going to delete your messages after it's read [ if I even read it ]. There is a < 0.1% chance that I will think it important enough to keep. What should I care if you have this [ supposedly ] secure proof that you are you and the sender of the message. OK, that's my $0.02US worth of my opinion about this thread which will be ignored from now on. -- Women and cats will do just as they please. Men and dogs should just get used to the idea.
On 2023-01-24 10:29, Simon Becherer wrote:
Am 24.01.23 um 09:36 schrieb Per Jessen:
Carlos E. R. wrote:
On 2023-01-23 21:06, Patrick Shanahan wrote:
Nonetheless _caused_ by those who are using a dying system (according to yourself).
No.
"dying":
here a server who uses a working technology for keys (describtion in german only, maybe you have to use some translation utility)
in short its a keyserver not made with the software SKS its written with the software Hagrid (language "rust") people envolved from known software: Enigmail, Openkeychain und Sequoia. they validate the keys/the upload. and as i read you are able to delete keys there. (because of the eu law) -> the informations i gave here are not validated by me. its only a short english describtion what i have read there.
https://keys.openpgp.org/about/news#2019-06-12-launch https://keys.openpgp.org/ https://keys.openpgp.org/about/usage
insert this as keyserver:
hkps://keys.openpgp.org
cer@Telcontar:~> gpg --keyserver hkps://keys.openpgp.org --search-keys 0xF62B7584 gpg: data source: https://keys.openpgp.org:443 gpg: key "0xF62B7584" not found on keyserver gpg: keyserver search failed: Not found cer@Telcontar:~> gpg --keyserver hkps://keys.openpgp.org --recv-keys 0x30A79B3E30ED0012 gpg: keyserver receive failed: No data cer@Telcontar:~> Unless they are isolated from the network of keyservers and I have to upload my key there. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-01-24 10:29, Simon Becherer wrote:
Am 24.01.23 um 09:36 schrieb Per Jessen:
Carlos E. R. wrote:
https://keys.openpgp.org/about/news#2019-06-12-launch https://keys.openpgp.org/ https://keys.openpgp.org/about/usage
insert this as keyserver:
hkps://keys.openpgp.org
I just checked the config editor of Thunderbird. temp.openpgp.keyserver = vks://keys.openpgp.org -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-01-23 20:51, David T-G wrote:
Paka, et al --
...and then Patrick Shanahan said... % * Carlos E. R. <> [01-23-23 06:36]: % > % > Patrick is using Mutt, which is ancient software, and I am using ... % % please define "ancient software". yes, mutt is > 27 years of age but my % last update: Build Date : Mon 05 Dec 2022 12:06:19 PM EST % ie: it is constantly improving. [snip]
+1 ... or maybe +10 or +100 :-)
UNIX is ancient, too; I'd put elm and PINE there. Linux is by now fairly long in the tooth, and I'd put mutt in that range. So, yeah, maybe ancient ... but *good*.
I didn't say otherwise... only that it is ancient ;-)
But it's support of PGP may not be working or may not exist. Similar to Alpine's.
Yesterday you posted two messages from Alpine, both with PGP signatures. They worked fine, although I can't be bothered to check the signatures. -- Per Jessen, Zürich (0.2°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-01-24 09:30, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-23 20:51, David T-G wrote:
Paka, et al -- ...and then Patrick Shanahan said... % * Carlos E. R. <> [01-23-23 06:36]: % > % > Patrick is using Mutt, which is ancient software, and I am using ... % % please define "ancient software". yes, mutt is > 27 years of age but my % last update: Build Date : Mon 05 Dec 2022 12:06:19 PM EST % ie: it is constantly improving. [snip]
+1 ... or maybe +10 or +100 :-)
UNIX is ancient, too; I'd put elm and PINE there. Linux is by now fairly long in the tooth, and I'd put mutt in that range. So, yeah, maybe ancient ... but *good*.
I didn't say otherwise... only that it is ancient ;-)
But it's support of PGP may not be working or may not exist. Similar to Alpine's.
Yesterday you posted two messages from Alpine, both with PGP signatures. They worked fine, although I can't be bothered to check the signatures.
Exactly, your knode, same as my alpine, only work with inline signatures, but not with s/mime, attached signatures. Ancient software. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-01-23 11:16, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-18 23:08, Patrick Shanahan wrote:
[-- Error: unable to create PGP subprocess! --]
you might do something about that unenforcable signature, Marc
Works fine here.
Doesn't work here - I dare say it depends on whether local support has been set up.
Patrick is using Mutt, which is ancient software, and I am using Thunderbird, which uses a very new implementation; although Marc uses an old version, I don't know if it is old enough to use enigmail implementation. Carlos, all - FWIW I am using version 91.11.0 (64-bit) of Thunderbird which I think is fairly new. I used to use enigmail as an add-on, but now TB comes with OpenPGP support built in, so I no longer need/use enigmail. As was suggested, I am no longer sending my public key as
On 1/23/23 03:33, Carlos E. R. wrote: part of the attachment for my signature signing. To bad TB does not support custom signatures on a per receiver basis, I will try to remember to remove my "artistic" part of my signature when sending emails to this group, since I received complaints about it, but not going to guarantee I can always remember to do so. Marc... --
On 2023-01-23 18:07, Marc Chamberlin wrote:
On 1/23/23 03:33, Carlos E. R. wrote:
On 2023-01-23 11:16, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-01-18 23:08, Patrick Shanahan wrote:
[-- Error: unable to create PGP subprocess! --]
you might do something about that unenforcable signature, Marc
Works fine here.
Doesn't work here - I dare say it depends on whether local support has been set up.
Patrick is using Mutt, which is ancient software, and I am using Thunderbird, which uses a very new implementation; although Marc uses an old version, I don't know if it is old enough to use enigmail implementation. Carlos, all - FWIW I am using version 91.11.0 (64-bit) of Thunderbird which I think is fairly new.
We are at 102.6 :-)
I used to use enigmail as an add-on, but now TB comes with OpenPGP support built in, so I no longer need/use enigmail. As was suggested, I am no longer sending my public key as part of the attachment for my signature signing. To bad TB does not support custom signatures on a per receiver basis, I will try to remember to remove my "artistic" part of my signature when sending emails to this group, since I received complaints about it, but not going to guarantee I can always remember to do so.
That can be configurable with "identities". The trouble is how to select automatically a different identity for mail list. I don't remember how to do that. maybe: https://support.mozilla.org/en-US/questions/1340827 -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
Marc Chamberlin composed on 2023-01-18 13:58 (UTC-0800):
This is probably the wrong group to ask, but I will start here and then follow any pointers to where I should ask my question...
I am running Leap 15.4 with the KDE/Plasma desktop. There is a bug, reported and fixed/resolved - https://bugs.kde.org/show_bug.cgi?id=453280 which is bugging me now. This was resolved last year (June) and I am wondering when this fix will show up in an update for my system? It is annoying to have to log out and log back in whenever this problem shows up on my systems, so I thought I would ask and hopefully get an update soon that fixes it.
Just guessing, I don't think you'll ever see a fix in Leap, unless 15.5 gets a bump up from the Plasma 5.24.4 version current in 15.4 and 15.5 - unless you report an openSUSE bug referencing that upstream bug that asks for a backport of the fix for that bug that landed in 5.24.6. What you could do is upgrade your own installation to TW's 5.26.5 by saving http://download.opensuse.org/repositories/KDE%3A/Frameworks5/openSUSE_Leap_1... to /etc/zypp/repos.d/ and doing a vendor change of plasma5-desktop with YaST or Zypper. Or use opi, which will setup the new repo in the process of upgrading. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 1/18/23 14:28, Felix Miata wrote:
Marc Chamberlin composed on 2023-01-18 13:58 (UTC-0800):
This is probably the wrong group to ask, but I will start here and then follow any pointers to where I should ask my question...
I am running Leap 15.4 with the KDE/Plasma desktop. There is a bug, reported and fixed/resolved - https://bugs.kde.org/show_bug.cgi?id=453280 which is bugging me now. This was resolved last year (June) and I am wondering when this fix will show up in an update for my system? It is annoying to have to log out and log back in whenever this problem shows up on my systems, so I thought I would ask and hopefully get an update soon that fixes it.
Just guessing, I don't think you'll ever see a fix in Leap, unless 15.5 gets a bump up from the Plasma 5.24.4 version current in 15.4 and 15.5 - unless you report an openSUSE bug referencing that upstream bug that asks for a backport of the fix for that bug that landed in 5.24.6.
What you could do is upgrade your own installation to TW's 5.26.5 by saving http://download.opensuse.org/repositories/KDE%3A/Frameworks5/openSUSE_Leap_1... to /etc/zypp/repos.d/ and doing a vendor change of plasma5-desktop with YaST or Zypper. Or use opi, which will setup the new repo in the process of upgrading.
Thanks Felix for your suggestions. Although I am not sure I grok all of your comments and their implications, I am reluctant to switch to TW because of the rate of change that occurs is too high for my comfort level of maintaining it on my systems. For now I will try Patrick's suggestion and install kscreen5 to see if that will fix it. Marc...
On 2023-01-18 22:58, Marc Chamberlin wrote:
This is probably the wrong group to ask, but I will start here and then follow any pointers to where I should ask my question...
I am running Leap 15.4 with the KDE/Plasma desktop. There is a bug, reported and fixed/resolved - https://bugs.kde.org/show_bug.cgi?id=453280 which is bugging me now. This was resolved last year (June) and I am wondering when this fix will show up in an update for my system? It is annoying to have to log out and log back in whenever this problem shows up on my systems, so I thought I would ask and hopefully get an update soon that fixes it.
Then you should create an openSUSE Bugzilla with more or less the same text as here, except the first paragraph :-) Maybe include a description of the problem, maybe taken from the upstream report, to save them time, not needing to open a link initially. On another matter, maybe you could configure your Thunderbird to not include the PGP key itself everytime, and only send it when someone requests it. Just leave the PGP signature. That saves 2.4 KB. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
participants (9)
-
Bill Walsh -
Carlos E. R. -
Dave Howorth -
David T-G -
Felix Miata -
Marc Chamberlin -
Patrick Shanahan -
Per Jessen -
Simon Becherer