From: bo0od <bo0od@riseup.net>
To: "Bonface Munyoki K." <me@bonfacemunyoki.com>
Cc: 47660@debbugs.gnu.org
Subject: bug#47660: Add link to the ticket when someone reply
Date: Thu, 15 Apr 2021 17:00:03 +0000 [thread overview]
Message-ID: <be8288f6-f500-3090-4612-975568d47882@riseup.net> (raw)
In-Reply-To: <86im4nmxrs.fsf@bonfacemunyoki.com>
To be honest i find this bad thing to use emails to do anything rather
than online registration and not necessary stuff (means being
encrypted,manipulated.. just not something important)
Email sucks due to:
* Messages are not encrypted by default which mean it need an extra tool
to do it and commonly used is GPG/PGP + it needs tool to implement this
encryption on the messages which mean mail reader/client most commonly
one used is thunderbird/icedove <- This method having tremendous
security issues check for example:
- https://efail.de/
- https://www.whonix.org/wiki/OpenPGP#Issues_with_PGP
* Most of the time (not always) heavily rely on clearnet which mean
issues of TLS/DNS which needs to be hardened otherwise they are exist by
names but does nothing.
..This is out of scope to discuss this in details, I just want to see
the bug URL linked to the bottom of the email i receive thats it.
Bonface Munyoki K.:
> bo0od <bo0od@riseup.net> writes:
>
>> what are you talking about? who uses PGP/GPG for
>> a public ticket tracking system?...
>>
>
> I do. I sign my e-mails as a guarantee to my
> recipients that what you get is truly from
> me. That plus my mail client makes that-- signing
> emails-- way easy to do. I also sign all my
> commits, even on the major platforms. FWIW, even
> on GH, and GL, you could sign your emails when
> replying to an email, thereby having the
> recipients on the Cc see your pgp/ gpg signature,
> while GL/ GH scrapes it off when displaying it's
> contents. However, there are people who sign email
> inline. Here's one such example:
> https://github.com/alezost/guix.el/issues/39
>
> PS: If you use gnus from Emacs, you should read:
> https://www.gnu.org/software/emacs/manual/html_node/message/Signing-and-encryption.html#Signing-and-encryption
> In my Emacs, I have:
>
> --8<---------------cut here---------------start------------->8---
> (use-package mm-encode
> :config (setq mm-encrypt-option 'guided) (setq
> mm-sign-option 'guided))
>
> (use-package mml-sec
> :config (setq mml-secure-openpgp-encrypt-to-self
> t) (setq mml-secure-openpgp-sign-with-sender t)
> (setq mml-secure-smime-encrypt-to-self t) (setq
> mml-secure-smime-sign-with-sender t))
>
> (use-package epa-file
> :config (setq
> epa-file-cache-passphrase-for-symmetric-encryption
> nil))
> --8<---------------cut here---------------end--------------->8---
>
>
>> gitlab,github,trac...etc all giving the ticket
>> URL on the bottom of the message nothing with
>> magic im suggesting here.
>>
>> Maxime Devos:
>>> On Fri, 2021-04-09 at 20:44 +0000, bo0od wrote:
>>>> This work or i search for it also work, But we
>>>> are talking making things much easier and its
>>>> possible through providing the link directly
>>>> to the ticket in bottom, I believe this
>>>> practice followed by all major ticketing
>>>> systems,platforms,projects.. So i dont
>>>> understand whats the big deal having it here
>>>> as well.
>>> Mangling e-mails can cause all kinds of
>>> trouble. It would mess up git patches, break
>>> messages signed with PGP or S/MIME (does anyone
>>> here actually use S/MIME?), makes some headers
>>> used for spam detection (and more generally,
>>> detecting forged mails) invalid, which will
>>> lead to messages from the mailing list and
>>> @debbugs.gnu.org be marked as spam ...
>>> Greetings, Maxime.
>>>
>>
>>
>>
>>
>
next prev parent reply other threads:[~2021-04-15 19:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-08 17:38 bug#47660: Add link to the ticket when someone reply bo0od
2021-04-08 18:45 ` Leo Famulari
2021-04-09 20:44 ` bo0od
2021-04-10 10:45 ` Maxime Devos
2021-04-10 14:20 ` bo0od
2021-04-10 16:44 ` Maxime Devos
2021-04-10 20:13 ` bo0od
2021-04-15 14:24 ` Bonface Munyoki K.
2021-04-15 17:00 ` bo0od [this message]
2021-04-15 17:51 ` Maxime Devos
2021-04-16 2:38 ` bo0od
2022-03-18 2:56 ` Maxim Cournoyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be8288f6-f500-3090-4612-975568d47882@riseup.net \
--to=bo0od@riseup.net \
--cc=47660@debbugs.gnu.org \
--cc=me@bonfacemunyoki.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).