[gentoo-commits] dev/alexxy:master commit in: net-dialup/accel-pptp/, sys-auth/fingerprint-gui/, sys-apps/maemo-flasher35/, ...

[Alexey Shvetsov]

commit:     301dde8243307d3c8be875541ea05172a41108be
Author:     Alexey Shvetsov <alexxy <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 26 21:32:46 2011 +0000
Commit:     Alexey Shvetsov <alexxy <AT> gentoo <DOT> org>
CommitDate: Sat Nov 26 21:32:46 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=dev/alexxy.git;a=commit;h=301dde82

Moved to betagarden

Signed-off-by: Alexey Shvetsov <alexxy <AT> gentoo.org>

---
 licenses/Nokia-EULA                                |  255 -------
 licenses/UPEK_EULA                                 |  215 ------
 net-dialup/accel-pptp/Manifest                     |    1 -
 net-dialup/accel-pptp/accel-pptp-0.8.5.ebuild      |   95 ---
 net-dialup/accel-pptp/files/README.gentoo          |   13 -
 net-dialup/accel-pptp/files/options.pptp           |   32 -
 net-dialup/accel-pptp/files/pptpd-confd            |    5 -
 net-dialup/accel-pptp/files/pptpd-init             |   24 -
 net-dialup/accel-pptp/metadata.xml                 |    8 -
 sys-apps/maemo-flasher35/Manifest                  |    1 -
 .../maemo-flasher35/maemo-flasher35-2.5.2.2.ebuild |   38 --
 sys-auth/fingerprint-gui/Manifest                  |    1 -
 .../files/Install-step-by-step.html                |  699 --------------------
 .../fingerprint-gui/fingerprint-gui-1.00.ebuild    |   60 --
 sys-auth/upekbsapi-bin/Manifest                    |    1 -
 .../upekbsapi-bin/upekbsapi-bin-4.0.0218.ebuild    |   47 --
 16 files changed, 0 insertions(+), 1495 deletions(-)

