Hi,
This may be a little bit off-topic, but does anyone here use stunnel with
pan? My connections to stunnel (in pan) are always refused by libwrap. I was
looking for the right rule to add to /etc/hosts.allow but nothing seems to
work aside from "ALL : ALL" (which is obviously not good) and "nntps:
KNOWN". Is the latter reasonable? The hosts_access(5) manpage is confusing
to say the least. It mentions that daemon (the first token on any line) is
the name of the daemon running the process, …
[View More]which would be "stunnel" in my
case, but using "stunnel : LOCAL" or even "stunnel : ALL" doesn't work. The
rule that seems to work, as mentioned, is "nntps : KNOWN" ("nntps" being the
group name in stunnel.conf).
What's even more confusing to me is that "nntps : LOCAL" does not work
either. Nor does "nntps : localhost 127.0.0.1", "nntps : localhost", "nntps
: 127.0.0.1", or "nntps : 192.168.1.". Pan is running on the same machine as
stunnel so all connections must be coming from localhost. Why do these rules
not trigger?
Either way, I'd like to know the "least permissive" hosts.allow rule that
would allow me to connect to my news provider from pan, and/or whether
"nntps : KNOWN" is a safe option.
Thanks,
Yousef
[View Less]
Hi,
I noticed that parsing of HTTP header fields is not robust enough and
not RFC compliant - and that way it casues incompatibility with
Microsoft TMG proxy with NTLM authentication.
The symptom is "Proxy-Authenticate: Invalid Content-Length" message
while the header received is "Content-Length: 0 " <- note trailing
spaces.
The responsible piece of code is in protocol.c:
if(tmpstr==line+16 || *tmpstr || content_length<0) {
(tmpstr contains trailing spaces in this case).
…
[View More]According to RFC 7230 trailing space is allowed and should be discarded
by parser:
A field value might be preceded and/or followed by optional
whitespace (OWS); a single SP preceding the field-value is preferred
for consistent readability by humans. The field value does not
include any leading or trailing whitespace: OWS occurring before the
first non-whitespace octet of the field value or after the last
non-whitespace octet of the field value ought to be excluded by
parsers when extracting the field value from a header field.
best regards
--
Marcin Gryszkalis, PGP 0xA5DBEEC7
jabber jid:mg@fork.pl
[View Less]
Hi,
I'm new to stunnel and I'd like to compile it to ARM and x86 platforms. I
downloaded the stunnel-5.17 package and I'm using the build-android.sh and
android-ndk-r10e script to compile it:
../../configure
--with-sysroot=/home/ptofanelli/android-ndk-r10e/platforms/android-18/arch-arm/
--build=i686-pc-linux-gnu --host=arm-linux-androideabi --prefix=/data/local
I'm getting the message "The C compiler cannot create executables" and
checking the logs I've found that the problem is this:
…
[View More]configure:3538: arm-linux-androideabi-gcc conftest.c >&5
/home/ptofanelli/android-ndk-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld:
error: cannot open crtbegin_dynamic.o: No such file or directory
/home/ptofanelli/android-ndk-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld:
error: cannot open crtend_android.o: No such file or directory
/home/ptofanelli/android-ndk-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld:
error: cannot find -lc
/home/ptofanelli/android-ndk-r10e/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/ld:
error: cannot find -ldl
collect2: error: ld returned 1 exit status
I searched for this problem and a topic in stackoverflow (
http://stackoverflow.com/questions/16795583/android-error-cannot-open-crtbe…)
is said that the problem is the sysroot, so I tried to use the option
--with-sysroot, but I'm getting the same problem.
Can you help me?
Thanks and regards,
Pio Tofanelli
[View Less]
Hi,
We cannot get stunnel SMTP to work with Office 365 mail server. We are using Stunnel 5.13 and below are the config file content and the the client PC logs. The mail server logs do not reveal anything more.
Two observations of the test setup:
1) Using e.g. Mozilla Firebird mail client directly SLL/SMTP on the same PC connection to same Office 365 mail server works ok, but via Stunnel it outputs the error log below.
2) Also, on the same PC, SSL/SMTP connection via stunnel to …
[View More]Gmail server works ok.
Stunnel conf-file:
==============
output = stunnel_log.txt
debug = debug
cert = tstunnel.pem
client = yes
[SSMTP]
accept = 127.0.0.1:54500
connect = xxx.xxx.xxx.xxx:587 (Hannu V: removed IP address from this mail)
protocol = smtp
Client PC logs:
===========
2015.04.28 09:17:36 LOG7[ui]: No limit detected for the number of clients
2015.04.28 09:17:36 LOG5[ui]: stunnel 5.13 on x86-pc-msvc-1500 platform
2015.04.28 09:17:36 LOG5[ui]: Compiled/running with OpenSSL 1.0.2a 19 Mar 2015
2015.04.28 09:17:36 LOG5[ui]: Threading:WIN32 Sockets:SELECT,IPv6 TLS:ENGINE,FIPS,OCSP,PSK,SNI
2015.04.28 09:17:36 LOG7[ui]: errno: (*_errno())
2015.04.28 09:17:36 LOG5[ui]: Reading configuration from file tstunnelSmtp_SAUX1_0.conf
2015.04.28 09:17:36 LOG5[ui]: UTF-8 byte order mark not detected
2015.04.28 09:17:36 LOG5[ui]: FIPS mode disabled
2015.04.28 09:17:36 LOG7[ui]: Compression disabled
2015.04.28 09:17:36 LOG7[ui]: PRNG seeded successfully
2015.04.28 09:17:36 LOG6[ui]: Initializing service [SSmtp]
2015.04.28 09:17:36 LOG6[ui]: Loading certificate from file: tstunnel.pem
2015.04.28 09:17:36 LOG6[ui]: Loading key from file: tstunnel.pem
2015.04.28 09:17:36 LOG7[ui]: Private key check succeeded
2015.04.28 09:17:36 LOG7[ui]: SSL options: 0x03000004 (+0x03000000, -0x00000000)
2015.04.28 09:17:36 LOG5[ui]: Configuration successful
2015.04.28 09:17:36 LOG7[ui]: Listening file descriptor created (FD=448)
2015.04.28 09:17:36 LOG7[ui]: Service [SSmtp] (FD=448) bound to 127.0.0.1:8030
2015.04.28 09:17:36 LOG7[ui]: Service [SSmtp] accepted (FD=456) from 127.0.0.1:54500
2015.04.28 09:17:36 LOG7[ui]: Creating a new thread
2015.04.28 09:17:36 LOG7[ui]: New thread created
2015.04.28 09:17:36 LOG7[0]: Service [SSmtp] started
2015.04.28 09:17:36 LOG5[0]: Service [SSmtp] accepted connection from 127.0.0.1:54500
2015.04.28 09:17:36 LOG6[0]: s_connect: connecting xxx.xxx.xxx.xxx:587 (Hannu V: removed IP address from this mail)
2015.04.28 09:17:36 LOG7[0]: s_connect: s_poll_wait connecting xxx.xxx.xxx.xxx:587 : waiting 10 seconds (Hannu V: removed IP address from this mail)
2015.04.28 09:17:37 LOG5[0]: s_connect: connected connecting xxx.xxx.xxx.xxx:587 (Hannu V: removed IP address from this mail)
2015.04.28 09:17:37 LOG5[0]: Service [SSmtp] connected remote server from yyy.yyy.yyy.yyy:54503 (Hannu V: removed IP address from this mail)
2015.04.28 09:17:37 LOG7[0]: Remote socket (FD=472) initialized
2015.04.28 09:17:37 LOG7[0]: <- 220 NNN.outlook.office365.com Microsoft ESMTP MAIL Service ready at Tue, 28 Apr 2015 14:17:38 +0000
2015.04.28 09:17:37 LOG7[0]: -> 220 NNN.outlook.office365.com Microsoft ESMTP MAIL Service ready at Tue, 28 Apr 2015 14:17:38 +0000
2015.04.28 09:17:37 LOG7[0]: -> EHLO localhost
2015.04.28 09:17:37 LOG7[0]: <- 250-NNN.outlook.office365.com Hello [xxx.xxx.xxx.161] (Hannu V: removed IP address from this mail)
2015.04.28 09:17:37 LOG7[0]: <- 250-SIZE 157286400
2015.04.28 09:17:37 LOG7[0]: <- 250-PIPELINING
2015.04.28 09:17:37 LOG7[0]: <- 250-DSN
2015.04.28 09:17:37 LOG7[0]: <- 250-ENHANCEDSTATUSCODES
2015.04.28 09:17:37 LOG7[0]: <- 250-STARTTLS
2015.04.28 09:17:37 LOG7[0]: <- 250-8BITMIME
2015.04.28 09:17:37 LOG7[0]: <- 250-BINARYMIME
2015.04.28 09:17:37 LOG7[0]: <- 250 CHUNKING
2015.04.28 09:17:37 LOG7[0]: -> STARTTLS
2015.04.28 09:17:37 LOG7[0]: <- 220 2.0.0 SMTP server ready
2015.04.28 09:17:37 LOG6[0]: SNI: sending servername: NNN.office365.com
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): before/connect initialization
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): SSLv2/v3 write client hello A
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): SSLv3 read server hello A
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): SSLv3 read server certificate A
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): SSLv3 read server key exchange A
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): SSLv3 read server certificate request A
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): SSLv3 read server done A
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): SSLv3 write client certificate A
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): SSLv3 write client key exchange A
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): SSLv3 write certificate verify A
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): SSLv3 write change cipher spec A
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): SSLv3 write finished A
2015.04.28 09:17:37 LOG7[0]: SSL state (connect): SSLv3 flush data
2015.04.28 09:17:37 LOG3[0]: SSL_connect: Peer suddenly disconnected
2015.04.28 09:17:37 LOG5[0]: Connection reset: 0 byte(s) sent to SSL, 0 byte(s) sent to socket
2015.04.28 09:17:37 LOG7[0]: Remote socket (FD=472) closed
2015.04.28 09:17:37 LOG7[0]: Local socket (FD=456) closed
2015.04.28 09:17:37 LOG7[0]: Service [SSmtp] finished (0 left)
--- Hannu
[View Less]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dear Users,
While reading various 3rd party stunnel tutorials I noticed that they
either don't configure authentication, or they recommend insecure
configurations.
I wrote a short overview of authentication methods available in stunnel:
https://www.stunnel.org/auth.html
Proper authentication is essential to TLS security.
Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/…
[View More]iQIcBAEBAgAGBQJVVXk5AAoJEC78f/DUFuAUN/QP/3m4HX4zWS8SehukDNWw54AB
ySAT+XmT8SEo/iuGer/CRYbUWoMDpmwaI9x+whXMg+EBsxGd+nmyE9fkFiFSqOsV
vnXc14zuMkQYorWbGtduXdnQ0/jQzWPDOIeKgpyXIsN/OvEhx1A6med9Go/SqaFz
couW55wysqpJ9a+3YMtxIjLoCMzIGOZ8TKIHWJiZaBcgp93YCABeoE5hKR4RlxVj
OrgHhuyA8yz1EIYUPKTEMuJwqnCl9Mk3FVskKIXgfEcxBzism2n/xJpEIYAWVPRW
N8JaaZDojk6dt5oMiMzXUeobigZ82SKuV9MG3aQjuxXAP7IX2vuOa6rQ/85T1OFI
PMZMKENM1aAcOVpiq/4OMNKhIG+OuhDm/dla5NC8lsfxDuJ3YESVp/Z0VeW1EWYA
BFHxjGw8OA65izTYcvJKl1j7flfSgRELOCf1SMakR+VIUhkWlPQjdHWuW2V5NKgv
5aU0fwPGEpudKdsLFzgaYzhVPjTNfavl8k+xUWHOQyrNvEM9SNbOTyorxY7QA2aQ
uyAOrUF8whboBTX59/3gXYI9vaepvT00ktCtQEz3XelkYT9SzCRYV+I+mUqquBd+
0JQdiSMvOzfNraxT03rzYA6h/Iey9+tj9WnffpmYU5eyTt2bCp+xavzCyEmdQZlq
4LfAPgFYII9+59444dY2
=m51O
-----END PGP SIGNATURE-----
[View Less]
Given a lack of other suggestions here and elsewhere that yielded any
progress, I decided to download the current source and attempt to build
it on my system. I didn't see a routine to check for prerequisites
being met, so I wound up running ./configure several times and adding
the libssl-dev, libwrap0-dev and libsystemd-daemon-dev packages based on
what I saw in the output. Perhaps a check routine could be added later?
I then ran make and the output contains neither errors nor warnings, …
[View More]so
that looks good. As suggested in the INSTALL file, I next ran make
check and received neither errors nor warnings.
At this point the next step appears to be make install as root, but I am
wondering if I should uninstall the stunnel4 package from the repository
first. I am also wondering if I can simply use the existing
/etc/stunnel/stunnel.conf that I included in my first post in this
thread or if I should start over with one of the examples included with
this version.
I would appreciate input from the list on this. If you want to see
further details, such as ./configure or make outputs or configuration
files just let me know and I will put them in a follow-up post.
Dave
[View Less]
Thanks!
I applied the patch to tls.c and I'm able to create sessions with no
problem.
The version of OpenSSL provided by IBM is built off the 1.0.1e codebase,
with backported security fixes via "iFixes" for announced CVEs. They
apparently don't backport new functionality or maybe even non-CVE bugfixes.
I'm guessing an un-patched stunnel 5.17 would work once/if they release
OpenSSL built off 1.0.1j or later.
> On Tue, May 12, 2015 at 3:40 PM, Michal Trojnara <Michal.Trojnara(a)mirt.…
[View More]net
> > wrote:
>
>> On 12.05.2015 18:29, Eckert, Doug wrote:
>> > With that in mind, I compiled stunnel v5.03 with same OpenSSL 1.0.1.513
>> > and iFix IV71446m9a applied as with the v5.17 attempt. I'm able to
>> > create sessions with no problem. The internal error/bad magic does not
>> > occur.
>>
>> Additional security checks to the OpenSSL memory management functions
>> were introduced in stunnel 5.09. The enclosed patch disables them in
>> the latest stunnel 5.17.
>>
>> Mike
>>
>> _______________________________________________
>> stunnel-users mailing list
>> stunnel-users(a)stunnel.org
>> https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
>>
>>
>
>
> --
>
>
>
>
[View Less]