[4026] in testers
Re: xss not ready for prime time
daemon@ATHENA.MIT.EDU (Joseph Sokol-Margolis)
Tue May 18 22:28:30 1999
Message-Id: <199905190228.WAA08492@smoke-screen.mit.edu>
To: Greg Hudson <ghudson@MIT.EDU>
Cc: Joseph Sokol-Margolis <seph@MIT.EDU>, testers@MIT.EDU
In-Reply-To: Your message of "Tue, 18 May 1999 19:06:00 EDT."
<199905182306.TAA29541@small-gods.mit.edu>
Date: Tue, 18 May 1999 22:28:23 EDT
From: Joseph Sokol-Margolis <seph@MIT.EDU>
> > if you try and run xss-button, it should tell you to run xss-button
> > instead of xss (okay, this isn't really a bug)
>
> "Huh?" Is there a mistake in that sentence?
right, I can be more coherent. :)
xss, is designed to run in the background and be controled by
xss-command. so you normally run xss& then xss-command -whatever
xss-button is a replacement for xss, not something designed to talk
to an xss process.I happen to find this counterintuitive, so I ran
xss&, then xss-button, and got an error about already having an xss
running. It would be neat if the error was more along the lines of
"run xss-button *instead* of xss"
seph
