Package: t-prot
Version: 2.0.2-1
Severity: minor

t-prot fails to handle an MS-style TOFU from mutt.  When called without
the -Mmutt option, the same message was handled correctly.

I think the problem is the following, at /usr/bin/t-prot line 715 after
the t-prot-r1.243-mutt157.diff patch has been applied:

  $$lines[$x] !~
      /^(?:\e[^\a]+\a)?(?:\Q$mutt_ssloutstart\E)/o)) {

This equates to true if the given line *doesn't* match the SSL intro,
and consequently it matches the first line of the message.  Shouldn't
the test be using a "=~" (like in the check for pgpoutstart, immediately
before it) instead?

-- System Information:
Debian Release: testing/unstable
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'proposed-updates'), 
(500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=en_GB.ISO8859-15, LC_CTYPE=en_GB.ISO8859-15 (charmap=ISO-8859-15)

Versions of packages t-prot depends on:
ii  libgetopt-mixed-perl          1.008-10   Perl module for processing options
ii  liblocale-gettext-perl        1.05-1     Using libc functions for internati
ii  perl                          5.8.8-4    Larry Wall's Practical Extraction 

Versions of packages t-prot recommends:
ii  mutt                1.5.11+cvs20060403-1 text-based mailreader supporting M

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to