From: Mike Galbraith <mikeg@wen-online.de>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: John Jasen <jjasen1@umbc.edu>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: reading your email via tcpdump
Date: Tue, 19 Mar 2002 20:16:40 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.10.10203192012410.606-100000@mikeg.wen-online.de> (raw)
In-Reply-To: <20020319185225.GT2254@matchmail.com>
On Tue, 19 Mar 2002, Mike Fedyk wrote:
> On Tue, Mar 19, 2002 at 07:56:27PM +0100, Mike Galbraith wrote:
> > On Tue, 19 Mar 2002, Mike Fedyk wrote:
> > > That's not the problem part of the tcpdump output. The problem is that part
> > > of an email previously read on the linux box (with no samba runing. (also,
> > > no smbfs MikeG?)) showed up in the tcpdump output...
> >
> > Yes. That's exactly what worried me. (no clue as to security issues)
>
> What computer is 10.0.0.101?
My son's win98 box. I'm ~positive that the message did _not_ propagate
to my son's box and come back via net.. local data exposed probably via
page return.
-Mike
prev parent reply other threads:[~2002-03-20 5:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 17:20 reading your email via tcpdump Mike Galbraith
2002-03-19 11:39 ` Denis Vlasenko
2002-03-19 9:19 ` Mike Galbraith
2002-03-19 14:20 ` John Jasen
2002-03-19 14:58 ` Mike Galbraith
2002-03-19 18:11 ` Mike Fedyk
2002-03-19 15:47 ` Andreas Dilger
2002-03-19 20:02 ` Mike Fedyk
2002-03-19 20:19 ` Richard B. Johnson
2002-03-20 0:34 ` Alan Cox
2002-03-20 1:00 ` Petko Manolov
2002-03-19 21:04 ` Urban Widmark
2002-03-20 7:46 ` Mike Galbraith
2002-03-19 18:56 ` Mike Galbraith
2002-03-19 18:52 ` Mike Fedyk
2002-03-19 19:16 ` Mike Galbraith [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=Pine.LNX.4.10.10203192012410.606-100000@mikeg.wen-online.de \
--to=mikeg@wen-online.de \
--cc=jjasen1@umbc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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;
as well as URLs for NNTP newsgroup(s).