similar to: SNI-20: Telnetd tgetent vulnerability

-----BEGIN PGP SIGNED MESSAGE----- ##### ## ## ###### ## ### ## ## ##### ## # ## ## ## ## ### ## ##### . ## ## . ###### . Secure Networks Inc. Security Advisory

-----BEGIN PGP SIGNED MESSAGE----- ##### ## ## ###### ## ### ## ## ##### ## # ## ## ## ## ### ## ##### . ## ## . ###### . Secure Networks Inc. Security Advisory

-----BEGIN PGP SIGNED MESSAGE----- ###### ## ## ###### ## ### ## ## ###### ## # ## ## ## ## ### ## ###### . ## ## . ######. Secure Networks Inc. Security Advisory

I don''t know if this has made it to you yet, so here it is... =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Kirk Bauer Georgia Tech gt5918a@prism.gatech.edu or Finger for PGP Key --> kirk@kaybee.gt.ed.net http://www.kaybee.gt.ed.net/~kirk/html/index.html Resnet RTA (Residence Technical Advisor) GTRI Co-Op ----------

###### ## ## ###### ## ### ## ## ###### ## # ## ## ## ## ### ## ###### . ## ## . ######. Secure Networks Inc. Security Advisory March 2, 1997

###### ## ## ###### ## ### ## ## ###### ## # ## ## ## ## ### ## ###### . ## ## . ######. Secure Networks Inc. Security Advisory February 24, 1997

I try to make an asterisk system and downloaded and unzipped the file asterisk-1.0-RC1.tar.gz. When I do the first make I got the following messages: ..... checking for tgetent in ltermcap.......no checking for tgetent in ltinfo.......no checking for tgetent in lcurses.......no checking for tgetent in lncurses.......no configure: error: termcapsupport not found make: *** [editline/libedit.a] Error

Dear all, I have tried to compile * 1.0.6 (downloaded from the digium site, in the right sequence - zaptel, libpri, asterisk) on two different machines running SUSE 9.2. The problem comes during some preliminary checks: checking for ar... /usr/bin/ar checking for tgetent in -ltermcap... no checking for tgetent in -ltinfo... no checking for tgetent in -lcurses... no checking for tgetent in

Make sure you have libtermcap and libtermcap-devel loaded.. To check use #rpm -q libtermcap and #rpm -q libtermcap-devel I have an install guide for RH9 in PDF format if you are interested.. Later.. > Hello, I am trying to install asterisk and get this error. > > creating cache ./config.cache > checking for gcc... gcc > checking whether the C compiler (gcc ) works... yes

I thought I would give RedHat 9 a try with Asterisk..I thought it would be a good idea to use the latest version.. Zaptel, Zapata and Libpri all appear to have compiled sucessfully.. But.. (Why is there always a but??) It seems Asterisk is having issues with 'termcap' or 'tgetent' whatever that is.. Here is the output from 'make install'.. --------Start-------- if [ -d

I am trying to run the make command to install Asterisk, but I get the following error: make ... ... checking for tgetent in -ltermcap ... no checking for tgetent in -ltinfo ... no checking for tgetent in -lcurses ... no checking for tgetent in -lncurses ... no configure: error: termcap support not found I am running Mandrake 9.1 on a Pentium II 200MHz. Could this be a hardware issue? I

FYI? dovecot 2.2.10 from RedHat 7 has an issue with clients, which won't send SNI.?As you are using version 2.2.27 you might encounter the same behaviour. If the client won't send SNI, my server randomly answers with any cert instead of?the default cert,? --Perhaps dovecot just utilises the last used cert? One speciality?of my certs is, that both share the same Common Name (CN) but differ

On Thursday 20 of October 2016, Aki Tuomi wrote: > On 20.10.2016 15:41, Arkadiusz Mi?kiewicz wrote: > > On Thursday 20 of October 2016, Aki Tuomi wrote: > >> On 18.10.2016 14:16, Arkadiusz Mi?kiewicz wrote: > >>> On Monday 17 of October 2016, KT Walrus wrote: > >>>>> On Oct 17, 2016, at 2:41 AM, Arkadiusz Mi?kiewicz <arekm at maven.pl> >

////////////////////////////////////////////////////////////////////////// I have got a couple of messages stating that I am wrong and that the resolver vulnerability sent to list by Oliver Friedrichs (oliver@secnet.com) is a new one. Our discussion with Oliver outlined that even though it is possible that this vulnerability was discussed during BOFs at conferences such as LISA, SANS and NETSEC,

On Monday 17 of October 2016, KT Walrus wrote: > > On Oct 17, 2016, at 2:41 AM, Arkadiusz Mi?kiewicz <arekm at maven.pl> wrote: > > > > On Monday 30 of May 2016, Arkadiusz Mi?kiewicz wrote: > >> Is there a way to log SNI hostname used in TLS session? Info is there in > >> SSL_CTX_set_tlsext_servername_callback, dovecot copies it to > >>

On Thursday 20 of October 2016, Aki Tuomi wrote: > On 18.10.2016 14:16, Arkadiusz Mi?kiewicz wrote: > > On Monday 17 of October 2016, KT Walrus wrote: > >>> On Oct 17, 2016, at 2:41 AM, Arkadiusz Mi?kiewicz <arekm at maven.pl> > >>> wrote: > >>> > >>> On Monday 30 of May 2016, Arkadiusz Mi?kiewicz wrote: > >>>> Is there

In tools except guestfish, we don't use ncurses, or even curses, just 2 termcap functions and a global variable. These are provided by libtinfo, so just link to that. In guestfish we use readline which needs ncurses. Leave that alone. --- builder/Makefile.am | 2 +- configure.ac | 12 ++++++------ customize/Makefile.am | 2 +- mllib/Makefile.am | 6 +++---

On Friday 11 of November 2016, Felipe Gasper wrote: > Hello, > > We?re rolling out large SNI deployments for our mail servers. Each domain > gets an entry like this in the config: > > local_name mail.foo.com { > ssl_cert = </ssl/domain_tls/*.foo.com/combined > ssl_key = </ssl/domain_tls/*.foo.com/combined > } Lack of glob/regexp support here is also a

Can you provide some details on what those openssl commands returned? Aki On 20.07.2018 12:14, Martin Johannes Dauser wrote: > Hi, > > I recognised some funny behaviour on my server. IMAP clients which > won't send an Server Name Indication (SNI) sometimes get the wrong > certificate. I would expect that those clients always get the default > certificate (of my new

> On November 11, 2016 at 12:22 PM Arkadiusz Mi?kiewicz <arekm at maven.pl> wrote: > > > On Friday 11 of November 2016, Felipe Gasper wrote: > > Hello, > > > > We?re rolling out large SNI deployments for our mail servers. Each domain > > gets an entry like this in the config: > > > > local_name mail.foo.com { > > ssl_cert =