From: Mike Fedyk <mfedyk@matchmail.com>
To: John Jasen <jjasen1@umbc.edu>,
Mike Galbraith <mikeg@wen-online.de>,
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 12:02:05 -0800 [thread overview]
Message-ID: <20020319200205.GW2254@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10203191009290.5694-100000@mikeg.wen-online.de> <Pine.SGI.4.31L.02.0203190915250.7550126-100000@irix2.gl.umbc.edu> <20020319181130.GQ2254@matchmail.com> <20020319154734.GM470@turbolinux.com>
On Tue, Mar 19, 2002 at 08:47:34AM -0700, Andreas Dilger wrote:
> On Mar 19, 2002 10:11 -0800, 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...
>
> I haven't been following the whole thread, but it is _possible_ that the
> email data was written to the end of a data block which was later re-used
> for a file exported via SMB. Depending on how the SMB code works, is it
> possible that it is sending a whole block of data to the client and/or
> not zeroing out new blocks?
>
> Of course (not having looked at the original tcpdump output), is it
> possible that the email was captured by tcpdump because it arrived on
> the host via the network?
>
I'm still waiting to find out what computer 10.0.0.101 is for MikeG...
But, he's not running samba or smbfs, and the email was encoded within a smb
packet...
next prev parent reply other threads:[~2002-03-19 20:01 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 [this message]
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
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=20020319200205.GW2254@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=jjasen1@umbc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
--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 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.