search for: opportunistic

...ut when to configure oplocks. This is intended as a rudimentry guide to help avoid the most obvious oplock pitfalls. Hopefully the plain text alignments hold up well for most editors. Word messes things up. Thanks, Eric Roseme Hewlett-Packard -------------- next part -------------- HP-UX Samba Opportunistic Locking Usage Recommendations Eric Roseme, Hewlett-Packard October, 2002 Contents Legal Notices 2 Chapter 1 Introduction 4 Chapter 2 Opp...

Goldmine seems to a compiled database application compiled in something likeClipper. Clipper applications record lock through ISAM like files (DBF). However, in Windows NT/2000/XP, Opportunistic locking is turned on by default in order to accelerate file transfer from file services. [Windows 95/98 did not Opportunisticly lock] However, opportunistic locking corrupts ISAM and ISAM like databases. Here is how to turn off opportunistic locking. (NOTE: It has to be turned off at a system wi...

I'm switching quota backend to redis (from maildir++), so all my current usages are reset. I get that I can do "doveadm quota recalc -A", but it takes forever (and auth processes time out/crash). It would make much more sense to recalc the usage on login if the current usage is unset. Is there no way to do a recalc-quota-on-first-login? Thanks. -- Tom Sommer

On 2016-04-06 20:38, Timo Sirainen wrote: > On 06 Apr 2016, at 13:43, Tom Sommer <mail at tomsommer.dk> wrote: >> >> I'm switching quota backend to redis (from maildir++), so all my >> current usages are reset. >> >> I get that I can do "doveadm quota recalc -A", but it takes forever >> (and auth processes time out/crash). >>

This is an idea from FreeSWAN, which was implemented in the recently released version 1.0. Basically the idea is that FreeSWAN sites automatically encrypt traffic between them when possible, without having to set up the link ahead of time. How this works is: The sites publish some info in DNS. FreeSWAN gets some traffic destined for that site. - looks up the info in DNS - if the info is there:

On 07 Apr 2016, at 14:49, Tom Sommer <mail at tomsommer.dk> wrote: > > On 2016-04-06 21:09, Tom Sommer wrote: >> On 2016-04-06 20:38, Timo Sirainen wrote: >>> On 06 Apr 2016, at 13:43, Tom Sommer <mail at tomsommer.dk> wrote: >>>> I'm switching quota backend to redis (from maildir++), so all my current usages are reset. >>>> I get that

...r about 993/995 not being official, they *are* official, but 465 is not which is probably what led to the confusion. > It would > appear that STARTTLS is significantly more vulnerable to MITM attacks > than plain SSL/TLS for all the above protocols. Is the slight extra > convenience of opportunistic encryption really worth the substantial > loss in security? I would not say significantly. If the client is configured to require encryption and to validate the resulting cert from the server then any MITM vulnerability of STARTTLS is fully mitigated. A MITM attack is only an issue if the cli...

Is there any package available for qmail? I am having hard time finding it.

At one point seems like I found a write up in the Dovecot docs about having Dovecot directly listen on port 25 using Opportunistic TLS along with port 587 authentication, so only Dovecot was required to handle incoming email. Said another way, no requirement for Sendmail, or Postfix or EXIM. Just straight up Dovecot. If I'm remembering correctly, someone point me to the correct docs for this setup. Thanks!

IF you are not stuck to IPSec, you might want to take a look at OpenVPN (www.openvpn.org). I found OpenVPN easier to install than FreeSWAN (an IPSEC VPN) and have setup an OpenVPN solution between my German office and our mainoffice in a matter of hours. Thom van der Boon E-Mail: Thom.van.der.Boon at vdb.nl ===== Thom.H. van der Boon b.v. Havens 563 Jan Evertsenweg 2-4 NL-3115 JA Schiedam

...r at all with STARTTLS for imap, pop3 and even smtp (and by the way, port 465 for SMTP + SSL/TLS *is* indeed deprecated officially)? It would appear that STARTTLS is significantly more vulnerable to MITM attacks than plain SSL/TLS for all the above protocols. Is the slight extra convenience of opportunistic encryption really worth the substantial loss in security?

...xmit packets > speculatively in virtnet_poll_tx(), we need call free_old_xmit_skbs() > unconditionally. This can also help to reduce the possible of napi > rescheduling in virtnet_poll_tx(). Because of the use of trylock there. Absolutely, thanks! Perhaps I should only use trylock in the opportunistic clean path from the rx softirq and full locking in the tx softirq. I previously observed that cleaning here would, counterintuitively, reduce efficiency. It reverted the improvements of cleaning transmit completions from the receive softirq. Going through my data, I did not observe this regression...

...xmit packets > speculatively in virtnet_poll_tx(), we need call free_old_xmit_skbs() > unconditionally. This can also help to reduce the possible of napi > rescheduling in virtnet_poll_tx(). Because of the use of trylock there. Absolutely, thanks! Perhaps I should only use trylock in the opportunistic clean path from the rx softirq and full locking in the tx softirq. I previously observed that cleaning here would, counterintuitively, reduce efficiency. It reverted the improvements of cleaning transmit completions from the receive softirq. Going through my data, I did not observe this regression...

...?). Then the client seems to close all opened files to the shares. I post at the end a part of the traces from the sniffer. How can I stop this problem ? Thanks. SMB Command: 0x73 (115) - Session Set Up and X (including User Logon) Flags1: 0x18 (24) Response: 0 Notify on every action: 0 Opportunistic Lock: 0 Canonized Paths: 1 Ignore Path Case: 1 Do Not Acknowledge: 0 LockAndOp Supported: 0 Flags2: 0x4807 (18439) UNICODE: 0 NT-style error: 1 Read is allowed if execution is allowed: 0 Long Name: 1 Extended attributes: 1 Non-8.3 names allowed: 1 Tree ID: 0x0000 (0) Process...

