similar to: [Bug 2685] New: Case sensitive hostname matching

Hi, as recently noticed by one of our customers, ssh tends to perform hostname matching in a case sensitive manner since the lowercasing has been delayed till after configuration parsing (by commits d56b44d2dfa093883a5c4e91be3f72d99946b170 and eb6d870a0ea8661299bb2ea8f013d3ace04e2024). Given that hostnames are ususally interpreted in a case insensitive way (and the code actually expects the

https://bugzilla.mindrot.org/show_bug.cgi?id=2267 Bug ID: 2267 Summary: Host matching uses modified hostname as well as original Product: Portable OpenSSH Version: 6.6p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: ssh

On Wed, 20 Feb 2019 at 23:54, Corinna Vinschen <vinschen at redhat.com> wrote: > The previous revert enabled case-insensitive user names again. This > patch implements the case-insensitive user and group name matching. > To allow Unicode chars, implement the matcher using wchar_t chars in > Cygwin-specific code. Keep the generic code changes as small as possible. > Cygwin:

Hello, The uniqueness validator was always case sensitive but that seems wrong because we want uniqueness validations to be insensitive in most of the time. Do not make more sense be insensitive by default and set sensitive only where it should be? We are migrating a lot of big applications from mysql to postgresql here and we are setting case sensitive to false on **all** uniqueness

> I want to have it case-insensitive again, like in Pigeonhole version 0.4.24 i would also plea for making it case-insensitive again! We were hit by this too, and I never saw any mail system in which the local Part ist Case sensitive! Sincerly, Klaus Steinberger -- Rechnerbetriebsgruppe / IT, Fakult?t f?r Physik Klaus Steinberger FAX: +49 89 28914280 Tel: +49 89 28914287 --------------

The recipients in the vacation :addresses String list are matched case-sensitive. If the recipient gets a mail with wrong case, the message is discarded with: "discarding vacation response for implicitly delivered message; no known (envelope) recipient address found in message headers" I think the matching should be case-insensitive. Is this a bug or do I miss some option? I'm

> > It is not recommended to rely on local-part case, but it is indeed > case-sensitive. > > And this is to avoid such issues that postfix supports address > cleanup/canonicalisation before forwarding mails to dovecot. > > ---------- > RFC 5321: > > "Local-part = Dot-string / Quoted-string ; MAY be case-sensitive > [?] > While the above definition

Forgive me if this topic has already been discussed on the list. I googled but couldn''t find much. I''d like to search through text for US state abbreviations that are written in capitals. What is the best way to do this? I read somewhere that tokenized fields are stored in the index in lowercase, so I am concerned that I will lose precision. What is the best way to store a

> On 9 Sep 2019, at 16.17, Philipp Faeustlin via dovecot <dovecot at dovecot.org> wrote: > >> It is not recommended to rely on local-part case, but it is indeed >> case-sensitive. >> And this is to avoid such issues that postfix supports address >> cleanup/canonicalisation before forwarding mails to dovecot. >> ---------- >> RFC

Hi! This is a heads-up for now, more debugging to follow. I had to downgrade samba from 4.20.1 to 4.19.6 because 4.20 broke case insensitive file access entirely. Only exact case filename works, no matter which value is set in "case sensitive" parameter. In 4.19, things works again. /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key:

On Sun, Mar 12, 2017 at 2:55 PM, Oliver Braunsdorf via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > Perhaps by "value" you mean points-to set? > > Thats right! I meant the points-to set. Sorry I didn't mention that. > I want to track back the value of the parameter to its definition -- an > "assignment" which could be indirect through a pointer

On Wed, Sep 4, 2019 at 8:25 AM Philipp Faeustlin via dovecot < dovecot at dovecot.org> > Further investigation showed me that it has to be a bug. > > I tested with Dovecot 2.2.36.3 (a7d78f5a2), Pigeonhole version 0.4.24 > (5a7e9e62): > > In this version the additional addresses in vacation :addresses > ["test at example.com"] are handled case-insensitive. >

others have found this problem ? this possible bug can be used by user in that way that one password login can use 2 maildirs in filesystem effitively give them all space qoutas and lost of other goodies so to speak: foo at example.com with a password can login with fOO at example.com and fOo at example.com add more chars to get more mailbox :/ confirms ? i found the problem when i had

Hi, I am looking for some flow-sensitive (context-insensitive) alias analysis algorithm implemented in LLVM. (I use LLVM 3.9, hope to switch to 4.0 soon.) As far as I know, none of the built-in analysis (basicAA, globals-modref, andersAA, etc.) is intended to be flow-sensitive. So I searched and came across these two 1. https://github.com/unsw-corg/SVF by Yulei Sui (for LLVM 3.8) 2.

innetgr.. much easier.. Had a look for the user section but didn't find it in my 15 seconds of looking.. --- access.c 2003-07-30 16:12:27.000000000 +1000 +++ ../rsync-2.6.0-Linux/access.c 2004-02-01 23:21:12.000000000 +1100 @@ -22,10 +22,21 @@ */ #include "rsync.h" +#include <netdb.h> static int match_hostname(char *host, char *tok) { + char

Hello, One year ago a bug was reported regarding pigeonhole vacation plugin https://www.mail-archive.com/dovecot at dovecot.org/msg78588.html a mail sent to User at domain.com instead of user at domain.com will generate a " vacation action: discarding vacation response for implicitly delivered message; no known (envelope) recipient address found in message headers (recipient=<user at

On 6/7/24 9:34 AM, Michael Tokarev via samba wrote: > I had to downgrade samba from 4.20.1 to 4.19.6 because 4.20 > broke case insensitive file access entirely.? Only exact case > filename works, no matter which value is set in "case sensitive" > parameter. hm, can't reproduce: $ bin/smbclient -U "slow%x" //localhost/test smb: \> ls foo foo N

Greetings, As previously reported by me to the Debian bug tracking system: ---------------------------------------------------------------------- An access list in rsyncd.conf may contain hostnames as well as addresses. It may contain several patterns to match against. address_match (in access.c) does this by trying to match hostname and address against each of the patterns until a match is

I am using dovecot as an IMAP server for a Cisco product (Cisco Agent Desktop by Calabrio) and noticed some odd behavior when trying to access emails. The mail is delivered to the main INBOX, then a Cisco server moves it to a directory within the INBOX based on the queue it is meant for. Here is the directory structure of the Maildir: Maildir/INBOX Maildir/INBOX/tmp Maildir/INBOX/63

Strangest thing. Since some time Marts 25. I'm no longer receiving mails from the dovecot mailing list server. Mails from other sources are behaving fine. Instead I'm just seing Mar 26 08:27:54 dna01 postfix/smtpd[107746]: Anonymous TLS connection established from talvi.dovecot.org[94.237.25.159]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) Mar 26 08:27:54 dna01