diff --git a/licenses/Nokia-EULA b/licenses/Nokia-EULA
deleted file mode 100644
index cecfcaf..0000000
--- a/licenses/Nokia-EULA
+++ /dev/null
@@ -1,255 +0,0 @@
-THIS LICENSE COVERS THE FOLLOWING COMPONENTS
-
-Maemo Flasher tool
-
-IMPORTANT: READ CAREFULLY BEFORE INSTALLING, DOWNLOADING, OR USING
-THE SOFTWARE
-
-This Software includes some software copyrighted by Nokia Corporation or
-third parties and some Open Source Software in binary form.
-
-The Software copyrighted by Nokia or some third parties is licensed to you
-under the Nokia End-User License Agreement [see below] and distributed to
-you only in binary form.
-
-The Open Source Software is licensed and distributed under GNU General
-Public License (GPL, the GNU lesser General Public License (LGPL, aka. The GNU
-Library General Public License) and/or other copyright licenses, permissions,
-notices or disclaimers containing obligation or permission to provide the
-source code of such software with the binary / executable form delivery of
-the said software. The source code of such software are made available to
-you in accordance with the referred license terms and conditions on this
-page http://www.maemo.org. The exact license terms of GPL, LGPL and said
-certain other licenses, as well as the required copyright and other notices,
-permissions and acknowledgements are reproduced in and delivered to you as
-part of the referred source code.
-
-
-NOKIA CORPORATION END-USER SOFTWARE AGREEMENT
-
-This Software Agreement ("Agreement") is between You (either an
-individual or an entity), the End User, and Nokia Corporation ("Nokia").
-The Agreement authorizes You to use the Software specified in Clause 1
-below, which may be stored on a CD-ROM, sent to You by electronic mail,
-or downloaded from Nokia's Web pages or Servers or from other sources
-under the terms and conditions set forth below. This is an agreement on
-end-user rights and not an agreement for sale. Nokia continues to own
-the copy of the Software and the physical media contained in the sales
-package and any other copy that You are authorized to make pursuant to
-this Agreement.
-
-Read this Agreement carefully before installing, downloading, or using
-the Software.  By clicking on the "I Accept" button while installing,
-downloading, and/or using the Software, You agree to the terms and
-conditions of this Agreement.  If You do not agree to all of the
-terms and conditions of this Agreement, promptly click the "Decline"
-or "I Do Not Accept" button, cancel the installation or downloading,
-or destroy or return the Software and accompanying documentation to
-Nokia. YOU AGREE THAT YOUR USE OF THE SOFTWARE ACKNOWLEDGES THAT YOU
-HAVE READ THIS AGREEMENT, UNDERSTAND IT, AND AGREE TO BE BOUND BY ITS
-TERMS AND CONDITIONS.
-
-1. SOFTWARE.
-
-As used in this Agreement, the term "Software" means, collectively:
-(i) the software product identified above (ii) all the contents of the
-disk(s), CD-ROM(s), electronic mail and its file attachments, or other
-media with which this Agreement is provided, including the object code
-form of the software delivered via a CD-ROM, electronic mail, or Web page
-(iii) digital images, stock photographs, clip art, or other artistic
-works ("Stock Files") (iv) related explanatory written materials and
-any other possible documentation related thereto ("Documentation");
-(v) fonts, and (vi) upgrades, modified versions, updates, additions,
-and copies of the Software (collectively "Updates"), if any, licensed
-to You by Nokia under this Agreement.
-
-2. END-USER RIGHTS AND USE.
-
-Nokia grants to You non-exclusive, non-transferable end-user rights
-to install the Software on the local hard disk(s) or other permanent
-storage media of one computer and use the Software on a single computer
-or terminal at a time.
-
-3. LIMITATIONS ON END-USER RIGHTS.
-
-You may not copy, distribute, or make derivative works of the Software
-except as follows:
-
-(a) You may make one copy of the Software on magnetic media as an archival
-backup copy, provided Your archival backup copy is not installed or
-used on any computer. Any other copies You make of the Software are in
-violation of this Agreement.
-
-(b) You may not use, modify, translate, reproduce, or transfer the right
-to use the Software or copy the Software except as expressly provided
-in this Agreement.
-
-(c) You may not resell, sublicense, rent, lease, or lend the Software.
-
-(d) You may not reverse engineer, reverse compile, disassemble, or
-otherwise attempt to discover the source code of the Software (except
-to the extent that this restriction is expressly prohibited by law)
-or create derivative works based on the Software.
-
-(e) Unless stated otherwise in the Documentation, You shall not display,
-modify, reproduce, or distribute any of the Stock Files included with the
-Software. In the event that the Documentation allows You to display the
-Stock Files, You shall not distribute the Stock Files on a stand-alone
-basis, i.e., in circumstances in which the Stock Files constitute the
-primary value of the product being distributed. You should review the
-"Readme" files associated with the Stock Files that You use to ascertain
-what rights You have with respect to such materials. Stock Files may
-not be used in the production of libelous, defamatory, fraudulent,
-infringing, lewd, obscene, or pornographic material or in any otherwise
-illegal manner. You may not register or claim any rights in the Stock
-Files or derivative works thereof.
-
-(f) You agree that You shall only use the Software in a manner that
-complies with all applicable laws in the jurisdiction in which You use
-the Software, including, but not limited to, applicable restrictions
-concerning copyright and other intellectual property rights.
-
-4. COPYRIGHT.
-
-The Software and all rights, without limitation including proprietary
-rights therein, are owned by Nokia and/or its licensors and affiliates and
-are protected by international treaty provisions and all other applicable
-national laws of the country in which it is being used. The structure,
-organization, and code of the Software are the valuable trade secrets and
-confidential information of Nokia and/or its licensors and affiliates. You
-must not copy the Software, except as set forth in clause 3 (Limitations
-On End-User Rights). Any copies which You are permitted to make pursuant
-to this Agreement must contain the same copyright and other proprietary
-notices that appear on the Software.
-
-5. MULTIPLE ENVIRONMENT SOFTWARE / MULTIPLE LANGUAGE SOFTWARE / DUAL
-MEDIA SOFTWARE / MULTIPLE COPIES / UPDATES.
-
-If the Software supports multiple platforms or languages, if You receive
-the Software on multiple media, or if You otherwise receive multiple
-copies of the Software, the number of computers on which all versions
-of the Software are installed shall be one computer. You may not rent,
-lease, sublicense, lend, or transfer versions or copies of the Software
-You do not use. If the Software is an Update to a previous version of
-the Software, You must possess valid end-user rights to such a previous
-version in order to use the Update, and You may use the previous version
-for ninety (90) days after You receive the Update in order to assist
-You in the transition to the Update. After such time You no longer have
-a right to use the previous version, except for the sole purpose of
-enabling You to install the Update.
-
-6. COMMENCEMENT & TERMINATION.
-
-This Agreement is effective from the first date You install the
-Software. You may terminate this Agreement at any time by permanently
-deleting, destroying, and returning, at Your own costs, the Software, all
-backup copies, and all related materials provided by Nokia. Your end-user
-rights automatically and immediately terminate without notice from Nokia
-if You fail to comply with any provision of this Agreement. In such an
-event, You must immediately delete, destroy, or return at Your own cost,
-the Software, all backup copies, and all related material to Nokia.
-
-7. YOU ACKNOWLEDGE THAT THE SOFTWARE IS PROVIDED "AS IS" WITHOUT
-WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, AND TO THE MAXIMUM EXTENT
-PERMITTED BY APPLICABLE LAW NEITHER NOKIA, ITS LICENSORS OR AFFILIATES,
-NOR THE COPYRIGHT HOLDERS MAKE ANY REPRESENTATIONS OR WARRANTIES,
-EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
-MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE OR THAT THE SOFTWARE
-WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS, OR
-OTHER RIGHTS.  THERE IS NO WARRANTY BY NOKIA OR BY ANY OTHER PARTY THAT
-THE FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET YOUR REQUIREMENTS OR
-THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE.
-YOU ASSUME ALL RESPONSIBILITY AND RISK FOR THE SELECTION OF THE SOFTWARE
-TO ACHIEVE YOUR INTENDED RESULTS AND FOR THE INSTALLATION, USE, AND
-RESULTS OBTAINED FROM IT.
-
-8. NO OTHER OBLIGATIONS.
-
-This Agreement creates no obligations on the part of Nokia other than
-as specifically set forth herein.
-
-9. LIMITATION OF LIABILITY.
-
-TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL
-NOKIA, ITS EMPLOYEES OR LICENSORS OR AFFILIATES BE LIABLE FOR ANY LOST
-PROFITS, REVENUE, SALES, DATA, OR COSTS OF PROCUREMENT OF SUBSTITUTE GOODS
-OR SERVICES, PROPERTY DAMAGE, PERSONAL INJURY, INTERRUPTION OF BUSINESS,
-LOSS OF BUSINESS INFORMATION, OR FOR ANY SPECIAL, DIRECT, INDIRECT,
-INCIDENTAL, ECONOMIC, COVER, PUNITIVE, SPECIAL, OR CONSEQUENTIAL
-DAMAGES, HOWEVER CAUSED AND WHETHER ARISING UNDER CONTRACT, TORT,
-NEGLIGENCE, OR OTHER THEORY OF LIABILITY ARISING OUT OF THE USE OF
-OR INABILITY TO USE THE SOFTWARE, EVEN IF NOKIA OR ITS LICENSORS OR
-AFFILIATES ARE ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. BECAUSE
-SOME COUNTRIES/STATES/JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF
-LIABILITY, BUT MAY ALLOW LIABILITY TO BE LIMITED, IN SUCH CASES, NOKIA,
-ITS EMPLOYEES OR LICENSORS OR AFFILIATES' LIABILITY SHALL BE LIMITED
-TO U.S. $50.  Nothing contained in this Agreement shall prejudice the
-statutory rights of any party dealing as a consumer.  Nothing contained
-in this Agreement limits Nokia's liability to You in the event of death
-or personal injury resulting from Nokia's negligence. Nokia is acting
-on behalf of its employees and licensors or affiliates for the purpose
-of disclaiming, excluding, and/or restricting obligations, warranties,
-and liability as provided in this clause 9, but in no other respects
-and for no other purpose.
-
-10. TECHNICAL SUPPORT.
-
-Nokia has no obligation to furnish You with technical support unless
-separately agreed in writing between You and Nokia.
-
-11. EXPORT CONTROL.
-
-The Software, including technical data, includes cryptographic software
-subject to export controls under the U.S. Export Administration
-Regulations ("EAR") and may be subject to import or export controls in
-other countries. The EAR prohibits the use of the Software and technical
-data by a Government End User, as defined hereafter, without a license
-from the U.S. government. A Government End User is defined in Part
-772 of the EAR as "any foreign central, regional, or local government
-department, agency, or other entity performing governmental functions;
-including governmental research institutions, governmental corporations,
-or their separate business units (as defined in part 772 of the EAR)
-which are engaged in the manufacture or distribution of items or
-services controlled on the Wassenaar Munitions List, and international
-governmental organizations. This term does not include: utilities
-(telecommunications companies and Internet service providers; banks
-and financial institutions; transportation; broadcast or entertainment;
-educational organizations; civil health and medical organizations; retail
-or wholesale firms; and manufacturing or industrial entities not engaged
-in the manufacture or distribution of items or services controlled on
-the Wassenaar Munitions List.)" You agree to strictly comply with all
-applicable import and export regulations and acknowledge that You have
-the responsibility to obtain licenses to export, re-export, transfer, or
-import the Software. You further represent that You are not a Government
-End User as defined above, and You will not transfer the Software to
-any Government End User without a license.
-
-12. NOTICES.
-
-All notices and return of the Software and Documentation should be
-delivered to:
-
-NOKIA CORPORATION 
-P.O. Box 100 
-FIN-00045 
-NOKIA GROUP FINLAND
-
-13.  APPLICABLE LAW & GENERAL PROVISIONS.
-
-This Agreement is governed by the laws of Finland.  All disputes
-arising from or relating to this Agreement shall be settled by a single
-arbitrator appointed by the Central Chamber of Commerce of Finland. The
-arbitration procedure shall take place in Helsinki, Finland in the English
-language. If any part of this Agreement is found void and unenforceable,
-it will not affect the validity of the balance of the Agreement, which
-shall remain valid and enforceable according to its terms. This Agreement
-may only be modified in writing by an authorized officer of Nokia.
-
-This is the entire agreement between Nokia and You relating to the
-Software, and it supersedes any prior representations, discussions,
-undertakings, end-user agreements, communications, or advertising relating
-to the Software.
-
-PLEASE SUBMIT ANY ACCOMPANYING REGISTRATION FORMS TO RECEIVE REGISTRATION
-BENEFITS WHERE APPLICABLE
-

diff --git a/licenses/UPEK_EULA b/licenses/UPEK_EULA
deleted file mode 100644
index d6a5891..0000000
--- a/licenses/UPEK_EULA
+++ /dev/null
@@ -1,215 +0,0 @@
-END-USER LICENSE AGREEMENT
-for
-UPEK, INC. SDK SOFTWARE PRODUCTS
-IMPORTANT, PLEASE READ CAREFULLY
-YOU MAY NOT INSTALL OR USE THIS UPEK SOFTWARE PRODUCT UNLESS YOU HAVE
-CAREFULLY READ THE TERMS AND CONDITIONS SET FORTH BELOW AND INDICATE
-YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS BY CLICKING ON THE “I
-ACCEPT” BUTTON AT THE END OF THIS SCREEN.
-This End-User License Agreement (“EULA”) represents the understanding between UPEK, Inc. and its
-successors and assigns (“UPEK”) and you (either an individual person or a single legal entity, referred to in
-this EULA as “You” or “Your”) and governs the use of the UPEK software product that accompanies this
-EULA, including any associated media, printed materials and electronic documentation (the “Software
-Product”), except to the extent a particular program is the subject of a separate written agreement with
-UPEK. The Software Product may also include any software updates, add-on components, stencils,
-templates, shapes, symbols, web services and/or supplements that UPEK may provide to You or make
-available to You, or that You obtain from the use of features or functionality of the Software Product, after
-the date You obtain Your initial copy of the Software Product (whether by delivery of a CD, permitted
-downloading from the Internet or a dedicated web site, or otherwise), to the extent that such items are not
-accompanied by a separate license agreement or terms of use.
-BY INSTALLING OR USING THE SOFTWARE PRODUCT, YOU ARE CONSENTING TO BE
-BOUND BY THIS EULA. IF YOU DO NOT AGREE TO ALL OF THE TERMS AND
-CONDITIONS OF THIS EULA, THEN (A) DO NOT INSTALL OR USE THE SOFTWARE
-PRODUCT, AND (B) YOU MAY RETURN THE SOFTWARE PRODUCT TO THE PERSON
-WHO PROVIDED IT TO YOU FOR A FULL REFUND. Should You have any questions concerning
-this EULA, or if You desire to contact UPEK for any reason, please contact the UPEK subsidiary serving
-Your country/region.
-1. GRANT OF LICENSE. Subject to the terms and conditions of this EULA and Your payment of all
-applicable fees for the Software Product, UPEK and its suppliers hereby grant to You, and You hereby
-accept a nonexclusive license to install and use copies of the Software Product, on a device, workstation,
-terminal, PC peripheral or other digital, electronic or analog device embedding a UPEK fingerprint sensor
-(a “UPEK-Enabled Device”), for the purpose of designing, creating testing, and distributing Your software
-product(s). If this Software Product contains documentation that is provided only in electronic form, You
-may print one copy of such electronic documentation; provided, however, that You may not copy the
-printed materials accompanying the Software Product.
-2. ADDITIONAL LICENSE RIGHTS – REDISTRIBUTABLE CODE. In addition to the rights granted in
-section 1, certain portions of the product are redistributable by You as part of Your copyrighted software
-application. These additional license rights are conditioned upon your compliance with the distribution
-requirements and license restrictions described in Section 3.
-2.1 Sample Code. UPEK grants you the right to use and modify the source code version of those portions
-of the Product identified as "Samples" in REDISTRIBUTABLES.TXT or elsewhere in the Product
-("Sample Code") for the sole purposes of designing, developing, testing and distributing your software
-product(s), and to reproduce and distribute the Sample Code, along with any modifications thereof, in
-object and/or source code form. For applicable redistribution requirements for Sample Code, see
-Section 3.1 below.
-2.2 Redistributable Object-Code. UPEK grants you a nonexclusive right to reproduce and distribute the
-object code of any portion of the Product listed in REDISTRIBUTABLES.TXT ("Redistributable Code").
-For applicable redistribution requirements for Redistributable Code, see Section 3.1, below.
-
-MP1:942657.3
-
-3. LICENSE RESTRICTIONS -- DISTRIBUTION REQUIREMENTS. If you choose to exercise your
-rights under Section 2, any redistribution by you requires compliance with the following terms, as
-appropriate.
-3.1 Redistributable Code-Standard.
-(a) If you are authorized and choose to redistribute Sample Code and/or Redistributable Object-Code, as
-described in Section 2, you agree: (i) except as otherwise noted in Section 2.1 (Sample Code), to distribute
-the Redistributables only in object code form and in conjunction with and as a part of a copyrighted
-software application product developed by you that adds significant and primary functionality to the
-Redistributables ("Licensed Product"); (ii) to display your own valid copyright notice which shall be
-sufficient to protect UPEK’s copyright in the Product; (iii) not to remove or obscure any copyright,
-trademark or patent notices that appear on the Product as delivered to you; (iv) to indemnify, hold harmless,
-and defend UPEK from and against any claims or lawsuits, including attorney's fees, that arise or result
-from the use or distribution of the Licensed Product; (v) otherwise comply with the terms of this EULA;
-and (vi) agree that UPEK reserves all rights not expressly granted.
-(b) You also agree not to permit further distribution of the Redistributables by your end users except: (1)
-you may permit further redistribution of the Redistributables by your distributors to your end-user
-customers if your distributors only distribute the Redistributables in conjunction with, and as part of, the
-Licensed Product and You and Your distributors comply with all other terms of this EULA.
-4. RESERVATION OF RIGHTS; RESTRICTIONS. All rights not expressly granted by UPEK in this
-EULA are reserved. Except as otherwise expressly provided under this EULA, You shall not, and shall not
-allow any third party to:
-(a) transfer, assign, sublicense, resell, re-license or provide, lease, lend or allow access to the Software
-Product to any other person or entity, except as otherwise provided herein;
-(b) make error corrections or create derivative works based upon the Software Product;
-(c) copy (except to make a single back-up copy to replace an unusable copy of the Software Product),
-modify, prepare derivative works based upon, decompile, decrypt, reverse engineer or attempt to
-reconstruct or discover any source code or underlying ideas or algorithms of the Software Product by any
-means whatsoever (except to the extent applicable laws specifically prohibit such restriction), disassemble
-or otherwise reduce the Software Product to human-readable form to gain access to trade secrets or
-confidential information in the Software Product;
-(d) use the Software Product for timesharing, hosting or service bureau purposes; or
-(e) remove, obscure, or alter UPEK’s (or its third party licensors’) copyright notices, trademarks, or other
-proprietary rights notices affixed to or contained within the Software Product (and any copies thereof,
-including the back-up copy) or use such notices, trademarks or service marks for any other purpose.
-You understand and agree that (i) the Software Product is licensed to You and not sold, (ii) your license to
-the individual components of the Software Product is limited to use of the Software Product as a whole, and
-You may not use or seek to use software code incorporated therein on a stand-alone basis, and (iii) the
-individual components of the Software Product may not be separated for use on more than one UPEKEnabled Device, unless expressly permitted by this EULA. UPEK retains title to all copies of the Software
-Product and all associated intellectual property rights therein, and any and all documentation thereof.
-
-5. PROPRIETARY NOTICES; TRADEMARKS. You agree to maintain and reproduce all copyright and
-other proprietary notices on all copies, in any form, of the Software Product in the same form and manner
-that such copyright and other proprietary notices are included on the Software Product, including on any
-
-MP1:942657.3
-
-back-up copy of the Software Product. This EULA does not grant You any rights in connection with any
-trademarks or service marks of UPEK.
-6. SUPPORT SERVICES. UPEK may provide You with support services related to the Software Product
-(“Support Services”). Use of Support Services, if any, is governed by the UPEK policies and terms
-described in other UPEK-provided materials. Any supplemental software code provided to You as part of
-the Support Services is considered part of the Software Product and subject to the terms and conditions of
-this EULA.
-7. LIMITED WARRANTY.
-(a) UPEK warrants that during the “Warranty Period” (as defined below): (i) the media on which the
-Software Product is furnished, if any, will be free of defects in materials and workmanship under normal
-use; and (ii) the Software Product will substantially conform to its published specifications (the “Limited
-Warranty”). The “Warranty Period” means a period beginning on the date of Your receipt of the Software
-Product, as applicable, and ending on the later of (i) thirty (30) days from the date of delivery of such
-Software Product, as applicable, or (ii) the end of the minimum period required by the law of the applicable
-jurisdiction. The Limited Warranty extends only to You as the original licensee. This Limited Warranty
-does not cover anything caused by accident or abuse or by use of the Software Product other than for its
-reasonably intended purposes and as recommended in the accompanying user documentation. Updates are
-covered by this warranty only if provided to You during the Warranty Period. Your sole and exclusive
-remedy and the entire liability of UPEK and its suppliers under this Limited Warranty will be, at UPEK’s
-option, to repair, replace, or refund the purchase price for the Software Product that is returned to UPEK, as
-applicable, provided that you report the defects to UPEK or its designee within the Warranty Period. Any
-breach of the Limited Warranty related to an error or defect in the media containing the Software Product
-shall be remedied solely with the replacement of the media containing the Software Product. You shall pay
-shipping or freight charges, including, without limitation, obtaining full value replacement insurance, for
-any returns, whether for repair, replacement, or refund, to UPEK or its designee.
-(b) This warranty does not apply if the Software Product (i) is licensed for beta, evaluation, testing,
-demonstration or other purposes for which UPEK does not receive a license fee, (ii) has been altered,
-except by UPEK, (iii) has not been installed, operated, repaired, or maintained by UPEK or in accordance
-with instructions supplied by UPEK, (iv) has been subjected to abnormal physical or electrical stress,
-misuse, negligence, or accident, or (v) is used in ultrahazardous activities.
-8. DISCLAIMER OF WARRANTIES.
-(a) EXCEPT FOR THE EXPRESS WARRANTIES SET FORTH IN SECTION 7, UPEK AND ITS
-SUPPLIERS PROVIDE THE SOFTWARE PRODUCT AND SUPPORT SERVICES (IF ANY) TO YOU
-“AS IS,” AND YOUR USE IS AT YOUR OWN RISK. UPEK DOES NOT MAKE, AND HEREBY
-DISCLAIMS, ANY AND ALL OTHER EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
-NOT LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
-PARTICULAR PURPOSE, NONINFRINGEMENT OF THIRD PARTY RIGHTS, AND ANY
-WARRANTIES ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. THE
-DURATION OF ANY IMPLIED WARRANTY THAT IS NOT EFFECTIVELY DISCLAIMED WILL
-BE LIMITED TO THE WARRANTY PERIOD. SOME STATES DO NOT ALLOW LIMITATIONS ON
-HOW LONG AN IMPLIED WARRANTY LASTS, SO THE ABOVE LIMITATION MAY NOT APPLY
-TO YOU.
-(b) UPEK DOES NOT WARRANT THAT THE SOFTWARE PRODUCT IS ERROR FREE OR THAT
-YOU WILL BE ABLE TO OPERATE THE SOFTWARE WITHOUT PROBLEMS OR
-INTERRUPTIONS.
-9. LIMITATION OF LIABILITY.
-
-MP1:942657.3
-
-(a) TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, YOU EXPRESSLY
-ACKNOWLEDGE AND AGREE THAT NEITHER UPEK NOR ITS AFFILIATES, RESELLERS OR
-LICENSORS WILL BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL,
-CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF OR IN
-CONNECTION WITH THIS EULA, HOWSOEVER CAUSED BY ANY THEORY OF LIABILITY,
-INCLUDING BUT NOT LIMITED TO, CONTRACTS, PRODUCTS LIABILITY, STRICT LIABILITY
-AND NEGLIGENCE, AND WHETHER OR NOT UPEK OR ITS SUPPLIERS OR LICENSORS HAVE
-BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. WITHOUT LIMITING THE
-FOREGOING AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO
-EVENT WILL THE TOTAL LIABILITY OF UPEK OR ANY OF ITS AFFILIATES, SUPPLIERS OR
-LICENSORS ARISING OUT OF OR RELATED TO THIS EULA EXCEED THE FEES ACTUALLY
-PAID TO UPEK FOR THE SOFTWARE PRODUCT.
-(b) YOU ACKNOWLEDGE AND AGREE THAT THE PROVISIONS UNDER THIS EULA THAT
-LIMIT LIABILITY, DISCLAIM WARRANTIES, OR EXCLUDE CONSEQUENTIAL DAMAGES OR
-OTHER DAMAGES OR REMEDIES ARE ESSENTIAL TERMS OF THIS EULA THAT ARE
-FUNDAMENTAL TO THE PARTIES’ UNDERSTANDING REGARDING ALLOCATION OF RISK.
-ACCORDINGLY, SUCH PROVISIONS SHALL BE SEVERABLE AND INDEPENDENT OF ANY
-OTHER PROVISIONS AND SHALL BE ENFORCED AS SUCH, REGARDLESS OF ANY BREACH
-OR OTHER OCCURRENCE HEREUNDER, AND EVEN UNDER CIRCUMSTANCES THAT CAUSE
-ANY EXCLUSIVE REMEDY UNDER THIS EULA TO FAIL OF ITS ESSENTIAL PURPOSE.
-10. TERM AND TERMINATION.
-(a) The term of this EULA shall commence upon the date You accept the terms and conditions of this
-EULA, and shall continue in full force and effect thereafter unless terminated by UPEK as provided herein.
-UPEK may, at its option, terminate this EULA immediately upon notice to You, if You fail to comply with
-any terms and conditions of this EULA.
-(b) Upon termination, all license rights under this EULA will terminate and You must promptly destroy all
-copies of the Software Product in Your possession or control. Upon UPEK’s request, You shall certify in
-writing that You have complied with Your obligations under this Section and otherwise under this EULA.
-Termination by UPEK will not limit any of UPEK’s other rights or remedies under this EULA or at law or
-in equity.
-11. MISCELLANEOUS.
-(a) LIMITS ON YOUR RIGHT TO TRANSFER. You may not assign, sublicense, rent, lease, lend, sell,
-grant a security interest in, or otherwise transfer the Software Product or any rights under this EULA
-without the prior written consent of UPEK.
-(b) APPLICABLE LAW. This EULA is governed by the laws of the United States and the State of
-California, without regard to the conflict of laws principles thereof. In relation to any legal action or
-proceeding arising out of this EULA, You hereby irrevocably consent and submit to the exclusive
-jurisdiction of the competent federal and state courts having jurisdiction in San Francisco County,
-California, and waive any objection to proceedings in such courts. If this EULA is translated into a
-language other than English and there is a conflict between the terms of the EULA in English and the
-EULA in the other language, the terms of the terms of the EULA in English shall prevail. The EULA in
-English may be downloaded from the UPEK website.
-(c) COMPLIANCE WITH LAWS. You agree to use the Software Product in compliance with all
-applicable laws, statutes, rules and regulations, including, without limitation, U.S. export laws and
-regulations.
-(d) SEVERABILITY AND SURVIVAL. If any provision of this EULA is illegal or unenforceable under
-applicable law, the remaining provisions of this EULA will remain valid and fully enforceable. If any
-
-MP1:942657.3
-
-provision is in part enforceable and in part unenforceable, it will be enforced to the extent permitted under
-applicable law. Sections 4, 5, 7, 8, 9, 10 and 11 shall survive the termination of this EULA.
-(e) INJUNCTIVE RELIEF. You agree that a breach of this EULA adversely affecting UPEK’s proprietary
-rights in the Software Product or any UPEK-Enabled Device may cause irreparable injury to UPEK for
-which monetary damages would not be an adequate remedy and UPEK shall be entitled to equitable relief
-in addition to any remedies it may have hereunder or at law.
-(f) ENTIRE AGREEMENT. This EULA (including any addendum or amendment to this EULA which is
-included with the Software Product) is the entire agreement between You and UPEK relating to the
-Software Product and the Support Services (if any) and they supersede all prior or contemporaneous oral or
-written communications, proposals and representations with respect to the Software Product or any other
-subject matter covered by this EULA. No amendment to or modification of this EULA will be binding
-unless made in writing and signed by UPEK. No failure to exercise, and no delay in exercising, on the part
-of either party, any right or any power hereunder shall operate as a waiver thereof, nor shall any single or
-partial exercise of any right or power hereunder preclude further exercise of any other right hereunder. In
-the event of any conflict between this EULA and any applicable purchase terms or UPEK’s policies and
-terms for Support Services, the terms of this EULA shall control.
-
-MP1:942657.3
-
-

diff --git a/net-dialup/accel-pptp/Manifest b/net-dialup/accel-pptp/Manifest
deleted file mode 100644
index 6f874b0..0000000
--- a/net-dialup/accel-pptp/Manifest
+++ /dev/null
@@ -1 +0,0 @@
-DIST accel-pptp-0.8.5.tar.bz2 589096 RMD160 7ac16756f32ccf617ac63e50fa57ab8c6d9f106f SHA1 1bb5ee672dab14025fc16906368244c17719e7a1 SHA256 ac27e9834e61bb4c97be232c8c2c342cc91ebf431309079d1014acede805106b

diff --git a/net-dialup/accel-pptp/accel-pptp-0.8.5.ebuild b/net-dialup/accel-pptp/accel-pptp-0.8.5.ebuild
deleted file mode 100644
index cfdee69..0000000
--- a/net-dialup/accel-pptp/accel-pptp-0.8.5.ebuild
+++ /dev/null
@@ -1,95 +0,0 @@
-# Copyright 1999-2011 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-# $Header: $
-
-EAPI="4"
-
-inherit linux-mod eutils autotools multilib
-
-DESCRIPTION="Point-to-Point Tunnelling Protocol Client/Server for Linux"
-SRC_URI="mirror://sourceforge/accel-pptp/${P}.tar.bz2"
-HOMEPAGE="http://accel-pptp.sourceforge.net/"
-
-SLOT="0"
-LICENSE="GPL-2"
-KEYWORDS="~amd64 ~x86"
-IUSE="tcpd server"
-
-COMMON_DEPEND=">=net-dialup/ppp-2.4.2
-	server? ( !net-dialup/pptpd )
-	tcpd? ( sys-apps/tcp-wrappers )"
-DEPEND="${COMMON_DEPEND}
-	virtual/linux-sources"
-RDEPEND="${COMMON_DEPEND}"
-
-BUILD_TARGETS="all"
-BUILD_PARAMS="KDIR=${KERNEL_DIR}"
-CONFIG_CHECK="PPP PPPOE PPTP"
-MODULESD_PPTP_ALIASES=("net-pf-24 pptp")
-
-src_prepare() {
-	use server && cd "${S}/pptpd-1.3.3" && eautoreconf
-	cd "${S}/pppd_plugin" && eautoreconf
-
-	#Match pptpd-logwtmp.so's version with pppd's version (#89895)
-	local PPPD_VER=$(best_version net-dialup/ppp)
-	PPPD_VER=${PPPD_VER#*/*-} #reduce it to ${PV}-${PR}
-	PPPD_VER=${PPPD_VER%%[_-]*} # main version without beta/pre/patch/revision
-	echo "#define VERSION \"${PPPD_VER}\"" > "${S}/pptpd-1.3.3/plugins/patchlevel.h"
-	# Respect LDFLAGS
-	sed -e "/^LDFLAGS/{s:=:+=:}" -i "${S}/pptpd-1.3.3/plugins/Makefile"
-}
-
-src_configure() {
-	if use server; then
-		cd "${S}/pptpd-1.3.3"
-		# Define KDIR to build against userspace headers...
-		KDIR='/usr' \
-		    econf --enable-bcrelay \
-				$(use_with tcpd libwrap)
-	fi
-
-	cd "${S}/pppd_plugin"
-	KDIR='/usr' econf
-}
-
-src_compile() {
-	if use server; then
-		cd "${S}/pptpd-1.3.3"
-	    emake COPTS="${CFLAGS}" || die "make failed"
-	fi
-
-	cd "${S}/pppd_plugin"
-	emake COPTS="${CFLAGS}" || die "make failed"
-}
-
-src_install () {
-	if use server; then
-	    cd "${S}/pptpd-1.3.3"
-	    einstall || die "make install failed"
-
-	    insinto /etc
-	    doins samples/pptpd.conf
-
-	    insinto /etc/ppp
-	    doins samples/options.pptpd
-
-	    exeinto /etc/init.d
-	    newexe "${FILESDIR}/pptpd-init" pptpd || die
-
-	    insinto /etc/conf.d
-	    newins "${FILESDIR}/pptpd-confd" pptpd || die
-	fi
-
-	cd "${S}/pppd_plugin/src/.libs"
-	local PPPD_VER=$(best_version net-dialup/ppp)
-	PPPD_VER=${PPPD_VER#*/*-} #reduce it to ${PV}-${PR}
-	PPPD_VER=${PPPD_VER%%[_-]*} # main version without beta/pre/patch/revision
-	insinto /usr/$(get_libdir)/pppd/${PPPD_VER}
-	newins pptp.so.0.0.0 pptp.so || die
-	doman "${S}"/pppd_plugin/src/pppd-pptp.8 || die
-
-	cd "${S}"
-	dodoc README || die
-	cp -R example "${D}/usr/share/doc/${P}/example"
-}

diff --git a/net-dialup/accel-pptp/files/README.gentoo b/net-dialup/accel-pptp/files/README.gentoo
deleted file mode 100644
index 68d6af2..0000000
--- a/net-dialup/accel-pptp/files/README.gentoo
+++ /dev/null
@@ -1,13 +0,0 @@
-link_ppp17="/dev/null"
-username_ppp17='pva0xd'
-password_ppp17='3149068110'
-pppd_ppp17="
-plugin pptp.so
-pptp_server 78.31.23.148
-file /etc/ppp/options.pptp
-mtu 1436
-mru 1436
-lcp-echo-interval 20
-lcp-echo-failure  3
-"
-

diff --git a/net-dialup/accel-pptp/files/options.pptp b/net-dialup/accel-pptp/files/options.pptp
deleted file mode 100644
index d61ab80..0000000
--- a/net-dialup/accel-pptp/files/options.pptp
+++ /dev/null
@@ -1,32 +0,0 @@
-#
-# Lock the port
-#
-#lock
-
-#
-# We don't need the tunnel server to authenticate itself
-#
-noauth
-
-#
-# Turn off transmission protocols we know won't be used
-#
-nobsdcomp
-nodeflate
-
-#
-# We want MPPE
-#
-require-mppe
-
-#
-# We want a sane mtu/mru
-#
-mtu 1437
-mru 1437
-
-#
-# Time this thing out of it goes poof
-#
-lcp-echo-failure 10
-lcp-echo-interval 10

diff --git a/net-dialup/accel-pptp/files/pptpd-confd b/net-dialup/accel-pptp/files/pptpd-confd
deleted file mode 100644
index 1169e57..0000000
--- a/net-dialup/accel-pptp/files/pptpd-confd
+++ /dev/null
@@ -1,5 +0,0 @@
-# Config file for /etc/init.d/pptpd
-
-# Any extra options you want to pass to pptpd
-# on start-up should be put here.
-PPTPD_OPTS=""

diff --git a/net-dialup/accel-pptp/files/pptpd-init b/net-dialup/accel-pptp/files/pptpd-init
deleted file mode 100644
index 171e113..0000000
--- a/net-dialup/accel-pptp/files/pptpd-init
+++ /dev/null
@@ -1,24 +0,0 @@
-#!/sbin/runscript
-# Copyright 1999-2009 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License, v2 or later
-# $Header: $
-
-depend() {
-	need net
-}
-
-start() {
-	ebegin "Starting pptpd"
-	modprobe pptp
-	start-stop-daemon --start --quiet --exec /usr/sbin/pptpd -- ${PPTPD_OPTS}
-	eend $?
-}
-
-stop() {
-	ebegin "Stopping pptpd"
-	start-stop-daemon --stop --quiet --pidfile /var/run/pptpd.pid
-	result=$?
-	start-stop-daemon --stop --quiet --oknodo --exec /usr/sbin/pptpctrl
-	result=$(( $result + $? ))
-	eend $result
-}

diff --git a/net-dialup/accel-pptp/metadata.xml b/net-dialup/accel-pptp/metadata.xml
deleted file mode 100644
index 009a9d9..0000000
--- a/net-dialup/accel-pptp/metadata.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
-<pkgmetadata>
-	<herd>net-dialup</herd>
-	<use>
-		<flag name='server'>Enable pptpd</flag>
-	</use>
-</pkgmetadata>

diff --git a/sys-apps/maemo-flasher35/Manifest b/sys-apps/maemo-flasher35/Manifest
deleted file mode 100644
index 7e794d8..0000000
--- a/sys-apps/maemo-flasher35/Manifest
+++ /dev/null
@@ -1 +0,0 @@
-DIST maemo_flasher-3.5_2.5.2.2.tar.gz 48619 SHA256 2072c7d146e72ba238723ebc639ad0fa6a61fc1f5305463a6bcc76ccb302723e SHA512 bbb16f97489ec437e1a9c5dabb07ff55b9eb954e81b19a70e195f2a93aee256827907810366ac66a83ad09fe0752edc790c5d4a719fbcc3e38cdb163e5b733fd WHIRLPOOL 8c5d6fdcd3d62289e9d162e12b7a3878602d34695bc3bbd3b238adb489652830168c2ecc5c745c541bce92cc916e5835af409be08372d954c32da21ab195ebaa

diff --git a/sys-apps/maemo-flasher35/maemo-flasher35-2.5.2.2.ebuild b/sys-apps/maemo-flasher35/maemo-flasher35-2.5.2.2.ebuild
deleted file mode 100644
index 2d0f02a..0000000
--- a/sys-apps/maemo-flasher35/maemo-flasher35-2.5.2.2.ebuild
+++ /dev/null
@@ -1,38 +0,0 @@
-# Copyright 1999-2010 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-# $Header: $
-
-EAPI=3
-
-MY_PN="${PN/-/_}"
-MY_PN="${MY_PN/35/}"
-MY_PV="3.5_${PV}"
-MY_P="${MY_PN}-${MY_PV}"
-
-FN="${MY_P}.tar.gz"
-DESCRIPTION="Firmware flasher for Maemo"
-HOMEPAGE="http://www.maemo.org"
-SRC_URI="${FN}"
-
-LICENSE="Nokia-EULA"
-SLOT="0"
-KEYWORDS="~amd64"
-IUSE=""
-RESTRICT="fetch strip"
-
-DEPEND="virtual/libc"
-RDEPEND="${DEPEND}"
-
-pkg_nofetch() {
-	elog "Please obtain ${FN} from
-	http://tablets-dev.nokia.com/maemo-dev-env-downloads.php
-	and place it in ${DISTDIR}"
-}
-
-S="${WORKDIR}"/${MY_P}
-
-src_install() {
-	newbin flasher-3.5 flasher || die
-	newman man/man1/flasher-3.5.1 flasher.1 || die
-	dodoc doc/changelog doc/README.Debian || die
-}

diff --git a/sys-auth/fingerprint-gui/Manifest b/sys-auth/fingerprint-gui/Manifest
deleted file mode 100644
index 2b5408e..0000000
--- a/sys-auth/fingerprint-gui/Manifest
+++ /dev/null
@@ -1 +0,0 @@
-DIST fingerprint-gui-1.00.tar.gz 3781064 SHA256 4d826156e553076f6d7817c4a347ab955e81c44c355ec10b7ab2d3d7732136f5 SHA512 5372964ea5f75b51362316041eb1504cb235c016a615870a88994e4c566561a98c630b400203752bb4ac40c82d881a31a19304b664928ce0c1a03ff7134c362c WHIRLPOOL 9a7a3c5b545bdccc4af86cfabd1b4f9d9bb2996568540e338e7926a6f2453dc8d6113b978c6eb6202bfcd360aa44a8163fbdd92c7f51b57a2440c8d50010196d

diff --git a/sys-auth/fingerprint-gui/files/Install-step-by-step.html b/sys-auth/fingerprint-gui/files/Install-step-by-step.html
deleted file mode 100644
index 240f49e..0000000
--- a/sys-auth/fingerprint-gui/files/Install-step-by-step.html
+++ /dev/null
@@ -1,699 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<HTML>
-<HEAD>
-	<META HTTP-EQUIV="CONTENT-TYPE" CONTENT="text/html; charset=utf-8">
-	<TITLE></TITLE>
-	<META NAME="GENERATOR" CONTENT="OpenOffice.org 3.2  (Unix)">
-	<META NAME="AUTHOR" CONTENT="Wolfgang Ullrich">
-	<META NAME="CREATED" CONTENT="20081021;15191700">
-	<META NAME="CHANGEDBY" CONTENT="Wolfgang Ullrich">
-	<META NAME="CHANGED" CONTENT="20100819;20523800">
-	<META NAME="Info 1" CONTENT="">
-	<META NAME="Info 2" CONTENT="">
-	<META NAME="Info 3" CONTENT="">
-	<META NAME="Info 4" CONTENT="">
-	<STYLE TYPE="text/css">
-	<!--
-		@page { margin: 2cm }
-		P { margin-bottom: 0.21cm; page-break-before: auto }
-		P.cjk { font-size: 10pt }
-		H1 { margin-bottom: 0.21cm; page-break-before: auto }
-		H1.western { font-family: "Arial", sans-serif; font-size: 16pt }
-		H1.cjk { font-family: "DejaVu Sans"; font-size: 16pt }
-		H1.ctl { font-family: "DejaVu Sans"; font-size: 16pt }
-		H2 { margin-bottom: 0.21cm; page-break-before: auto }
-		H2.western { font-family: "Arial", sans-serif; font-size: 14pt; font-style: italic }
-		H2.cjk { font-size: 14pt; font-style: italic }
-		H2.ctl { font-size: 14pt; font-style: italic }
-		H3 { margin-bottom: 0.21cm; page-break-before: auto }
-		H3.western { font-family: "Arial", sans-serif }
-		A.western:visited { so-language: en-US }
-		A.cjk:visited { so-language: zxx }
-		A.ctl:visited { so-language: zxx }
-	-->
-	</STYLE>
-</HEAD>
-<BODY LANG="en-US" DIR="LTR">
-<P ALIGN=CENTER STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT FACE="Arial, sans-serif"><FONT SIZE=4><B>Installing
-Step by Step</B></FONT></FONT></P>
-<P CLASS="western" ALIGN=CENTER><FONT SIZE=2>(Version 0.15)</FONT></P>
-<DIV ID="Inhaltsverzeichnis1" DIR="LTR">
-	<DIV ID="Inhaltsverzeichnis1_Head" DIR="LTR">
-		<P STYLE="margin-top: 0.42cm; page-break-after: avoid"><FONT FACE="Arial, sans-serif"><FONT SIZE=4 STYLE="font-size: 16pt"><B>Contents</B></FONT></FONT></P>
-	</DIV>
-	<P STYLE="margin-bottom: 0cm"> 1 Installing Executables and
-	Libraries	2</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 1.1 Installing
-	required Libraries	2</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 1.2 Installing
-	executables	2</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 1.3 Creating a
-	“plugdev” group	3</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 1.4 Uninstalling
-	other Fingerprint Solutions	3</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 1.5 Special
-	preparations for Lubuntu	3</P>
-	<P STYLE="margin-bottom: 0cm"> 2 Acquiring Fingerprints	3</P>
-	<P STYLE="margin-bottom: 0cm"> 3 Setting up Fingerprint
-	Authentication	3</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 3.1 Configuring
-	“su”	4</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 3.2 Configuring
-	“login”	5</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 3.3 Configuring
-	“sudo”	5</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 3.4 Configuring
-	“gdm”	5</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 3.5 Configuring
-	“gnome-screensaver”	6</P>
-	<P STYLE="margin-bottom: 0cm"> 4 Exporting Fingerprint Data and
-	Testing PAM Settings	6</P>
-	<P STYLE="margin-bottom: 0cm"> 5 Password Store	6</P>
-	<P STYLE="margin-bottom: 0cm"> 6 Troubleshooting	8</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 6.1 Gdm Greeter
-	doesn't show the Fingerprint GUI Widget or needs a long time (up to
-	20 seconds) to show it	8</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 6.2
-	Fingerprint-gui Error “Could not open fingerprint device”	8</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 6.3 Login on a
-	secure tty hangs with “OK” Message	8</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 6.4 You have a
-	fingerprint device from UPEK/SGS Thomson and get some “ABSOpen()
-	failed...” error message in /var/log/auth.log	8</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 6.5 Password can
-	not be saved to removable media	8</P>
-	<P STYLE="margin-bottom: 0cm"> 7 Known Limitations	9</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 7.1 Applications
-	that don't use PAM for prompting a password	9</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 7.2 Missing
-	XAUTHORITY environment variable	9</P>
-	<P STYLE="margin-left: 0.5cm; margin-bottom: 0cm"> 7.3 Other Linux
-	distributions	9</P>
-	<P STYLE="margin-left: 1cm; margin-bottom: 0cm">Debian 4.0	9</P>
-	<P STYLE="margin-left: 1cm; margin-bottom: 0cm">SuSE 11.1 (gnome
-	edition)	9</P>
-	<P STYLE="margin-left: 1cm; margin-bottom: 0cm">Slackware	9</P>
-</DIV>
-<P CLASS="western" ALIGN=CENTER><BR><BR>
-</P>
-<P CLASS="western"><BR><BR>
-</P>
-<P CLASS="western" STYLE="page-break-before: always">This HowTo
-describes the installation and setup of the “Fingerprint GUI”
-project. It was tested on <I><U>Ubuntu 8.04, 8.10, 9.04, 9.10 and
-10.04 Desktop</U></I>, <I><U>Lubuntu 10.04</U></I> and <I><U>Fedora
-10 and 12</U></I> (32bit versions) and <I><U>Ubuntu 8.10 9.04 and
-10.04 Desktop</U></I> (64bit version) each new installed with default
-settings. It is applicable for GDM/Gnome desktop systems only and <B>can
-</B><U><B>not</B></U><B> be used as a HowTo for KDE systems</B>. It
-should show the principles of installing and configuring the system
-and provide enough information needed for deployment in other Linux
-distributions. In the chapter <B>&quot;Other Linux distributions&quot;</B>,
-my experiences with these distributions are described. I didn't have
-the time to solve all those problems. That should be the
-responsibility of the distributors or of experienced users. Please
-contact me if you have the system installed properly to such a
-distribution or if you experience a bug.</P>
-<OL>
-	<LI><H1 CLASS="western">Installing Executables and Libraries</H1>
-</OL>
-<P CLASS="western">After downloading the
-“fingerprint-gui-x.y-&lt;arch&gt;.tar.gz” package please unpack
-it into some directory (<FONT FACE="Courier 10 Pitch"><FONT SIZE=2>tar
--xzf fingerprint-gui-x.y-&lt;arch&gt;.tar.gz</FONT></FONT>). Then
-change to this directory and become “root”. The command for
-installation is “<FONT FACE="Courier 10 Pitch"><FONT SIZE=2>./install.sh
-[--uninstall]</FONT></FONT>”.  If you have a device from UPEK Inc.
-or SGS Thomson you will need the proprietary driver library
-“libbsapi.so” from UPEK Inc.  In this case you will be prompted
-for installing this library. If you chose “Yes” the “libbsapi.so”
-file (for your architecture) will be copied to “/usr/lib/” and
-“ldconfig” will be called then. If you have a device from other
-vendors you will not be prompted for installing “libbsapi.so”.
-Please have a look at the libfprint homepage
-(<A CLASS="western" HREF="http://reactivated.net/fprint/wiki/Main_Page">http://reactivated.net/fprint/wiki/Main_Page</A>)
-for a list of supported devices. 
-</P>
-<OL>
-	<OL>
-		<LI><H2 CLASS="western">Installing required Libraries</H2>
-	</OL>
-</OL>
-<P CLASS="western">When executing “./install.sh” as root it will
-probably print a list of missing libraries. Use your package manager
-to install the required packages and their dependencies. Below is a
-list of packages to install:</P>
-<P CLASS="western"><U>Ubuntu 10.04 Desktop:</U></P>
-<UL>
-	<LI><P CLASS="western">libfakekey0 
-	</P>
-	<LI><P CLASS="western">libfprint0 (<U><B>IMPORTANT</B></U>: Since
-	version 0.14 fingerprint-gui requires libfprint0 version
-	0.1.0~pre2-1 that is <U>not</U> part of the Ubuntu repository yet.
-	Please install this version from
-	<A CLASS="western" HREF="https://launchpad.net/~fingerprint/+archive/fprint">https://launchpad.net/~fingerprint/+archive/fprint</A>
-	.</P>
-	<LI><P CLASS="western">libqca2</P>
-	<LI><P CLASS="western">libqca2-plugin-ossl</P>
-	<LI><P CLASS="western">libqt4-xml</P>
-</UL>
-<P CLASS="western"><U>Fedora 12:</U></P>
-<UL>
-	<LI><P CLASS="western">libfakekey-0.1.3 
-	</P>
-	<LI><P CLASS="western">libfprint-0.1.0-14.pre2</P>
-	<LI><P CLASS="western">qt-x11-1:4.6.2-16</P>
-	<LI><P CLASS="western">qca2-2.0.2-2 
-	</P>
-</UL>
-<UL>
-	<LI><P CLASS="western">qca-ossl-2.0.0-0.8.beta3</P>
-</UL>
-<OL>
-	<OL START=2>
-		<LI><H2 CLASS="western">Installing executables</H2>
-	</OL>
-</OL>
-<P CLASS="western">If all required libraries are installed the
-“./install.sh” script will copy the executables and some other
-files to the following locations:</P>
-<UL>
-	<LI><P CLASS="western">“fingerprint-gui” and
-	“fingerprint-identifier” to /usr/local/bin/,</P>
-	<LI><P CLASS="western">“fingerprint-suid”, “fingerprint-helper”
-	and “fingerprint-plugin” to /usr/local/lib/fingerprint-gui/,</P>
-	<LI><P CLASS="western">A “Fingerprint GUI” entry in the “System
-	Settings” menu,</P>
-	<LI><P CLASS="western">The plugin “pam_fingerprint-gui.so” to
-	/lib/security/ (/lib64/security/ in Fedora 64bit),</P>
-	<LI><P CLASS="western">In case of a detected device from UPEK Inc.
-	or SGS Thomson your choice of “Yes” to the appropriate prompt
-	the library “libbsapi.so” to “/usr/lib”, a configuration
-	file “upek.cfg” to “/etc”, an udev-rules file
-	“91-fingerprint-gui-upek.rules” to “/etc/udev/rules.d” and
-	create a directory “/var/upek_data”.</P>
-</UL>
-<OL>
-	<OL START=3>
-		<LI><H2 CLASS="western">Creating a “plugdev” group</H2>
-	</OL>
-</OL>
-<P CLASS="western">While installation <SPAN STYLE="background: transparent">the</SPAN>
- “./install.sh” script will check your “/etc/group” file for
-the existence of a group named “plugdev”. If it doesn't exist
-you'll get a warning. In this case please create this group and make
-all desktop users being members of this group or make sure all users
-have r/w access to the fingerprint scanner device by a proper setup
-of your “udev” configuration.</P>
-<OL>
-	<OL START=4>
-		<LI><H2 CLASS="western">Uninstalling other Fingerprint Solutions</H2>
-	</OL>
-</OL>
-<P CLASS="western">Because fingerprint-gui can conflict with other
-fingerprint PAM modules these must be uninstalled. Please make sure
-there is no “libpam-fprint”, “libpam-fprintd” or
-”libpam-thinkfinger” installed.</P>
-<P CLASS="western"><U><B>IMPORTANT:</B></U> On Fedora 12 you need to
-<U>uninstall</U> “gdm-plugin-fingerprint” and disable the
-fingerprint authentication in “system | administration |
-authentication”.</P>
-<OL>
-	<OL START=5>
-		<LI><H2 CLASS="western">Special preparations for Lubuntu</H2>
-	</OL>
-</OL>
-<P CLASS="western">The default display manager (lxdm) of Lubuntu
-doesn't work with fingerprint login. Please install “gdm” and
-make it the default display manager. If you want to use the default
-screensaver (xscreensaver) of Lubuntu please change settings of file
-“/etc/pam.d/xscreensaver” instead of
-“/etc/pam.d/gnome-screensaver” below. The setup for an embedded 
-keyboard command is <U>not</U> required in this case.</P>
-<OL START=2>
-	<LI><H1 CLASS="western" STYLE="page-break-after: avoid"><FONT FACE="Arial, sans-serif">Acquiring
-	Fingerprints</FONT></H1>
-</OL>
-<P CLASS="western">Now you should be able to call “fingerprint-gui”
-from the command line or use the “Fingerprint GUI” entry in the
-“System Settings” menu. Acquiring fingerprints should be
-self-explanatory in the “fingerprint-gui” program. Your
-fingerprints are stored in a
-“/var/lib/fingerprint-gui/&lt;your_username&gt;/” directory,
-where only you have access to. If you give the “--debug” argument
-to “fingerprint-gui” a lot of debug output is given to syslog (or
-/var/log/auth.log).</P>
-<P CLASS="western">After some users have registered their
-fingerprints you can test the fingerprint identification by calling
-“fingerprint-identifier” <U>as root</U> (execute “sudo
-fingerprint.identifier –debug”). This application can identify
-your users and print their login names to stdout.</P>
-<OL START=3>
-	<LI><H1 CLASS="western" STYLE="page-break-after: avoid">Setting up
-	Fingerprint Authentication</H1>
-</OL>
-<P CLASS="western">You need root permissions to make changes to your
-PAM configuration. First of all make a copy of your
-“/etc/pam.d/common-auth” file and name it
-“/etc/pam.d/common-auth.fingerprint”. Edit this file like
-follows:</P>
-<UL>
-	<LI><P CLASS="western">insert a line <FONT FACE="Courier New, monospace"><FONT SIZE=2><SPAN STYLE="text-decoration: none">“auth
-	 sufficient  pam_fingerprint-gui.so  --debug”</SPAN></FONT></FONT>
-	<B>as the first </B><B>line</B>;</P>
-	<LI><P CLASS="western">find the line containing “pam_unix.so”
-	and add the argument “try_first_pass” to the call of
-	“pam_unix.so”;</P>
-</UL>
-<P CLASS="western">The distributions differ slightly with regard to
-the filenames and their contents:</P>
-<P CLASS="western"><U>Ubuntu 10.04 Desktop:</U></P>
-<P CLASS="western">“/etc/pam.d/common-auth.fingerprint” is a copy
-of “/etc/pam.d/common-auth”. The changed lines in question read:</P>
-<P CLASS="western" STYLE="text-decoration: none">“<FONT FACE="Courier New, monospace"><FONT SIZE=2>auth	sufficient	pam_fingerprint-gui.so	--debug”</FONT></FONT></P>
-<P CLASS="western" STYLE="text-decoration: none">“<FONT FACE="Courier New, monospace"><FONT SIZE=2>auth	[success=1
-default=ignore]	pam_unix.so	try_first_pass nullok_secure”</FONT></FONT></P>
-<P CLASS="western"><U>Fedora 12:</U></P>
-<P CLASS="western">“/etc/pam.d/common-auth.fingerprint” is a copy
-of “/etc/pam.d/system-auth-ac”. The changed lines in question
-read:</P>
-<P CLASS="western" STYLE="text-decoration: none">“<FONT FACE="Courier New, monospace"><FONT SIZE=2>auth	sufficient	pam_fingerprint-gui.so
---debug”</FONT></FONT></P>
-<P CLASS="western" STYLE="text-decoration: none">“<FONT FACE="Courier New, monospace"><FONT SIZE=2>auth	sufficient	pam_unix.so
-nullok try_first_pass”</FONT></FONT></P>
-<P CLASS="western">If you're finished setting up your
-“common-auth.fingerprint” file you can setup the services for
-fingerprint authentication now. It is assumed you have at least one
-fingerprint registered for your user account and one for root. Also
-make sure there is set a password for root (sudo passwd root).</P>
-<P CLASS="western">The following settings will change the existing
-reference to “common-auth” (“system-auth” in Fedora) to the
-new “common-auth.fingerprint” for the PAM services.</P>
-<P CLASS="western"><U><B>IMPORTANT NOTE:</B></U><SPAN STYLE="text-decoration: none"><SPAN STYLE="font-weight: normal">
-The following settings can lock access to your system completely if
-</SPAN></SPAN><SPAN STYLE="text-decoration: none"><SPAN STYLE="font-weight: normal">something
-goes wrong. So please open a secure tty (ctrl-alt-F2) and login as
-root there. This way you're able to undo the changes made in
-“/etc/pam.d/”.</SPAN></SPAN></P>
-<OL>
-	<OL>
-		<LI><H2 CLASS="western">Configuring “su”</H2>
-	</OL>
-</OL>
-<P CLASS="western">Edit the file “/etc/pam.d/su” and change the
-line “@include common-auth” to “@include
-common-auth.fingerprint” (on Ubuntu) or “auth include
-system-auth” to “auth include common-auth.fingerprint” (on
-Fedora).</P>
-<OL>
-	<OL>
-		<P CLASS="western"><U>Ubuntu:</U></P>
-	</OL>
-</OL>
-<P CLASS="western" STYLE="margin-left: 1.25cm; margin-bottom: 0cm">...</P>
-<P CLASS="western" STYLE="margin-left: 1.25cm; margin-bottom: 0cm">#@include
-common-auth 
-</P>
-<P CLASS="western" STYLE="margin-left: 1.25cm; margin-bottom: 0cm">@include
-common-auth.fingerprint 
-</P>
-<P CLASS="western" STYLE="margin-left: 1.25cm; margin-bottom: 0cm">@include
-common-account 
-</P>
-<P CLASS="western" STYLE="margin-left: 1.25cm; margin-bottom: 0cm">@include
-common-session 
-</P>
-<OL>
-	<OL>
-		<P CLASS="western" STYLE="margin-bottom: 0cm"></P>
-	</OL>
-</OL>
-<P CLASS="western" STYLE="margin-left: 1.25cm"><U>Fedora:</U></P>
-<P CLASS="western" STYLE="margin-left: 1.25cm; margin-bottom: 0cm">...</P>
-<P CLASS="western" STYLE="margin-left: 1.25cm; margin-bottom: 0cm">#auth
- required  pam_wheel.so  use_uid 
-</P>
-<P CLASS="western" STYLE="margin-left: 1.25cm; margin-bottom: 0cm">auth
- include  common-auth.fingerprint 
-</P>
-<P CLASS="western" STYLE="margin-left: 1.25cm; margin-bottom: 0cm">#auth
- include  system-auth 
-</P>
-<P CLASS="western" STYLE="margin-left: 1.25cm; margin-bottom: 0cm">account
- sufficient  pam_succeed_if.so uid = 0  use_uid  quiet</P>
-<P CLASS="western" STYLE="margin-left: 1.25cm; margin-bottom: 0cm">...
-</P>
-<P CLASS="western" STYLE="margin-left: 1.25cm; margin-bottom: 0cm"><BR>
-</P>
-<P CLASS="western">Then open a terminal window and call “su”. A
-password prompt should appear in the terminal <U><B>and</B></U><SPAN STYLE="text-decoration: none"><SPAN STYLE="font-weight: normal">
-the system should open a GUI widget requesting a finger swipe with
-the message “Authenticating </SPAN></SPAN><SPAN STYLE="text-decoration: none"><SPAN STYLE="font-weight: normal">root”
-in it's status bar. If you can become root by swiping the finger
-registered for root it works. You </SPAN></SPAN><SPAN STYLE="text-decoration: none"><SPAN STYLE="font-weight: normal">should
-also be able to become root by ignoring this GUI widget and typing
-root's password at the prompt.</SPAN></SPAN></P>
-<OL>
-	<OL START=2>
-		<LI><H2 CLASS="western">Configuring “login”</H2>
-	</OL>
-</OL>
-<P CLASS="western"><U><B>IMPORTANT:</B></U> On Fedora 12 SELinux
-denies access to the user's fingerprint data in
-“/var/lib/fingerprint-gui/...” while login. Currently I'm not
-able to setup a SELinux policy for fingerprint-gui. If you can be of
-assistance about this please contact me. If not, set your SELinux
-mode to “permissive” at least while testing login.</P>
-<P CLASS="western">Edit the file “/etc/pam.d/login” and change
-the line “@include common-auth” to “@include
-common-auth.fingerprint” (on Ubuntu) or “auth include
-system-auth” to “auth include common-auth.fingerprint” (on
-Fedora). Then change to a secure tty (e.g. ctrl-alt-F3), type the
-username and press enter. The password prompt should appear along
-with a message “Type your password or swipe your finger”. You
-should be able to login with a finger swipe and with typing the
-password as well.</P>
-<OL>
-	<OL START=3>
-		<LI><H2 CLASS="western">Configuring “sudo”</H2>
-	</OL>
-</OL>
-<P CLASS="western">Edit the file “/etc/pam.d/sudo” and change the
-line “@common-auth” to “@common-auth.fingerprint” (on Ubuntu)
-or “auth include system-auth” to “auth include
-common-auth.fingerprint” (on Fedora). Make sure your login name is
-in the sudoers file. Then open a terminal window and call “sudo
-gnome-terminal”. After swiping your finger the gnome-terminal
-should open with root permissions.</P>
-<OL>
-	<OL START=4>
-		<LI><H2 CLASS="western">Configuring “gdm”</H2>
-	</OL>
-</OL>
-<P CLASS="western">In order to be able to login into a desktop
-session you need to configure your gdm (probably with gdmsetup).
-Disable “autologin”, “timed login” and “userlist”. Use
-the command (this is one line!) to disable the userlist:</P>
-<P CLASS="western"><FONT FACE="Courier 10 Pitch"><FONT SIZE=2>sudo
-gconftool-2 --direct --config-source
-xml:readwrite:/etc/gconf/gconf.xml.defaults --type bool --set
-/apps/gdm/simple-greeter/disable_user_list true</FONT></FONT></P>
-<P CLASS="western">Then double check you have a root session on a
-secure tty open (for undoing the changes if something goes wrong). 
-</P>
-<P CLASS="western"><U>On Ubuntu</U> edit the file “/etc/pam.d/gdm”
-and change the line “@include common-auth” to “@include
-common-auth.fingerprint”.</P>
-<P CLASS="western"><U>On Kubuntu</U> edit the file “/etc/pam.d/kdm”
-and change the line “@include common-auth” to “@include
-common-auth.fingerprint” and move this line to the beginning of the
-file. Then start “System settings | Advanced&quot; and open the
-“Convenience” tab. Disable “Enable Auto-login” and “Focus
-password” and set “Previous” as the default user for login. You
-can then login with your fingerprint after pressing &lt;enter&gt; in
-the kdm greeter.</P>
-<P CLASS="western"><U>On Fedora</U> edit the file
-“/etc/pam.d/gdm-password” and change the line “auth substack
-system-auth” to “auth substack common-auth.fingerprint”. 
-</P>
-<P CLASS="western">If there is a line reading “auth  requisite 
-pam_nologin.so” <B>comment this line out or remove it</B>.  Now
-logout from your gnome session. The gdm greeter should show a login
-prompt <B>and</B> the GUI widget requesting a finger swipe below. You
-should be able to login with fingerprint and with name/password as
-well.</P>
-<OL>
-	<OL START=5>
-		<LI><H2 CLASS="western">Configuring “gnome-screensaver”</H2>
-	</OL>
-</OL>
-<P CLASS="western">Gnome-screensaver needs a plugin to display the
-fingerprint GUI widget to the user while unlocking. To start this
-plugin with the gnome-screensaver-dialog open the gconf-editor, find
-the “apps | gnome-screensaver” entry and <B>enable</B> the
-“embedded_keyboard_enabled” item. Then invoke the string
-“/usr/local/lib/fingerprint-gui/fingerprint-plugin -d” as the
-“/apps/gnome-screensaver/embedded_keyboard_command” and close
-gconf-editor. <B>This step needs to be taken by every user who wants
-to unlock his/her gnome-screensaver by fingerprint on that machine!</B></P>
-<P CLASS="western">Then edit the file “/etc/pam.d/gnome-screensaver”
-change the line “@include common-auth” to “@include
-common-auth.fingerprint” (on Ubuntu) or “auth include
-system-auth” to “auth include common-auth.fingerprint” (on
-Fedora). Double check you have a root session on a secure tty open
-(for undoing the changes if something goes wrong) before testing. You
-can now lock your screen and should be able to unlock it with a
-fingerswipe or with your password.</P>
-<P CLASS="western">For setting up the screensaver in Lubuntu please
-refer to “Special preparations for Lubuntu” above.</P>
-<OL START=4>
-	<LI><H1 CLASS="western" STYLE="page-break-after: avoid">Exporting
-	Fingerprint Data and Testing PAM Settings</H1>
-</OL>
-<P CLASS="western">With “fingerprint-gui” (“Settings” Tab)
-users can export their fingerprint data (bir files) and test the PAM
-settings of the current machine for proper setup for fingerprint
-authentication.</P>
-<P CLASS="western">With the  “Export now” button all data stored
-for this user (in /var/lib/fingerprint-gui/&lt;username&gt;/) are
-exported to a file “Fingerprints.tar.gz” in the user's home
-directory.</P>
-<P CLASS="western">To test for proper PAM settings the “Test”
-button can be used. First chose the PAM service to be tested then
-click the “Test” button. In case of proper settings the
-fingerprint-helper widget will appear and after a finger swipe the
-message “Authentication successful” will appear in the text field
-below. If nothing happens the PAM settings might be invalid. You can
-press &lt;enter&gt; to abort the test in this case.</P>
-<OL START=5>
-	<LI><H1 CLASS="western">Password Store</H1>
-</OL>
-<P CLASS="western">There are applications that need a password for
-encrypting or decrypting something on your system. Probably
-gnome-keyring is the most widespread of such applications. Also an
-<B>encrypted home directory</B> needs a password to decrypt when a
-user logs in. These applications sometimes get their key for
-decrypting (e.g. for the password safe) by querying the PAM session
-environment for the password given by the user at login. But when the
-user was logged in with a fingerprint there is no password stored in
-the PAM session environment. So the application will prompt the user
-for a password when needed (e.g. if a wireless WPA connection has to
-be established by the Gnome Network Manager or if you want to access
-your email account with Evolution) even if the user was logged in
-already.</P>
-<P CLASS="western" STYLE="margin-top: 0.42cm"><SPAN STYLE="text-decoration: none"><B>Since
-version 0.11 of Fingerprint GUI there is a solution:</B></SPAN> You
-can use some removable media (USB stick) to save your (encrypted)
-password there. If the media is connected to your machine while you
-login with your fingerprint the “pam_fingerprint-gui.so” module
-can decrypt the password and send it to the PAM session environment. 
-</P>
-<P CLASS="western" STYLE="margin-top: 0.42cm"><B>PLEASE READ
-CAREFULLY NOW AND USE THIS FEATURE ONLY IF YOU UNDESTAND HOW IT
-WORKS!</B></P>
-<P CLASS="western" STYLE="margin-top: 0.42cm">If you use the
-“Password” tab of “fingerprint-gui” you can chose a directory
-on some removable media, then type your login password twice and
-click the “Save” button. The removable media must be mounted and
-you must have write permission there. This is where “fingerprint-gui”
-creates a subdirectory “.fingerprints” and writes a file
-“&lt;<A CLASS="western" HREF="mailto:username@×××××××××××.xml">username&gt;@&lt;machinename&gt;.xml</A>”
-containing the encrypted password. The key for decrypting this
-password, the path for the “&lt;<A CLASS="western" HREF="mailto:username@×××××××××××.xml">username&gt;@&lt;machinename&gt;.xml</A>”
-file and the UUID of the removable media are saved in a file
-“/var/lib/fingerprint-gui/&lt;username&gt;/config.xml” (probably
-on your local HDD).</P>
-<P CLASS="western" STYLE="margin-top: 0.42cm">When you login using
-your fingerprint the “pam_fingerprint-gui.so” module reads the
-“/var/lib/fingerprint-gui/&lt;username&gt;/config.xml” file,
-finds the “&lt;<A CLASS="western" HREF="mailto:username@×××××××××××.xml">username&gt;@&lt;machinename&gt;.xml</A>”
-file on the removable media (if it is connected and has the given
-UUID), mounts it, decrypts the password and saves it to the PAM
-session environment where gnome-keyring or other permitted
-applications can read it. This avoids your system asking for the
-password again. 
-</P>
-<P CLASS="western" STYLE="margin-top: 0.42cm">In case of a
-fingerprint login to a session with an encrypted user home a message
-“!!!ERROR: FOUND ENCRYPTED HOMEDIR BUT NO PASSWORD!!!&quot; will
-appear in the gdm greeter and the login by fingerprint will fail,
-when the external media keeping the encrypted password could not be
-found.</P>
-<P CLASS="western" STYLE="margin-top: 0.42cm"><B>PLEASE NOTE THE
-FOLLOWING RESTRICTIONS:</B></P>
-<UL>
-	<LI><P CLASS="western" STYLE="margin-top: 0.42cm">Do <U>not</U> use
-	this feature if someone other then you has root permissions on this
-	machine. This is because root can connect to the machine via telnet,
-	ssh or something like this, mount the external media, find the
-	“&lt;<A CLASS="western" HREF="mailto:username@×××××××××××.xml">username&gt;@&lt;machinename&gt;.xml</A>”
-	file, read the “/var/lib/fingerprint-gui/&lt;username&gt;/config.xml”
-	file and decrypt your password.</P>
-	<LI><P CLASS="western" STYLE="margin-top: 0.42cm">Do <U>not</U>
-	connect the removable media if it isn't needed. The
-	“pam_fingerprint-gui.so” module only needs it while login is in
-	progress. It mounts the partition with the given UUID containing the
-	“&lt;<A CLASS="western" HREF="mailto:username@×××××××××××.xml">username&gt;@&lt;machinename&gt;.xml</A>”
-	file and unmounts it immediately after it has read the file.</P>
-	<LI><P CLASS="western" STYLE="margin-top: 0.42cm">Do <U>never</U>
-	leave the removable media and the computer at the same location
-	unattended. Someone could copy both files and decrypt your password
-	later.</P>
-	<LI><P CLASS="western" STYLE="margin-top: 0.42cm">You don't need to
-	type your password any more so you can use a very long and strong
-	password now. But do <U>not</U> forget your password! You would not
-	be able to unlock your login-keyring any more if your removable
-	media gets lost or corrupted.</P>
-	<LI><P CLASS="western" STYLE="margin-top: 0.42cm">If you change your
-	login password on this machine you need to use “fingerprint-gui”
-	again and save the new password to the removable media.</P>
-</UL>
-<P CLASS="western" STYLE="margin-top: 0.42cm"><U>This is how I use
-this feature for myself:</U></P>
-<P CLASS="western" STYLE="margin-top: 0.42cm">My USB stick has 3
-partitions: One “vfat” (/dev/sdb1) to keep files to be
-transferred to other machines, one “luks_crypto” (/dev/sdb2)
-partition to keep my secret data and a very small (3MB) “ext2”
-(/dev/sdb3) partition to hold the “&lt;<A CLASS="western" HREF="mailto:username@×××××××××××.xml">username&gt;@&lt;machinename&gt;.xml</A>”
-file. Corresponding entries in /etc/fstab ensure that the partitions
-sdb2 and sdb3 are not automatic mounted. Needless to say that I'm the
-only person who has root access to my notebook.</P>
-<P CLASS="western" STYLE="margin-top: 0.42cm">While booting my
-notebook I connect the USB stick until I'm logged in with my
-fingerprint, then remove the stick immediately and reconnect it only
-(and only as long as needed!) if I want to copy something from or to
-it. Because I don't need to invoke my password any more I use a very
-strong and cryptic login password.</P>
-<OL START=6>
-	<LI><H1 CLASS="western">Troubleshooting</H1>
-	<OL>
-		<LI><H2 CLASS="western"><FONT FACE="Arial, sans-serif">Gdm Greeter
-		doesn't show the Fingerprint GUI Widget or needs a long time (up to
-		20 seconds) to show it</FONT></H2>
-	</OL>
-</OL>
-<P CLASS="western" STYLE="margin-top: 0.42cm">This behavior was seen
-on Fedora 12 with SELinux set to “enforcing”. Please set the
-system default of SELinux to “permissive” (or help me setting up
-SELinux rules that can be installed with Fingerprint GUI).</P>
-<OL>
-	<OL START=2>
-		<LI><H2 CLASS="western"><FONT FACE="Arial, sans-serif">Fingerprint-gui
-		Error “Could not open fingerprint device”</FONT></H2>
-	</OL>
-</OL>
-<P CLASS="western">On some systems the file
-“/etc/udev/rules.d/40-libfprint0.rules” (or something like this
-in “/lib/udev/rules.d”) installed by the “libfprint” package
-doesn't work properly. It should help to rename this file so it is
-invoked at a later time. In all known cases renaming it to
-“91-libfprint0.rules” solved the problem. <B>You should also make
-sure your fingerprint scanner hardware has an entry in this file</B>.</P>
-<OL>
-	<OL START=3>
-		<LI><H2 CLASS="western"><A NAME="DDE_LINK"></A><FONT FACE="Arial, sans-serif">Login
-		</FONT>on a secure tty hangs with “OK” Message</H2>
-	</OL>
-</OL>
-<P CLASS="western">If you try to login on a secure tty the prompt
-“Swipe your finger or type your password” appears. If you swipe
-the finger the message “OK” appears and then nothing happens. In
-this case the “uinput” device doesn't work. Make sure the
-“uinput” module is loaded (“lsmod | grep uinput”), the device
-exists in “/dev/input/uinput”, “/dev/misc/uinput” or
-“/dev/uinput” and you have write permission to it. On Ubuntu add
-a line “uinput” to the file “/etc/modules” and restart.</P>
-<OL>
-	<OL START=4>
-		<LI><H2 CLASS="western">You have a fingerprint device from UPEK/SGS
-		Thomson and get some <FONT FACE="Courier New, monospace"><FONT SIZE=2>“ABSOpen()
-		failed...”</FONT></FONT> error message in /var/log/auth.log</H2>
-	</OL>
-</OL>
-<P CLASS="western">This is probably a problem with the proprietary
-UPEK driver (libbsapi.so). Maybe your device needs the &quot;NVM
-emulation&quot;. Please have a look into this document:
-<BR><A CLASS="western" HREF="http://www.n-view.net/Appliance//fingerprint/BSAPIUsageonLinux.pdf">http://www.n-view.net/Appliance//fingerprint/BSAPIUsageonLinux.pdf</A>
-<BR>and try to setup the emulation for your device. 
-</P>
-<OL>
-	<OL START=5>
-		<LI><H2 CLASS="western"><A NAME="DDE_LINK2"></A><FONT FACE="Arial, sans-serif">P</FONT><FONT FACE="Arial, sans-serif">assword
-		can not be saved to removable media</FONT></H2>
-	</OL>
-</OL>
-<P CLASS="western">If you find an entry reading:</P>
-<P CLASS="western" STYLE="margin-top: 0.42cm"><FONT FACE="Courier New, monospace"><FONT SIZE=2>&quot;AES128-CBC
-not supported! Provider (libqca-ossl.so) not installed?&quot;</FONT></FONT></P>
-<P CLASS="western">in the log files, the plugin library for
-encryption is missing. Install the “libqca2-plugin-ossl” package
-(Ubuntu) or a similar encryption plugin.</P>
-<P CLASS="western">In other cases make sure the media is removable,
-contains a valid partition and is mounted with read/write permission.</P>
-<OL START=7>
-	<LI><H1 CLASS="western">Known Limitations</H1>
-	<OL>
-		<LI><H2 CLASS="western">Applications that don't use PAM for
-		prompting a password</H2>
-	</OL>
-</OL>
-<P CLASS="western">The normal way to use PAM for authentication is to
-let the PAM system prompt the user for a username and/or a password.
-PAM uses then a callback function of the calling application for
-prompting something in it's own style. If called back by PAM the
-application can decide how it wants to prompt for name or password;
-if not called back, PAM has performed the authentication in another
-way (fingerprint, smart card, iris scanner or whatever). Maybe they
-didn't understand that or had another reason not to use that
-mechanism, the developers of some applications decided to prompt for
-password or username <U>before</U> calling PAM. In this case the
-“pam_fingerprint-gui.so” plugin is called at a time where the
-password is already known by the PAM stack and therefore exits
-immediately. Fingerprint authentication is not possible then.</P>
-<OL>
-	<OL START=2>
-		<LI><H2 CLASS="western">Missing XAUTHORITY environment variable</H2>
-	</OL>
-</OL>
-<P CLASS="western">When calling PAM some applications don't have a
-XAUTHORITY variable in their environment. “pam_fingerprint-gui.so”
-tries hard to find the “MIT Magic Cookie” to be used to connect
-to the current display but in some cases it fails. I guess this is in
-several KDE applications the reason for not being able to show the
-fingerprint widget. Maybe I'll find some better solution in a later
-version.</P>
-<OL>
-	<OL START=3>
-		<LI><H2 CLASS="western" STYLE="page-break-after: avoid">Other <FONT FACE="Arial, sans-serif">Linux</FONT>
-		distributions</H2>
-	</OL>
-</OL>
-<H3 CLASS="western">Debian 4.0</H3>
-<P CLASS="western">I didn't find any way to install libfprint. There
-is neither a package available nor do the sources compile without
-errors. Didn't want to waste more time with it.</P>
-<H3 CLASS="western">SuSE 11.1 (gnome edition)</H3>
-<P CLASS="western">The gdm used in SuSE behaves totally strange. It
-doesn't allow to show the fingerprint widget. Maybe it's only some
-setting to be changed or the original source installation of gdm to
-be used. Neither found any useful documentation about it nor had the
-time to try a fresh compiled gdm from sources. I gave up!</P>
-<H3 CLASS="western">Slackware</H3>
-<P CLASS="western">Slackware might need someone who has enough spare
-time to make it “PAM aware”. Not me!</P>
-<P CLASS="western"><BR><BR>
-</P>
-<P CLASS="western"><B>So if you are interested to bring Fingerprint
-GUI to work on some other distributions first read the “Hacking”
-document of this project for hints about how it works. If you need
-further information about it contact me. If you managed to make it up
-and running write a HowTo and let me know.</B></P>
-<P CLASS="western"><BR><BR>
-</P>
-<P CLASS="western" STYLE="border-top: none; border-bottom: 1.00pt solid #000000; border-left: none; border-right: none; padding-top: 0cm; padding-bottom: 0.07cm; padding-left: 0cm; padding-right: 0cm">
-<B>Ubuntu and Fedora users should have no serious problems; so have
-fun with it!</B></P>
-<P CLASS="western"><BR><BR>
-</P>
-</BODY>
-</HTML>
\ No newline at end of file

diff --git a/sys-auth/fingerprint-gui/fingerprint-gui-1.00.ebuild b/sys-auth/fingerprint-gui/fingerprint-gui-1.00.ebuild
deleted file mode 100644
index 4fd6c06..0000000
--- a/sys-auth/fingerprint-gui/fingerprint-gui-1.00.ebuild
+++ /dev/null
@@ -1,60 +0,0 @@
-# Copyright 1999-2010 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-# $Header: $
-
-EAPI="3"
-
-inherit qt4-r2 versionator multilib
-#pam
-
-MY_PV=$(replace_version_separator 2 -)
-DESCRIPTION="Use Fingerprint Devices with Linux"
-HOMEPAGE="http://www.n-view.net/Appliance/fingerprint/"
-SRC_URI="http://www.n-view.net/Appliance/fingerprint/download/${PN}-${MY_PV}.tar.gz"
-
-LICENSE="GPL-3"
-SLOT="0"
-KEYWORDS="~x86 ~amd64"
-IUSE="upekbsapi"
-
-DEPEND="
-	!sys-auth/pam_fprint
-	!sys-auth/fprintd
-	!sys-auth/thinkfinger
-	>=sys-auth/libfprint-0.1.0_pre2
-	x11-libs/libfakekey
-	>=app-crypt/qca-2.0.0
-	>=app-crypt/qca-ossl-2.0.0_beta3
-	sys-auth/upekbsapi-bin[headers]
-	x11-libs/qt-core:4
-	x11-libs/qt-gui:4
-"
-RDEPEND="${DEPEND}"
-
-S="${WORKDIR}/${PN}-${MY_PV}"
-
-src_configure() {
-	eqmake4 \
-		PREFIX="$EROOT/usr" \
-		LIB="$(get_libdir)" \
-		LIBEXEC=libexec \
-		LIBPOLKIT_QT=LIBPOLKIT_QT_1_1 || die "qmake4 failed"
-}
-
-src_install() {
-	emake INSTALL_ROOT="${D}" DESTDIR="${D}" install || die "emake install failed"
-	domenu bin/fingerprint-gui/fingerprint-gui.desktop
-	dodoc CHANGELOG README IMPORTANT-UPGRADE-INFORMATION.txt \
-		"${FILESDIR}/Install-step-by-step.html"
-}
-
-pkg_postinst() {
-	elog "1) You may want to add the followingline to the first of /etc/pam.d/system-auth"
-	elog "   auth        sufficient  pam_fingerprint-gui.so"
-	elog "2) You must be in the plugdev group to use fingerprint"
-	if use upekbsapi; then
-		elog "3) You select to install upeks bsapi library, it's not open-sourced."
-		elog "   Use it in your own risk."
-	fi
-	elog "*) Please see /usr/share/doc/${P}/Install-step-by-step.* to configure your device"
-}

diff --git a/sys-auth/upekbsapi-bin/Manifest b/sys-auth/upekbsapi-bin/Manifest
deleted file mode 100644
index 2b5408e..0000000
--- a/sys-auth/upekbsapi-bin/Manifest
+++ /dev/null
@@ -1 +0,0 @@
-DIST fingerprint-gui-1.00.tar.gz 3781064 SHA256 4d826156e553076f6d7817c4a347ab955e81c44c355ec10b7ab2d3d7732136f5 SHA512 5372964ea5f75b51362316041eb1504cb235c016a615870a88994e4c566561a98c630b400203752bb4ac40c82d881a31a19304b664928ce0c1a03ff7134c362c WHIRLPOOL 9a7a3c5b545bdccc4af86cfabd1b4f9d9bb2996568540e338e7926a6f2453dc8d6113b978c6eb6202bfcd360aa44a8163fbdd92c7f51b57a2440c8d50010196d

diff --git a/sys-auth/upekbsapi-bin/upekbsapi-bin-4.0.0218.ebuild b/sys-auth/upekbsapi-bin/upekbsapi-bin-4.0.0218.ebuild
deleted file mode 100644
index 1e3f1a4..0000000
--- a/sys-auth/upekbsapi-bin/upekbsapi-bin-4.0.0218.ebuild
+++ /dev/null
@@ -1,47 +0,0 @@
-# Copyright 1999-2010 Gentoo Foundation
-# Distributed under the terms of the GNU General Public License v2
-# $Header: $
-
-EAPI="3"
-
-FP_GUI=fingerprint-gui-1.00
-MY_PN=${PN/bsapi-bin/}
-DESCRIPTION="UPEK Biometric Services SDK for PC"
-HOMEPAGE="http://www.upek.com/solutions/eikon/default.asp"
-SRC_URI="http://www.n-view.net/Appliance/fingerprint/download/${FP_GUI}.tar.gz"
-
-LICENSE="UPEK_EULA"
-SLOT="0"
-KEYWORDS="~x86 ~amd64"
-IUSE="+headers"
-
-DEPEND=""
-RDEPEND="${DEPEND}"
-
-S=${FP_GUI}/${MY_PN}
-
-src_unpack() {
-	unpack ${FP_GUI}.tar.gz
-}
-
-src_install() {
-	cd "${S}"/
-	if use headers; then
-		insinto /usr/include
-		doins include/bsapi.h
-		doins include/bserror.h
-		doins include/bstypes.h
-	fi
-	if use x86; then
-		dolib lib/libbsapi.so
-	elif use amd64; then
-		dolib lib64/libbsapi.so
-	fi
-	insinto /etc/udev/rules.d
-	doins 91-fingerprint-gui-upek.rules
-	dodir /var/lib/${MY_PN}_data
-	fperms 777 /var/lib/${MY_PN}_data
-	echo "nvmprefix=\"/var/lib/${MY_PN}_data/.NVM\" dualswipe=0" > ${MY_PN}.cfg
-	insinto /etc
-	doins ${MY_PN}.cfg
-}