[exim-dev] [Bug 660] New: multi-valued attributes returned f…

Startseite
Nachricht löschen
Nachricht beantworten
Autor: Jeremy Harris
Datum:  
To: exim-dev
Neue Treads: [exim-dev] [Bug 660] multi-valued attributes returned from an ldap lookup parsing is hard, [exim-dev] [Bug 660] multi-valued attributes returned from an ldap lookup parsing is hard, [exim-dev] [Bug 660] multi-valued attributes returned from an ldap lookup parsing is hard, [exim-dev] [Bug 660] multi-valued attributes returned from an ldap lookup parsing is hard, [exim-dev] [Bug 660] multi-valued attributes returned from an ldap lookup parsing is hard
Betreff: [exim-dev] [Bug 660] New: multi-valued attributes returned from an ldap lookup parsing is hard
------- You are receiving this mail because: -------
You are on the CC list for the bug.

http://bugs.exim.org/show_bug.cgi?id=660
           Summary: multi-valued attributes returned from an ldap lookup
                    parsing is hard
           Product: Exim
           Version: 4.67
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: bug
          Priority: low
         Component: Lookups
        AssignedTo: nigel@???
        ReportedBy: jgh146exb@???
                CC: exim-dev@???, jgh146exb@???



Created an attachment (id=224)
--> (http://bugs.exim.org/attachment.cgi?id=224)
ldap lookup patch for multi-valued attributes

The ldap lookup code returns a multi-valued attribute as a list separated by
comma, space. This presents a problem when a value might contain that
sequence.

The docs only say "separated by commas".

The problem is likely to exist on all platforms and OS'.


A suggested fix:
1) Double any comma in an attribute value as a means of quoting it.
   Issue: this is an incompatible change at least for single-value
          attributes, and for when users are already successfully parsing
          multi-value.
2) Change the the list separator to be only the comma.
   Issue: this is an incompatible change which will affect existing
          parsing code (unless using exim's builtin list parsing).
   Assumption: the space is mainly for human-readability.



--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email