mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthias Andree <matthias.andree@gmx.de>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: HEADS UP lk-changelog/shortlog: security announcement
Date: Sun, 31 Aug 2003 16:33:59 +0200	[thread overview]
Message-ID: <20030831143359.GD30252@merlin.emma.line.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anyone who uses lk-changelog.pl or shortlog
(YES THIS COMPRISES YOU, MARCELO ;-) 
with these option combinations:

- --mode=terse AND NOT --noobfuscate

- --mode=oneline AND NOT --noobfuscate

please be aware that address obfuscation of unknown addresses does not
work (I'll consider that an information leak given that addresses and
logs are web accessible through archives and are actually harvested by
those saboteurs that call themselves direct advertisers), so you may get
lines like:

  o example change log entry (user@example.org)

Rather than

  o example change log entry (user:example.org)

The issue was fixed in 0.166; 0.167 is the latest release version.

Get it from:

BK:  bk://129.217.163.1   (NO trailing slash, bkd -xcd there!)

Once Linus pulls these changes, it will also become available at the

official repository: bk://kernel.bkbits.net/torvalds/tools/

WWW: http://mandree.home.pages.de/linux/kernel/
this site carries releases and GnuPG signatures

(Yes, the GPG signing key has changed recently,
the days of PGP 2.x are passing...)

- -- 
Matthias Andree

Encrypt your mail: my GnuPG key ID is 0x052E7D95
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/UgdOvmGDOQUufZURAkqTAJ9PlcQHCeNcC0CbM6fnEzIub6l1RwCfV3Jn
1cyDzwKTReYEIwEyxtMsjPM=
=e3ZP
-----END PGP SIGNATURE-----

                 reply	other threads:[~2003-08-31 14:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030831143359.GD30252@merlin.emma.line.org \
    --to=matthias.andree@gmx.de \
    --cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®