...and permissions settings should be to support multi-user Quickbooks on a Samba share? The Long Version: The Quickbooks data-file resides on it's own samba share (quickbooks), and all the client workstations run Win2K SP4 with Quickbooks Pro 2002. When we were running Samba 2.2.8, we disabled opportunistic locking on the quickbooks share and we had no problems (except for a highly intermittent situation where the Quickbooks agent wouldn't "let go" of the quickbooks data file eventhough Quickbooks was no longer running as an application). I upgraded to Samba 3.0Beta2+RC4 accidentally du...

Our development team has been having the following issue for quite some time and I cannot isolate the problem. I saw a similar posting in the archives but there are no replies. We are running Samba 2.0.7 on a RedHat 6.2 server and we connect to the server from Windows 2000 desktops. We are editing files through a drive mapped to a share on the server. The problem is when we save the file in the

A little background: The fmuladd intrinsic was introduced to support the FP_CONTRACT pragma in C. llvm.fmuladd.* is generated by clang when it sees an expression of the form 'a * b + c' within a single source statement. If you want to opportunistically form FMA target instructions my inclination would be to skip llvm.fmuladd.* and just form them from a*b+c expressions at isel time. I don't see any fundamental problem with forming llvm.fmuladd.* to model FMA formation opportunities in an IR pass though. - Lang. On Wed, Dec 12, 2012 at 4...

...tle less subtle: >> >> ALTERNATIVE "testl %eax, %eax; lz .Lsyscall_32_done", "jmp >> .Lsyscasll_32_done", X86_FEATURE_XENPV >> >> Borislav, what do you think? >> >> Ditto for the others. > > Can you just add !xen_pv_domain() to the opportunistic SYSRET check > instead? Bury the alternatives in that macro, ie. > static_cpu_has(X86_FEATURE_XENPV). That would likely benefit other > code as well. We could, but that won't help the 64-bit case where we want to keep the full asm path. Also, Xen is capable of the equivalent of sys...

...sts.centos.org/mailman/listinfo/centos > I doubt it, qmail is quite deprecated and does not support any modern TLS capabilities without a ton of community provided patches. I doubt even with community supported patches that it will ever support RFC 7672 which is important (it takes the "opportunistic" out of opportunistic TLS when both servers implement it, preventing protocol downgrade attacks that now are as easy as removing the STARTTLS)

...entos >> > > I doubt it, qmail is quite deprecated and does not support any modern > TLS capabilities without a ton of community provided patches. > > I doubt even with community supported patches that it will ever > support RFC 7672 which is important (it takes the "opportunistic" out > of opportunistic TLS when both servers implement it, preventing > protocol downgrade attacks that now are as easy as removing the > STARTTLS) You could try Matt Simerson's Toaster: https://github.com/msimerson/Mail-Toaster-6 It does a lot more than just qmail and repla...