From: Dmitry Alexandrov <dag@gnui.org>
To: Trevor Lee <begleybrothers@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [offtopic] Funny footer (was: Replacing Yocto with Guix kernel image builds: best practices)
Date: Sun, 17 May 2020 16:08:53 +0300 [thread overview]
Message-ID: <ftby1zfe.dag@gnui.org> (raw)
In-Reply-To: <CAJsH2Qm88r9_pu-YLA9hmWb+NjtovHpnS_PDxGoUi=zu67s4Yw@mail.gmail.com> (Trevor Lee's message of "Sun, 17 May 2020 21:41:00 +1000")
[-- Attachment #1: Type: text/plain, Size: 2769 bytes --]
My apologies to Guix devs for offtopic (I hope adding an appropriate tag to subject is enough not to disturb those who do not want to be disturbed), but I could not pass this by:
Trevor Lee <begleybrothers@gmail.com> wrote:
> 1. *The content of this email is confidential and intended for the recipient specified in message only.
Nope, youʼve sent it to a public mailing list. ;-)
And even if put this mistake aside:
> It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender.
By whom? Is there anyone, who is capable of ‘strictly forbidding’ me (or anyone else) to do anything? I would suggest you to revise the wording.
> If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.*
While this is undoubtedly formulated better, it contradicts with the normal workflow of most people: they could either reply to the letter (often citing the enough context) and store it in their archive forever along with their reply, or trash it.
> 2. *This message has been sent as a part of discussion between Begley Brothers Inc. and the addressee whose name is specified above. Should you receive this message by mistake, we would be most grateful if you informed us that the message has been sent to you. In this case, we also ask that you delete this message from your mailbox, and do not forward it or any part of it to anyone else. Thank you for your cooperation and understanding.*
Are not you repeating yourself?
> 3. *Begley Brothers Inc. puts the security of the client at a high priority. Therefore, we have put efforts into ensuring that the message is error and virus-free. Unfortunately, full security of the email cannot be ensured as, despite our efforts, the data included in emails could be infected, intercepted, or corrupted.
Sure, perfect secrecy / security cannot be achieved. But, for instance, signing and encrypting your mail sufficiently lower the chances that it would be tampered with and read by adversary third party respectively.
Unfortunately, you neither sign your mail, nor I can find your key to send you an encrypted one: it is not published neither at open keyserver network (for now represented by keyserver.ubuntu.com), neither at proprietary keys.openpgp.org. And gmail.com, of course, does not provide webkey-directory, let aside DANE.
> Therefore, the recipient should check the email for threats with proper software, as the sender does not accept liability for any damage inflicted by viewing the content of this email.*
It seems, that you have really decided to scare all your clients off. :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-05-17 13:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 11:41 Replacing Yocto with Guix kernel image builds: best practices Trevor Lee
2020-05-17 13:08 ` Dmitry Alexandrov [this message]
2020-05-17 16:59 ` [offtopic] Funny footer (was: Replacing Yocto with Guix kernel image builds: best practices) Josh Marshall
2020-05-17 21:03 ` Trevor Lee
2020-05-17 13:20 ` Replacing Yocto with Guix kernel image builds: best practices Efraim Flashner
2020-05-17 21:23 ` Begley Brothers Inc
2020-05-18 6:35 ` Efraim Flashner
2020-05-19 6:28 ` Begley Brothers Inc
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=ftby1zfe.dag@gnui.org \
--to=dag@gnui.org \
--cc=begleybrothers@gmail.com \
--cc=guix-devel@gnu.org \
/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).