search for: negociated

Hi All, I've set up Dovecot to use my signed SSL certificate and IMAP client is using STARTTLS on port 143 without secure authentication. The TLS negociation process seems to go through ok but once the negociation is finished the client sends an IMAP LOGOUT message; he does not try to authenticate, below is the Dovecot's info log: dovecot: 2010-06-15 15:37:01 Info: auth(default): new

If you don't want to proxy the media through * the put this setting: canreinvite=yes this will allow the 2 end points to connect directly for the RTP bypassing you. otherwise I have noticed the same when I try to proxy I have to make sure everyone is using the same codec or it doesn't work well. .o-------------------------------------------------------o. Brian Fertig NOC/Network

Is there a "cookbook" for setting this up? There are examples for setting up a tunnel between two fixed-address networks (e.g. a remote LAN that needs to be "integrated" with a central LAN over IPSec but I can't find anything addressing the other situation -- remote user(s) where the connecting IPs are not known in advance, such as a person with a laptop or smartphone in a

Hi all, In another series I proposed to add an architecture specific callback to fail feature negociation on architecture need. In VIRTIO, we already have an entry to reject the features on the transport basis. Transport is not architecture so I send a separate series in which we fail the feature negociation inside virtio_ccw_finalize_features, the virtio_config_ops.finalize_features for S390

Hi all, In another series I proposed to add an architecture specific callback to fail feature negociation on architecture need. In VIRTIO, we already have an entry to reject the features on the transport basis. Transport is not architecture so I send a separate series in which we fail the feature negociation inside virtio_ccw_finalize_features, the virtio_config_ops.finalize_features for S390

Hello, I've got an analog phone which is currently receiving unsollicited FAX calls from PSTN. For learning purpose, I'm preparing an Asterisk/SPA3102 setup that would let voice calls come in and out and translate incoming FAX calls to TIF files (forwarded through email)). My target setup is : PSTN <-- analog--> SPA3102 Line Port <-- SIP --> Asterisk <-- SIP -->

Hello, I tried to activate SSL on LMTP service, to secure connections between Postfix and Dovecot on my LAN, but Dovecot is not negociating a TLS session with Postfix. If I enforce TLS for LMTP at Postfix's side, communication between Postfix and Dovecot is not working. I put ssl = yes ssl_cert = </dovecot/ssl/ssl-LMTP.pem ssl_key = </dovecot/ssl/ssl-LMTP.key in section protocol

...new stack -- Executing Playback("H323/ip$10.0.3.23:32782/6502", "demo-instruct") in new stack -- Playing 'demo-instruct' (language 'en') which is the normal procedure. The connexion is well built between the client and asterisk (H225 & H245) and well negociated with the codec (gsm). But no RTP stream comes out of the asterisk (I tcpdumped to be sure). My question is: 1/Is there a way to explain this ? (lack of configuration, compilation options) if not, 2/ Is there a way to investigate deeper in order to understand where does the RTP stream fain...

Hi Is there known advices on how to favor PFS with dovecot? In Apache, I use the following directives, with cause all modern browsers to adopt 256 bit PFS ciphers, while keeping backward compatibility with older browsers and avoiding BEAST attack: SSLProtocol all -SSLv2 SSLHonorCipherOrder On SSLCipherSuite ECDHE at STRENGTH:ECDH at STRENGTH:DH at STRENGTH:HIGH:-SSLv3-SHA1:-TLSv10

