This package was debianized by Wouter Verhelst <wouter@debian.org> in early
2005. It was downloaded from
http://www.belgium.be/zip/eid_datacapture_nl.html

Upstream authors: Zetes Belgium N.V.; contact: Stef Hoeben <Hoeben.S@zetes.com>

The copyright of this software was assigned to FedIct, the ICT services of the
Belgian Federal government.

A verbatim copy of the license.txt file, which is part of the upstream 'SDK'
package but refers to the SDK package and this package, follows:

-----
IMPORTANT -- READ CAREFULLY BEFORE USING THIS SOFTWARE: Do not install, 
download or use the eID Toolkit software until you have read and accepted this 
Agreement (including its Exhibit). By clicking on the "Accept" button, 
installing, downloading or otherwise using the eID Toolkit you agree to to be 
bound by the terms of this Agreement (including its Exhibit). If you do not 
agree to the terms of this Agreement (and/or its Exhibit), click on the 
"cancel" button and/or do not install the eID Toolkit software.


                  eID Run-time Software License
                  =============================



Whereas this eID Toolkit software is released in a final version;

Whereas this eID Toolkit is being provided by Fedict for no fee and for wide 
use by any third party under the terms and conditions of this Agreement;

WHEREAS THIS AGREEMENT REFERS TO AN OPEN-SOURCE LIBRARY, BEING ITSELF BASED ON 
OPEN-SOURCE SOFTWARE, THE TERMS AND CONDITIONS OF WHICH ARE INCLUDED IN THE 
EXHIBIT, WHICH NEED TO BE COMPLIED WITH BY ANY PARTY USING, REPRODUCING, 
COPYING, MODIFYING, DISPLAYING AND DISTRIBUTING THE EID TOOLKIT;

WHEREAS THIS AGREEMENT DOES NOT TAKE AWAY YOUR FREEDOM TO SHARE THE EID 
TOOLKIT AND CHANGE IT IN ORDER TO ENABLE ITS WIDEST POSSIBLE ROLL-OUT TO OTHER 
POTENTIAL USERS, PROVIDED THAT SUCH USE IN RELATION TO THE EID TOOLKIT 
COMPLIES WITH THE TERMS AND CONDITIONS SET OUT IN THIS AGREEMENT (INCLUDING 
ITS EXHIBIT).


Article 1: Grant of license

