All of lore.kernel.org
 help / color / mirror / Atom feed
From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] mail server problems
Date: Wed, 02 Feb 2011 20:52:28 +0100	[thread overview]
Message-ID: <1296676348.2938.10.camel@tesla.lan> (raw)
In-Reply-To: <4D4960E2.9020900@tresys.com>

On Wed, 02/02/2011 at 08.49 -0500, Christopher J. PeBenito wrote:
> It appears there were some problems with the refpolicy list server.  It 
> should be fixed now, but there may have been some queued messages that 
> were rejected.  They should go through now if you resend them.

Hello Christopher,

thanks for the note.

You should also be aware that the list server does not carry out any
sanity check on the timestamp of messages sent to the list.

So, one could in theory send a message dated in the past or in the
future (even for malicious reasons) and the list server would just
"drink it".

The list server should probably regenerate the timestamp locally and
never accept the timestamp from the sender.

Best regards,

Guido Trentalancia

      reply	other threads:[~2011-02-02 19:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 13:49 [refpolicy] mail server problems Christopher J. PeBenito
2011-02-02 19:52 ` Guido Trentalancia [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1296676348.2938.10.camel@tesla.lan \
    --to=guido@trentalancia.com \
    --cc=refpolicy@oss.tresys.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.