> On Aug 15, 2016, at Aug 15, 4:06 AM, Ariano-Tim Donda > <[email protected]> wrote: > > For my project it must be possible to check different bytes from \x00 to \xFF > via tcp-check expect rstring. But it is not possible to check NULL bytes. > Everything after the first NULL byte will be ignored. > My test configuration: > tcp-check send-binary 9C00000800870100 > tcp-check expect rstring ^\x9a\x00\x00.{5}\x00{13}\x10\x00\x04
Strings are null terminated. I’m guessing that maybe the ‘binary’ matcher is what you want to use instead of ’string'? -Bryan > > > Best regards/Mit freundlichen Grüßen > ------------------------------------------------- > Ariano-Tim Donda > System Engineer HSM > > Utimaco IS GmbH > Germanusstr. 4 > 52080 Aachen > Germany > > phone: +49 241 1696 – 220 > www.utimaco.com <http://www.utimaco.com/> > > > > Utimaco IS GmbH > Germanusstr. 4, D.52080 Aachen, Germany, Tel: +49-241-1696-0, www.utimaco.com > <http://www.utimaco.com/> > Seat: Aachen – Registergericht Aachen HRB 18922 > VAT ID No.: DE 815 496 496 > Managementboard: Malte Pollmann (Chairman) CEO, Dr. Frank J. Nellissen CFO > > This communication is confidential. We only send and receive email on the > basis of the terms set out at https://www.utimaco.com/en/e-mail-disclaimer/ > <https://www.utimaco.com/en/e-mail-disclaimer/>