The terms of this License Agreement (“License Agreement”) between you, the 
licensee, and the Belgian Federal Government (“Fedict"), the licensor, allow 
you, subject to the terms and limits set forth in this License Agreement and 
its Exhibit (collectively "Agreement"), to receive from Fedict a world-wide, 
royalty-free, non-exclusive, perpetual and transferable right of using, 
reproducing, copying, modifying, displaying and distributing the software set 
out in the Exhibit ("eID Toolkit ").


Article 2: Warranties of Licensor and Disclaimers

2.1. Since the eID Toolkit has not specifically been created and tailored to 
address, and has not been based on, your specific needs, Fedict does not 
warrant that the eID Toolkit will meet your specific requirements or that the 
operation of the eID Toolkit will operate in the specific combinations which 
you may select for use. As no software is error-free, Fedict cannot guarantee 
that the eID Toolkit will operate without interruption or be error free. 

2.2. Without prejudice to the above paragraph, this eID Toolkit is provided by 
Fedict "AS IS" and any expressed or implied warranties other than those laid 
down in provision 2.1, including, but not limited to, the implied warranties 
of merchantability and fitness for a particular purpose are disclaimed. 

2.3 This Agreement does not entitle you to receive any maintenance, support 
(be it telephone, fax or email) or any other assistance with respect to the 
eID Toolkit or with respect to any alteration made on the eID Toolkit in any 
form whatsoever, including, but not limited to additions, upgrades, 
improvements to the substance and structure of the software ("Modifications").

Article 3: Licensee obligations

3.1. Any use, including, but not limited to, reproduction, copy, modification, 
display and distribution, is subject to compliance with the terms of this 
Agreement. You warrant that you will comply with the terms of this Agreement 
including the licenses governing the libraries or codes developed (and 
protected by intellectual property rights as the case may be) by third 
parties, which have been used wholly or in part for the development of the eID 
Toolkit, being embedded in the eID application, linked to, being integrated 
into or compiled with other libraries and codes to form the eID Toolkit 
("Third-Party Work").

3.2. You may not copy, modify, sublicense, or distribute the eID Toolkit 
otherwise than as expressly provided under this Agreement. Any attempt 
otherwise to copy, modify, sublicense or distribute the eID Toolkit is void, 
and will automatically terminate your rights under this Agreement.

3.3. Redistributions in source and binary forms, with our without 
modification, must reproduce this Agreement including the licenses governing 
the libraries or codes developed by third parties, which have been used wholly 
or in part for the development of the eID Toolkit.

3.4. The name of Fedict may not be used to endorse or promote products derived 
from this eID Toolkit without specific prior written permission.

3.5. Third parties who have received copies, or rights, from you under this 
Agreement will not have their licenses terminated if you infringe the terms of 
this Agreement, so long as such parties remain in full compliance with these 
terms. 

Article 4: Liability

4.1. Under this Agreement, Fedict shall under no circumstances, except for 
fraud or wilful misconduct, be liable for any indirect, special, incidental or 
consequential damages, or for any loss of profits, loss of data, loss of 
savings or business opportunity, trading losses, staff costs or costs of staff 
turnover, computer failure or malfunction, IT system break-down, business 
interruption or other technical or operational damage of any dimension 
whatever, or other indirect, consequential or punitive damages arising from or 
in connection with the use of the eID Toolkit or of any modified or derivative 
work, or for any other commercial damages or losses arising from the use of 
it. 

4.2. Fedict shall not be liable to indemnify you for any claims of 
intellectual property right infringement, including contributory infringement 
or inducement to infringe, of any intellectual property claimed in the eID 
Toolkit by the authors of the Third-Party Works as identified in the special 
notices in the Exhibit. You agree to indemnify, defend and hold harmless 
Fedict against any and all claims, demands, penalties, proceedings, losses, 
liabilities, damages of whatsoever nature, costs, fees and expenses of any 
kind relating to in any way directly or indirectly out of Modifications and/or 
the use of the eID Toolkit alone or in combination with other devices, 
products, software, services and/or materials, provided that Fedict notifies 
you in writing of the claim and allows you to control and reasonably 
cooperates with you in the defense of the claim and any related settlement 
negotiations.  

4.3. Fedict shall not be responsible for (i) the consequences of modifying the 
eID Toolkit, integrating the eID Toolkit in proprietary products, or using the 
eID Toolkit in combination with other devices, products, software, services 
and/or materials or (ii) determining whether you require a license to or 
additional rights from any of the Third Party Works, obtaining any such 
license on its behalf, or paying any fees relating to any such licenses, to 
the extent that such Third Party Works are claimed to be open source products.

Article 5: Termination

5.1 The Agreement and all licenses granted by the Licensor hereunder shall 
automatically terminate by law if you breach this Agreement. 

5.2 Upon termination of the Agreement, you shall cease all use of the eID 
Toolkit and shall destroy all copies of the eID Toolkit within your possession 
or control.

Article 6: General

6.1 If any term or provision of this Agreement is determined to be illegal or 
unenforceable, such term or provision shall be deemed stricken, and all other 
terms and provisions shall remain in full force and effect. Each such 
provision shall be modified by the parties to the extent necessary to make it 
valid, legal and enforceable whilst preserving the intent of and balance 
between the parties. 

6.2 This Agreement constitutes the entire understanding and agreement with 
respect to the eID Toolkit and supersedes all prior oral and written 
communications.

6.3 This Agreement shall be governed by the laws of Belgium. Any dispute that 
cannot be settled amicably shall be subject to the courts of Brussels.

Exhibit
The Belgian eID Run-time– see Belgian eID Run-time User's Guide – consist of
?	The Belgian eID Toolkit
?	The Belgian e-ID Security Middleware
1.2	Third-party licenses
1.2.1	GNU Lesser General Public License
This license is used by several open source products. We will refer to it when 
applicable.

	On Debian GNU/Linux systems, the LGPL can be found in
	/usr/share/common-licenses/LGPL-2.1. It is part of the upstream
	'license.txt' file, as it applies to the opensc (and thus belpic)
	source.

1.2.2	OpenSSL
This run-time uses the OpenSSL Toolkit developed by the OpenSSL Project 
(http://www.openssl.org/).
Here is a copy of the license (from 
http://www.openssl.org/source/license.html):
LICENSE ISSUES
  The OpenSSL toolkit stays under a dual license, i.e. both the conditions 
of   the OpenSSL License and the original SSLeay license apply to the toolkit. 
See below for the actual license texts. Actually both licenses are BSD-style   
Open Source licenses. In case of any license issues related to OpenSSL please 
contact openssl-core@openssl.org.

OpenSSL License
Copyright (c) 1998-2003 The OpenSSL Project.  All rights reserved.
Redistribution and use in source and binary forms, with or without 
modification, are permitted provided that the following conditions are met:

 1. Redistributions of source code must retain the above copyright notice, 
this list of conditions and the following disclaimer.

 2. Redistributions in binary form must reproduce the above copyright notice, 
this list of conditions and the following disclaimer in the documentation 
and/or other materials provided with the distribution.

 3. All advertising materials mentioning features or use of this software must 
display the following acknowledgment: "This product includes software 
developed by the OpenSSL Project for use in the OpenSSL Toolkit. 
(http://www.openssl.org/)"

 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to 
endorse or promote products derived from this software without prior written 
permission. For written permission, please contact openssl-core@openssl.org.

 5. Products derived from this software may not be called "OpenSSL" nor may 
"OpenSSL" appear in their names without prior written permission of the 
OpenSSL Project.

 6. Redistributions of any form whatsoever must retain the following 
acknowledgment: "This product includes software developed by the OpenSSL 
Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"

THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED 
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES 
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO 
EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, 
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, 
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY 
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, 
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes cryptographic software written by Eric Young 
(eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).

Original SSLeay License
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved.

 This package is an SSL implementation written by Eric Young 
(eay@cryptsoft.com). The implementation was written so as to conform with 
Netscapes SSL.

 This library is free for commercial and non-commercial use as long as the 
following conditions are aheared to.  The following conditions apply to all 
code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; 
not just the SSL code.  The SSL documentation included with this distribution 
is covered by the same copyright terms except that the holder is Tim Hudson 
(tjh@cryptsoft.com).

 Copyright remains Eric Young's, and as such any Copyright notices in the code 
are not to be removed. If this package is used in a product, Eric Young should 
be given attribution as the author of the parts of the library used. This can 
be in the form of a textual message at program startup or in documentation 
(online or textual) provided with the package.

 Redistribution and use in source and binary forms, with or without 
modification, are permitted provided that the following conditions are met: 1. 
Redistributions of source code must retain the copyright notice, this list of 
conditions and the following disclaimer. 2. Redistributions in binary form 
must reproduce the above copyright notice, this list of conditions and the 
following disclaimer in the documentation and/or other materials provided with 
the distribution. 3. All advertising materials mentioning features or use of 
this software must display the following acknowledgement: "This product 
includes cryptographic software written by Eric Young (eay@cryptsoft.com)" The 
word 'cryptographic' can be left out if the rouines from the library being 
used are not cryptographic related :-). 4. If you include any Windows specific 
code (or a derivative thereof) from the apps directory (application code) you 
must include an acknowledgement: "This product includes software written by 
Tim Hudson (tjh@cryptsoft.com)"

 THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED 
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO 
EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF 
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, 
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

 The licence and distribution terms for any publically available version or 
derivative of this code cannot be changed.  i.e. this code cannot simply be 
copied and put under another distribution licence [including the GNU Public 
Licence.]
1.2.3	OpenSC
This run-time uses the OpenSC Toolkit developed by the OpenSC Project 
(http://www.opensc.org/).
This toolkit is released under the “GNU Lesser General Public License” (see 
7.2.1) (included in the distribution package http://www.opensc.org/cgi-
bin/cvsweb/opensc/COPYING?rev=1.2&content-type=text/x-cvsweb-markup):
1.2.5	libstdc
This run-time uses the libstdc++ run-time libraries developed by the Gnu CC 
Project (http://www.gnucc.org/).
Here is a copy of the license (from 
http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/license.html):
The Code: Runtime GPL
The source code of libstdc++-v3 is distributed under version 2 of the GNU 
General Public License 
(http://gcc.gnu.org/onlinedocs/libstdc++/17_intro/COPYING), with the so-called 
"runtime exception," as follows (or see any header or implementation file):
As a special exception, you may use this file as part of a free software 
library without restriction.  Specifically, if other files instantiate 
templates or use macros or inline functions from this file, or you compile 
this file and link it with other files to produce an executable, this file 
does not by itself cause the resulting executable to be covered by the GNU 
General Public License.  This exception does not however invalidate any other 
reasons why the executable file might be covered by the GNU General Public 
License.

Hopefully that text is self-explanatory. If it isn't, you need to speak to 
your lawyer, or the Free Software Foundation. 

Q: So any program which uses libstdc++ falls under the GPL? 
A: No. The special exception permits use of the library in proprietary 
applications. 

Q: How is that different from the GNU {Lesser,Library} GPL? 
A: The LGPL requires that users be able to replace the LGPL code with a 
modified version; this is trivial if the library in question is a C shared 
library. But there's no way to make that work with C++, where much of the 
library consists of inline functions and templates, which are expanded inside 
the code that uses the library. So to allow people to replace the library 
code, someone using the library would have to distribute their own source, 
rendering the LGPL equivalent to the GPL. 

Q: I see. So, what restrictions are there on programs that use the library? 
A: None. We encourage such programs to be released as open source, but we 
won't punish you or sue you if you choose otherwise.