Hello everybody, I am writing on that mailing list because I have an issue using lftp and I would love to have more infos about features available on the LFTP version provided by CentOS 6. I try to connect to a ftp server in secured mode using FTPS explicit and I would love to use TLSv1.2. After several tries, I understood that the TLS negociation was not possible using TLSv1.2 (It works only

...no real way to know that this is the case, this is a specific "feature" of the qemu implementation. 2 - VIRTIO_F_PLATFORM_DMA (or whatever you want to call it), is a property of the guest platform itself (not qemu), there's no way the "peer" can advertize it via the virtio negociated flags. At least for us. I don't know for sure whether that would be workable for the ARM case. In our case, qemu has no idea at VM creation time that the VM will turn itself into a secure VM and thus will require bounce buffering for IOs (including virtio). So unless we have another hook for t...

...no real way to know that this is the case, this is a specific "feature" of the qemu implementation. 2 - VIRTIO_F_PLATFORM_DMA (or whatever you want to call it), is a property of the guest platform itself (not qemu), there's no way the "peer" can advertize it via the virtio negociated flags. At least for us. I don't know for sure whether that would be workable for the ARM case. In our case, qemu has no idea at VM creation time that the VM will turn itself into a secure VM and thus will require bounce buffering for IOs (including virtio). So unless we have another hook for t...

Hello, I have the pleasure to announce that the X.org Developer Conference 2017 will be held in Mountain View, California from September 20th to September 22nd. The venue is located at the Googleplex. The official page for the event is http://www.x.org/wiki/Events/XDC2017 while the call for paper is at http://www.x.org/wiki/Other/Press/CFP2017/ As usual, we are open to talks across the layers

Hello all, I'm looking for some help to try to understand why my CPE doesn't work good with Asterisk in MGCP. Here is what I want to do : - Register a TECOM AH4021 on Asterisk in MGCP with the following profile in mgcp.Conf : [general] port = 2727 bindaddr = 10.95.20.1 disallow=all allow=g729 allow=alaw 020202020202] context=mgcp host=dynamic canreinvite=no dtmfmode=rfc2833 nat=yes

On Thu, 6 Aug 2020 16:23:01 +0200 Pierre Morel <pmorel at linux.ibm.com> wrote: > Hi all, > > In another series I proposed to add an architecture specific > callback to fail feature negociation on architecture need. > > In VIRTIO, we already have an entry to reject the features on the > transport basis. > > Transport is not architecture so I send a separate

Hi I made some work using samba 2.0.6. I use large directory, more than 10000 file. The time to have a list from window NT is very big 2Minuts. I spy a little the dialog and I see that the negociation for exange files name is limited to 170 filenames and a buffer to 16387 octets. Do you know a way to change this ? I tryed without result, max xmit = 60000 packet size= 60000

In the course of debugging my still-unsolved "smbclient tar starts throwing SMB signature errors after 750MB of data or so" error, I came across this apparent inconsistency... >From the smb.conf man page: "client use spnego (G) This variable controls controls whether samba clients will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and

Hello, I am running asterisk 1.4. For argument's sake I have 4 telephones. 2 support video, 2 do not. Calls between phones work fine and codecs are properly negociated. I have videosupport=yes in sip.conf and when the two video phones communicate I have video. I call meet me with this command EXEC MEETME 1234|d SIP looks like this : -- AGI Script Executing Application: (MeetMe) Options: (17246|d) Video is at 192.168.1.1 port 17280 Audio is at 192.168.1....

Anyone out there using NetLogic DIDs? And have inbound working? I got outbound working, but no joy so far with inbound. Here are the relevant parts from my conf files: iax.conf [general] tos=lowdelay jitterbuffer=no register => username:secret@zoot.netlogic.net [netlogic] type=friend host=dynamic context=sourcekit-main auth=plaintext username= secret= disallow=all allow=ulaw allow=all

...se, this is a specific "feature" of the qemu implementation. > > > > 2 - VIRTIO_F_PLATFORM_DMA (or whatever you want to call it), is a > > property of the guest platform itself (not qemu), there's no way the > > "peer" can advertize it via the virtio negociated flags. At least for > > us. I don't know for sure whether that would be workable for the ARM > > case. In our case, qemu has no idea at VM creation time that the VM > > will turn itself into a secure VM and thus will require bounce > > buffering for IOs (including virtio...