Package: stunnel4
Version: 5.71
Epoch: 1
Revision: 1
Maintainer: Daniel Johnson <daniel@daniel-johnson.org>
BuildDepends: <<
	fink (>= 0.28-1),
	fink-package-precedence,
	openssl300-dev
<<
Depends: openssl300-shlibs
Conflicts: stunnel-egd, stunnel
Replaces: stunnel-egd, stunnel
Source: ftp://stunnel.mirt.net/stunnel/stunnel-%v.tar.gz
Source-Checksum: SHA256(f023aae837c2d32deb920831a5ee1081e11c78a5d57340f8e6f0829f031017f5)
ConfigureParams: <<
	--with-ssl=%p \
	--with-bashcompdir=%p/share/bash-completion/completions
<<
CompileScript: <<
	%{default_script}
	fink-package-precedence .
<<
InstallScript: <<
	make install DESTDIR=%d
<<
Shlibs: !%p/lib/stunnel/libstunnel.dylib
DocFiles: AUTHORS.md BUGS.md COPY* CREDITS.md NEWS.md PORTS.md README.md TODO.md ./tools/* ./doc/*.html
Description: Tool to encrypt TCP connections
DescDetail: <<
Allows you to encrypt arbitrary TCP connections inside SSL. It can
allow you to secure non-SSL aware daemons and protocols (like POP, 
IMAP, LDAP, etc) by having it provide the encryption, requiring no 
changes to the daemon's code.
<<
DescUsage: <<
If you want to use stunnel to secure services you need an .pem file. To have 
it seperated from the openssl files it is stored in %p/etc/stunnel. You can 
easily create it using openssl. e.g. (one line:) openssl req  -new -x509 -days 
365 -out %p/etc/stunnel/stunnel.pem -keyout  %p/etc/stunnel/stunnel.pem 
then openssl x509 -subject -dates -fingerprint -noout -in 
%p/etc/stunnel/stunnel.pem It is a good idea to look at the stunnel homepage 
and in %p/share/doc/stunnel4 for more information.
<<
DescPort: <<
To avoid interactivity in the install process there must be no .pem file created.
This has to be done later if stunnel is meant to be used secure services, could
be needed in some cases stunnel is used as client. 
<<
DescPackaging: <<
 Hardcode bash-completions path so we don't need
 BuildDepends:bash-completion,pkgconfig
<<
License: GPL2+
Homepage: http://www.stunnel.org/