similar to: Prohibit dots in folder names

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 11 Jan 2017, Aki Tuomi wrote: > On 10.01.2017 17:38, Marek Grondecki wrote: >> Hello Dovecot Community, >> >> I am using Dovecot 2.2.13-12~deb8u1 (Debian Jessie). >> >> separator = / >> listescape plugin is NOT active >> LAYOUT=fs is NOT active >> >> I would like to prohibit a creation

On 10.01.2017 17:38, Marek Grondecki wrote: > Hello Dovecot Community, > > I am using Dovecot 2.2.13-12~deb8u1 (Debian Jessie). > > separator = / > listescape plugin is NOT active > LAYOUT=fs is NOT active > > I would like to prohibit a creation of folders with dot "." in the > names - > so creation of a folder "foo.bar" should NOT be possible.

On 11.01.2017 11:35, Steffen Kaiser wrote: > On Wed, 11 Jan 2017, Aki Tuomi wrote: > > On 10.01.2017 17:38, Marek Grondecki wrote: > >> Hello Dovecot Community, > >> > >> I am using Dovecot 2.2.13-12~deb8u1 (Debian Jessie). > >> > >> separator = / > >> listescape plugin is NOT active > >> LAYOUT=fs is NOT active > >>

Hello Dovecot Community, I am using Dovecot 2.2.13-12~deb8u1 (Debian Jessie). separator = / listescape plugin is NOT active LAYOUT=fs is NOT active I would like to prohibit/ban the creation of folders with dot "." in the names - so creation of a folder "foo.bar" should NOT be possible. Currently, when I create "foo.bar" in Outlook 2013 it will be created but

'bry I'd like to install (and use ;) both wine forks: winehq and transgaming's winex. Both compiled from cvs sources. Is there any way to do it? What i have to do and why? TIA -- ojciec

when used Posix File System Test Suite(pjd-fstest) to test btrfs, some cases about setfacl failed when noacl mount option used. I simplified used commands in pjd-fstest, and the following steps can reproduce it. ------------------------ # cd btrfs-part/ # mkdir aaa # setfacl -m m::rw aaa <- successed, but not expected by pjd-fstest. ------------------------ I checked ext3, a warning

* Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > Currently the blacklist is maintained by hand in kprobes.c > which is separated from the function definition and is hard > to catch up the kernel update. > To solve this issue, I've tried to implement new > NOKPROBE_SYMBOL() macro for making kprobe blacklist at > build time. Since the NOKPROBE_SYMBOL()

On Tue, 12 Nov 2013 02:18:53 +0900 Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > > > After that we can convert all the rest, probably as part of this series. > > OK, I'll do. :) > BTW, converting all the __kprobes involves many archs, which > kprobes ported. In that case, which mailing-list would better me > to post the series, linux-arch? I

On Fri, Nov 15, 2013 at 5:43 PM, Steven Rostedt <rostedt at goodmis.org> wrote: > On Fri, 15 Nov 2013 04:53:18 +0000 > Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > >> .entry.text is a code area which is used for interrupt/syscall >> entries, and there are many sensitive codes. >> Thus, it is better to prohibit probing on all of such codes

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, How can I check if (i.e.) my provider is requesting me to hide the callerid? I.e. (Telco)E1/PRI---Zap(Asterisk1)IAX---IAX(Asterisk2)SIP---EP Now, if a call comes from the Telco with CLI screening prohobited to Asterisk1, where the call is forwarded using Dial() via IAX to Asterisk2 and then (also using Dial()) on to a SIP endpoint, how do I

On ISDN lines it's possible to prohibit the presentation of caller id, what if I have a SIP gateway, something like an Audiocodes Mediant 1000. How do I prohibit the caller id presentation on that one? Regards, Kristian -- Kristian Larsson KLL-RIPE Network Engineer Net At Once [AS35706] email: kristian@netatonce.se

Hi, I have an issue with a sieve_before rule (the script move incoming email to Junk folder when DMARC=fail and policy is quarantine) because one of my user delete his Junk folder : dovecot: lda(myuser at domain.com): Error: sieve: execution of script /etc/dovecot/sieve_before/01-dmarc-fail.sieve failed, but implicit keep was successful: 1 Time(s) dovecot: lda(myuser at domain.com): Error:

Hi There, Setup: - Debian Squeeze - Samba 3.5.6 - passdb-backend: tdbsam I have some machines running here, which are used by students. There is a "global" account for all of them. I'd like to prevent them from changing the password, so that nobody can make it a exclusive account. Is ther a way to do that? Is it possible to do that with pdbedit? Thanks for help in advance

On Fri, 15 Nov 2013 04:53:18 +0000 Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > .entry.text is a code area which is used for interrupt/syscall > entries, and there are many sensitive codes. > Thus, it is better to prohibit probing on all of such codes > instead of a part of that. > Since some symbols are already registered on kprobe blacklist, > this also

On Fri, 15 Nov 2013 04:53:18 +0000 Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > .entry.text is a code area which is used for interrupt/syscall > entries, and there are many sensitive codes. > Thus, it is better to prohibit probing on all of such codes > instead of a part of that. > Since some symbols are already registered on kprobe blacklist, > this also

Hello all, first post, need help. I'm running a complex asterisk 1.8 install with five machines. I inherited it and don't fully understand it, nor the deep mysteries of asterisk either. I would appreciate any insight you might have. I scoured the 'net and the Digium wiki and my Google-Fu has failed me. I've been asked to somehow prohibit transfers to extension 3232. It has to be

(2013/11/11 20:16), Ingo Molnar wrote: > > * Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > >> Currently the blacklist is maintained by hand in kprobes.c >> which is separated from the function definition and is hard >> to catch up the kernel update. >> To solve this issue, I've tried to implement new >> NOKPROBE_SYMBOL() macro

(2013/11/11 20:16), Ingo Molnar wrote: > > * Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> wrote: > >> Currently the blacklist is maintained by hand in kprobes.c >> which is separated from the function definition and is hard >> to catch up the kernel update. >> To solve this issue, I've tried to implement new >> NOKPROBE_SYMBOL() macro

.entry.text is a code area which is used for interrupt/syscall entries, and there are many sensitive codes. Thus, it is better to prohibit probing on all of such codes instead of a part of that. Since some symbols are already registered on kprobe blacklist, this also removes them from the blacklist. Signed-off-by: Masami Hiramatsu <masami.hiramatsu.pt at hitachi.com> Cc: Thomas Gleixner

Hello list, I'm using dovecot 1.1.11 and I'm going to prohibit users to remove their INBOX and some other directories in the mailbox root. I used Access Control Lists (http://wiki.dovecot.org/ACL) to do this: protocol imap { mail_plugins = acl } plugin { # With global ACLs in /etc/dovecot/acls/ directory: acl = vfile:/etc/dovecot/acls } /etc/dovecot/acls/.DEFAULT: owner