Privaris LFBT1-01 A personal handheld biometric security device User Manual

Privaris Inc. A personal handheld biometric security device

Contents

Users Manual

BPID™ LFBT Security Device USER MANUAL AND LICENSING AGREEMENT VERSION 1.4 www.privaris.com
Privaris BPID™ LFBT Security Device, V1.4 Congratulations on receiving your new BPID™ Security Device. Record your device’s unique Bluetooth™ address here: __ __ : __ __ : __ __ : __ __ : __ __ : __ __ The Bluetooth™ address is found on the back of your device. It is a 12 character string of letters and numbers separated by colons. For optimal results and convenience using your device, it is important that you read this manual. In addition to instructions for proper device usage, information is included on the device itself - how it works, its personal privacy features, troubleshooting guidelines, and answers to frequently asked questions. IMPORTANT. READ BEFORE USING FOR SUCCESSFUL DEVICE OPERATION FOLLOW THESE GUIDELINES:  Ensure that fingers are free of excessive dirt or grease. Clean fingers with a tissue, or on a clean article of clothing. You do not need to wash your hands prior to device use.  Always attempt to place your finger on the fingerprint sensor in the same position in which you placed it during the enrollment process - the Center Position.  Never press hard or squeeze the device. Press just enough to make solid contact with the sensor.  Always keep your finger flat and level with the device when placing it on the fingerprint sensor. The knuckle should never be raised or bent. ©2005 Privaris, Inc. 1
Privaris BPID™ LFBT Security Device, V1.4 1. WHAT IS A BPID™ SECURITY DEVICE? 3 OVERVIEW 3 DEVICE DIAGRAM 3 APPLICATIONS 4 2. USAGE INSTRUCTIONS 5 STEP 1: ACTIVATION 5 STEP 2: USING YOUR DEVICE 5 - FACILITY ACCESS 5 - COMPUTER OR NETWORK LOGON 6 3. BATTERY REPLACEMENT 7 BATTERY LEVEL INDICATORS 7 CHANGING THE BATTERY 7 4. SECURITY & PERSONAL PRIVACY 8 5. HOW IT WORKS 9 ENROLLMENT 9 TVERIFICATION 9 TRANSMISSION 9 6. GENERAL TROUBLESHOOTING 10 7. FACILITY ACCESS TROUBLESHOOTING 14 8. COMPUTER/NETWORK LOGON TROUBLESHOOTING 15 9. FREQUENTLY ASKED QUESTIONS 18 10. CUSTOMER SERVICE 20 11. WARRANTY 21 12. LICENSING AGREEMENT 22 13. PERMISSIONS 25 2
Privaris BPID™ LFBT Security Device, V1.4 1. WHAT IS A BPID™ SECURITY DEVICE? Overview A BPID™ Security Device is a wireless, biometric personal identification device that provides identity verification using fingerprint biometrics. Because no two fingerprints are identical, biometric verification significantly heightens security levels by ensuring that the intended and authorized user of the device is the only person for whom the device will function. The BPID™ device uses fingerprints to verify its user’s identity before granting access to a specific resource. It works in much the same way that a remote control is used to operate a television or a garage door, but instead requires the authorized user’s fingerprint to “unlock” and operate the device. Device Diagram Figure 1: Front of Device Figure 2: Back of Device 3
Privaris BPID™ LFBT Security Device, V1.4 The BPID™ Security Device’s design is simple and user-friendly. The device has four components: Lights: A green, yellow and red light help to prompt the user through device operation and communicate to the user what mode the device is in. Power Button: Turns the device on and off Fingerprint Sensor: Scans a user’s fingerprint and either grants or denies access to a particular resource. Battery Compartment: Located under a sliding cover. The cover is removed using the battery release. Applications The BPID™ Security Device replaces standard forms of identity verification. Examples of possible applications include the use of a BPID™:  In place of a proximity (prox) card for access through a door or gate  In place of a key to access a home, garage or automobile  In place of a password to access a computer or network  In place of a driver’s license, passport, or corporate ID card to verify an individual’s identity  In place of a credit card to purchase items without having to swipe a traditional credit card or sign for the purchase. 4
Privaris BPID™ LFBT Security Device, V1.4 2. USAGE INSTRUCTIONS Step 1: Activation In order to activate a BPID™ Security Device you must be enrolled in the device. Enrollment is the device issuance process and is typically managed by an organization’s issuing authority, such as the Information Technology Department, Security Office, or Human Resources Department. Enrollment initializes the device and “marries” it to its owner. During enrollment, users are asked to place their finger on the device several times in order for the fingerprint sensor to scan and securely store their print’s features. Once enrolled in a device, it is activated and ready for use. Step 2: Using Your Device FACILITY ACCESS (secured doorways or gated entrances): 1. Open the device’s clear plastic flip-cover. 2. Click the round gray Power Button once. -A blinking yellow light will indicate that the device is on and is awaiting a finger. 3. With the yellow light blinking, place an enrolled finger on the device’s fingerprint sensor in a position used during enrollment. -A solid yellow light will indicate that the device is scanning your finger. 4. A solid green light indicates that your fingerprint and your identity have been successfully verified. 5. With the green light still on, touch the tip of your device to the device reader located at the doorway or access point. 6. Your device will wirelessly transmit your programmed credentials to the access point. 7. Access to the facility is permitted. 8. Press the power button to turn off the device. If you forget, it will power off automatically after approximately 10 seconds. 5
Privaris BPID™ LFBT Security Device, V1.4 COMPUTER OR NETWORK LOGON: 1. Ensure that the computer or network is powered on. 2. Ensure that the computer has a Bluetooth™ adaptor. 3. Open the device’s clear plastic flip-cover. 4. Double-click the round gray Power Button. -The green light will continually blink. 5. The device will be detected by a properly configured computer or network and will request verification. -A blinking yellow light will indicate that the device is awaiting verification. 6. With the yellow light blinking, place an enrolled finger on the device’s fingerprint sensor in a position used during enrollment. -A solid yellow light will indicate that the device is scanning your finger. 7. A solid green light indicates that your fingerprint and your identity have been successfully verified. 8. Upon successful verification, the device will securely transmit your password to the computer or network. 9. Access is granted. 10. Press the power button to turn off the device. If you forget, it will power off automatically after a period of time determined by the application. 6
Privaris BPID™ LFBT Security Device, V1.4 3. BATTERY REPLACEMENT The BPID™ Security Device is powered by a CR2 lithium battery, the same type of battery used in many cameras. A replacement battery can be purchased at most camera stores, drug stores, or supermarkets. Battery Level Indicators Low Battery Indicator: A quick flashing red light upon start-up at the same time the yellow light comes on. Very Low Battery Indicator: A quick flashing red light upon start-up and then a flashing red light periodically throughout normal device usage. Critically Low Battery Indicator: A quick flashing red light upon start-up and then the device turns itself off automatically. Changing the Battery 1. Open the battery compartment on the back of the device by inserting the tip of a pen into the battery release (the small square at the bottom of the battery compartment) to pop the release and then slide the cover open (see Figure 2). 2. Remove the old battery. 3. Insert the new battery with the positive (+) end pointing toward the top of the device and ensure that it is secured tightly in the compartment. It should be touching the battery contacts at the top and bottom of the compartment. 4. Replace the battery cover by aligning it with the ridges of the battery compartment and sliding it back into position. Make sure that it is latched securely in place. A loud click is heard when properly closed. Replacing the battery does not require the user to be re-enrolled. 7
Privaris BPID™ LFBT Security Device, V1.4 4. SECURITY & PERSONAL PRIVACY Key points related to the security of the BPID™ device and the user’s personal privacy:  All fingerprint processing is done within the device, so fingerprints do not have to be stored in any type of database, thereby protecting the user’s personal privacy.  The fingerprint is used only for identity verification. Neither the fingerprint nor its features are ever physically transmitted nor ever leave the device. The device wirelessly transmits only the credentials necessary for authorization and access (i.e., a facility entrance code, a password, or personal identity document).  The fingerprint features stored on the device cannot be retrieved from the device.  The device releases the programmed authorization only after the authorized user of the device applies an enrolled finger.  The device’s fingerprint sensor recognizes and rejects a fake finger or other attempts to fool the device. These techniques rely on the specific chemistry of the skin, which is not present in a fake finger.  The device is a cryptographic services provider and supports two-way encrypted communications. Data can be encrypted on the device before it is released so that only the intended recipient can interpret the information. 8
Privaris BPID™ LFBT Security Device, V1.4 5. HOW IT WORKS The BPIDTM Security Device has three functions: enrollment, verification, and transmission. Enrollment Enrollment is the device activation and issuance process and generally occurs only once. It is what assigns or “marries” the device to its user. During enrollment, numeric representations of the unique features of a fingerprint (i.e. the ridges, valleys and whorls) are encoded and securely stored on the BPIDTM device. The actual fingerprint is not stored on the device. The fingerprint features are encoded and securely stored so that the device will function only for its authorized user. Also during enrollment, the user’s credentials (e.g. a facility entrance code, a password, or personal identity document) are typically encrypted and wirelessly transferred and stored on the BPID™ device. Verification After the initial enrollment process, each time a finger is placed on the BPID™ device, the device will attempt to match that print’s features to an originally enrolled fingerprint. This is the verification, or matching, process. A match is indicated by a green light and means that the user has been verified as the authorized owner of the device. If a user attempts to verify a non-enrolled finger, a match will not be found and access to the specified resource will not be granted. Failed verification attempts are indicated by a red light. Transmission Upon verification, which is the matching of a live finger to the template of an enrolled finger, the BPID™ device wirelessly transmits the user’s credentials that were stored during enrollment (e.g. a facility entrance code, a password, or personal identity documents). The transmission is verification of the user’s identity. The credentials are transferred typically as an encrypted data stream, depending on the application. Only the authorized user’s finger can trigger the release of their credentials, and only the user’s credentials are transferred - the stored fingerprint is never transferred and never released from the device. The BPID™ Security Device can store and transmit any number of user credentials including digital certificates. It supports both BluetoothTM and RFID wireless communication protocols for data transmission. 9
Privaris BPID™ LFBT Security Device, V1.4 6. GENERAL TROUBLESHOOTING PROBLEM Difficulty verifying. Getting solid red light instead of a solid green light. Try the following, in order, until capture speed increases or a green light appears:  Make sure you are using a finger that was enrolled.  Wipe-off any excess dirt or grease from finger.  Wipe-off the sensor with a clean finger, swiping it down the sensor twice to clean it.  Make sure your fingerprint core is directly over the very center of the sensor in the Center Position, and not aligned with the bottom edge of the sensor. Remember the placement reference point given during enrollment and try to replicate it. Unless you have very small fingers, you will likely be covering all or a portion of the grey power button.  Lift finger and replace it during verification, trying slightly different positions on and around the Center Position (core). Be sure to hold in place for 2 seconds before moving to a new position to give the device sufficient time to interpret your fingerprint.  Too little or too much pressure may be being applied. While the sensor is scanning, increase the pressure for a few seconds, and then decrease it to find the right amount. On a scale of 1 – 5 (5 being the highest) pressure should equal about a “2.” Less than or greater than “2” can present recognition difficulties.  Hold the device with only one hand, or just as you did during enrollment.  Keep finger flat and level with the sensor. The knuckle should never be raised or bent.  If still getting a red light, turn the device off and back on, and try verifying with a different enrolled finger. 10
Privaris BPID™ LFBT Security Device, V1.4 PROBLEM Device will not power on. 1. Open battery compartment by inserting tip of pen into the battery release (see Figure 2). 2. Remove cover. 3. Remove battery. 4. Put the same battery back, making sure that it is secured tightly and properly aligned. It should be touching the battery contacts on the top and bottom of the compartment, and the positive (+) end should be pointing toward the tip of the device. 5. Replace the battery cover by aligning it with the ridges of the battery compartment and sliding it back into position. Make sure that it is latched securely in place. A loud click is heard when properly closed. If the device still does not power on, replace the battery with a new one (see below). __________________________________________________________ PROBLEM Quick flashing red light seen anytime during operation OR a quick flashing red light and then device powers itself off. A flashing red light is an indication of a low or critically low battery. 1. Replace battery. The battery is a standard CR2 lithium camera battery. It can be easily replaced by inserting the tip of a pen into the battery release (see Figure 2) and pressing down to release the battery cover. 2. Remove the old battery and insert the new battery with the positive (+) end pointing toward the top of the device and ensure that it is secured tightly in the compartment. It should be touching the battery contacts at the top and bottom of the compartment. 3. Replace the battery cover by aligning it with the ridges of the battery compartment and sliding it back into position. Make sure that it is latched securely in place. A loud click is heard when properly closed. Replacing the battery does not require the user to be re-enrolled. 11
Privaris BPID™ LFBT Security Device, V1.4 PROBLEM Difficulty identifying correct device mode, i.e., facility access or computer logon. If the device is blinking yellow it is ready to be used for facility access. If the device is blinking green it is ready to be used for computer or network logon. To access a particular mode from a powered off state: For facility access: Press power button once. The device will blink yellow. For computer/network access: Double-click the power button. The device will blink green. Note: Once the computer detects the device’s presence, the device will change from blinking green to blinking yellow to request a finger for verification. PROBLEM All three lights (green, yellow and red) are blinking quickly. Whenever all three lights on the device are blinking simultaneously, the device has entered its Safe Mode. This typically occurs when the power button has been held down for an excessive period of time. To reset the device, simply press the power button to power off the device. Then power it back on by pressing and quickly releasing the power button. The device should now operate normally. PROBLEM Device will not connect to a third party software application. If you were enrolled in the device by an issuing authority (your company or other) and subsequently attempt to install applications from software vendors other than Privaris that use the BPID™ device, you may experience connectivity problems with that application (error messages such as "unable to connect with device" or "communication with device failed"). If this occurs your device 12
Privaris BPID™ LFBT Security Device, V1.4 may have been "keyed" during enrollment. Please see your issuing authority to obtain the license key and permission to use it with the intended application. 13
Privaris BPID™ LFBT Security Device, V1.4 7. FACILITY ACCESS TROUBLESHOOTING PROBLEM Seeing a green light and successfully verifying, but not being granted access to facility. 1. After a successful verification, with the green light lit, take your device and physically touch the tip of it to the reader at the facility access point. Try touching different points on the reader. 2. If still not working, try verifying again, but take the device to a reader at a different facility access point and try again. 3. If the device works at another access point, then there is a problem with the reader at the first access point. Report problem to issuing authority. 4. If the device does not work at either access point, it is likely a problem with your device. See the issuing authority for troubleshooting assistance with your device. PROBLEM Difficulty identifying correct device mode, i.e., facility access or computer logon. If the device is blinking yellow it is ready to be used for facility access. If the device is blinking green it is ready to be used for computer or network logon. To access a particular mode from a powered off state: For facility access: Press power button once. The device will blink yellow. For computer/network access: Double-click the power button. The device will blink green. Note: Once the computer detects the device’s presence, the device will change from blinking green to blinking yellow to request a finger for verification. 14
Privaris BPID™ LFBT Security Device, V1.4 8. COMPUTER/NETWORK LOGON TROUBLESHOOTING PROBLEM Device powers off when changing from facility access mode to computer/network access mode. The power button must be clicked twice within one second to enter computer/network access mode. If one second is exceeded, the device interprets the second push of the power button as a power off command. Try again, this time clicking the power button quickly. PROBLEM Cannot gain access to computer or network. 1. Make sure that your computer is equipped with a Bluetooth™ adaptor (either inserted in your computer’s USB port or built-in). 2. You may be having trouble verifying. Walk through each of the following steps below in order, until capture speed increases or a green light appears:  Make sure you are using a finger that was enrolled.  Wipe-off any excess dirt or grease from finger.  Wipe-off the fingerprint sensor with a clean finger, swiping it down the sensor twice to clean it.  Make sure your fingerprint core is directly over the very center of the sensor, and not aligned with the bottom of the sensor. Remember the placement reference point given during enrollment and try to replicate it. Unless you have very small fingers, you will likely be covering all or a portion of the grey power button.  Lift finger and replace it during verification, trying slightly different positions on and around the Center Position (core). Be sure to hold in place for 2 seconds before moving to a new position to give the device sufficient time to interpret your fingerprint.  Too little or too much pressure may be being applied. While the sensor is scanning, increase the pressure for a few seconds, and then decrease it to find the right amount. This will often help to trigger a green light. On a scale of 1 – 5 (5 15
Privaris BPID™ LFBT Security Device, V1.4 being the highest) pressure should equal about a “2.” Less or greater than “2” can present recognition difficulties.  Hold the device with only one hand, and just as you did during enrollment.  Keep finger flat and level with the sensor. The knuckle should never be raised or bent.  If still getting a red light, turn the device off, turn it back on, and try verifying with a different enrolled finger. 3. If none of the above solves the problem, the issue is likely with the logon software that resides on your computer or network. Defer to the issuing authority or the software’s user manual for assistance. PROBLEM Difficulty identifying correct device mode, i.e., facility access or computer logon. If the device is blinking yellow it is ready to be used for facility access. If the device is blinking green it is ready to be used for computer or network logon. To access a particular mode from a powered off state: For facility access: Press power button once. The device will blink yellow. For computer/network access: Double-click the power button. The device will blink green. Note: Once the computer detects the device’s presence, the device will change from blinking green to blinking yellow to request a finger for verification. PROBLEM Device will not connect to a third party software application. If you were enrolled in the device by an issuing authority (your company or other) and subsequently attempt to install applications from software vendors other than Privaris that use the BPID™ device, you may experience connectivity problems with that application (error messages such as "unable to connect with device" 16
Privaris BPID™ LFBT Security Device, V1.4 or "communication with device failed"). If this occurs your device may have been "keyed" during enrollment. Please see your issuing authority to obtain the license key and permission to use it with the intended application. 17
Privaris BPID™ LFBT Security Device, V1.4 9. FREQUENTLY ASKED QUESTIONS How do I turn on my device? Press and quickly release the round gray Power Button located on the front of the device. One click will start the device in facility access mode. A double-click will start the device in computer/network access mode. How do I know when my device is ready for verification? A blinking yellow light indicates that the device is ready to accept a finger for verification. For facility access this occurs after you turn on your device. For computer/network access, this occurs after the computer has made a connection to your device. How will I know if the device has successfully verified my fingerprint? A solid green light will display indicating a successful verification and you will be simultaneously granted access to the facility or computer/network. How much pressure do I need to apply with my finger? The sensor works best with enough pressure to make solid contact. Do not squeeze the device, and do not simply rest your finger on the sensor. On a scale of 1 – 5 (5 being the highest) pressure should equal about a “2.” Less or greater than “2” can present recognition difficulties. If your finger is on the sensor but the device is still blinking yellow, then you are not pressing hard enough. What if I injure my finger? During enrollment at least two fingers will be enrolled in your device. So if you were to injure your primary finger, you’ll have another to use as a temporary back up. What if my device is lost or stolen? As soon as you discover your device is missing, contact your issuing authority and you should be supplied with a replacement device. You will have to be enrolled in your new device. And remember, your device is useless in anyone’s hands but your own, so if it is lost or stolen, there is no concern that anyone else will be granted access with your device. What happens if I drop my device? Your device is constructed to withstand most accidents. But like any electronic device, significant unintentional or intentional mishandling may render the device inoperable. 18
Privaris BPID™ LFBT Security Device, V1.4 Is my fingerprint stored on the device? No. Your fingerprint itself is not stored. Only numeric representations of unique features of your fingerprint (for example, specific ridges, valleys or whorls) are encoded and stored on the device in the form of a template. These numeric representations are used in the matching process that confirms you as the authorized user of the device, and cannot be used to regenerate your actual fingerprint. Is my fingerprint transmitted from the device? No. When your device matches your live fingerprint to your stored fingerprint template it wirelessly transmits a stored credential which confirms your identity. Your fingerprint is never transmitted. Neither your fingerprint nor its features can ever leave your device, and it is impossible to recreate your original fingerprint from the device. Can my fingerprint be faked and the security of my device compromised? The fingerprint sensor on your device uses sensing technology that allows it to reject a fake finger or other attempts to fool the device. The sensor actually looks beyond the surface of your finger at the inner layers of your skin where your fingerprint features are formed. These techniques rely on the specific chemistry of your skin, which is not present in a fake finger. Can my fingerprints be accessed from my device? No. The device does not permanently store your actual fingerprint. Numeric representations of specific unique features of your fingerprint are encoded and stored on the device and used in the matching process that confirms you as the authorized user of the device. These numeric representations cannot be converted into your actual fingerprint. Can a third party steal my credentials while they are being wirelessly transmitted to or from my device? Typically, all information sent to or from your device is encrypted. This prevents a third party from intercepting the information as it is transmitted. For some low frequency physical access applications, encryption is not an option; however the close proximity required for access significantly reduces the possibility of a transmission being intercepted without notice. 19
Privaris BPID™ LFBT Security Device, V1.4 10. CUSTOMER SERVICE If the information contained herein has not answered your question(s) regarding your device, or to return defective products, please contact Privaris Customer Service at (866) 213-8252. 20
Privaris BPID™ LFBT Security Device, V1.4 11. WARRANTY Limited Warranty. Licensor warrants that the Software will, for a period of one (1) year following its delivery to you, be in good working order and will conform in all material respects to Licensor's published specifications. Licensor does not warrant that the operation of the Software will be uninterrupted or error-free, or that the functionality of the Software will meet your individualized requirements. The foregoing warranty does not cover repair for damages, malfunctions, or service failures caused by (1) actions of any non-Licensor personnel, you’re your failure to follow Licensor's installation, operation, or maintenance instructions, (3) attachment to or incorporation in the Software of non-Licensor products not supported or otherwise authorized by Licensor, or (4) or any factor beyond Licensor's control, including fire, explosion, lightning, pest damage, power surges or failures, strikes or labor disputes, water, acts of God, the elements, war, terrorism, civil disturbances, acts of civil or military authorities or the public enemy, transportation facilities, fuel or energy shortages, or acts or omissions of communications carriers. EXCEPT FOR THE WARRANTIES SET FORTH IN THIS SECTION 6, THE SOFTWARE IS LICENSED "AS IS," AND LICENSOR DISCLAIMS ANY AND ALL OTHER WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, QUALITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY, OR INTERFERENCE WITH YOUR ENJOYMENT OF THE SOFTWARE OR OF NON-INFRINGEMENT. YOUR SOLE REMEDY AGAINST LICENSOR, ITS AFFILIATES, SUBCONTRACTORS, AND REPRESENTATIVES FOR LOSS OR DAMAGE CAUSED BY ANY FAILURE OF THE SOFTWARE TO OPERATE IN CONFORMITY WITH THIS WARRANTY, REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT OR TORT, INCLUDING NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, SHALL BE (1) THE REPAIR OR REPLACEMENT OF THE SOFTWARE, PROVIDED THAT SUCH SOFTWARE IS RETURNED IN ACCORDANCE WITH THE CONDITIONS PROVIDED HEREIN OR (2) IF SUCH REPAIR CANNOT BE MADE OR AN EQUIVALENT REPLACEMENT CANNOT BE PROVIDED, THE REFUND OF AMOUNTS PREVIOUSLY PAID BY YOU BETWEEN DISCOVERY OF THE FAILURE OF THE SOFTWARE TO OPERATE IN CONFORMITY WITH THIS WARRANTY AND THE RETURN OF THE SOFTWARE AS REQUIRED BY THIS AGREEMENT. 21
Privaris BPID™ LFBT Security Device, V1.4 12. LICENSING AGREEMENT READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT (“AGREEMENT”) CAREFULLY BEFORE OPENING THIS PACKAGE. THE SOFTWARE APPLICATIONS AND THE ACCOMPANYING USER DOCUMENTATION CONTAINED IN THIS PACKAGE ARE COPYRIGHTED AND ARE LICENSED (NOT SOLD) TO YOU IN ACCORDANCE WITH THE TERMS OF THIS AGREEMENT. BY OPENING THIS PACKAGE, YOU MANIFEST YOUR ASSENT TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT ASSENT TO BE BOUND BY THE TERMS OF THIS AGREEMENT, THEN YOU MUST PROMPTLY RETURN THIS PACKAGE, IN UNOPENED FORM, AND YOU WILL RECEIVE A REFUND OF YOUR MONEY. 1. Generally. This Agreement represents the entire agreement between you, the end user (either in your individual capacity or as an authorized agent of an otherwise legally-recognized organization), and Privaris, Inc. (“Licensor”) relating to the software that is pre-installed on the hardware product(s) (“Hardware”) enclosed within this package, as well as all documentation related thereto (collectively, the “Software”). This Agreement supersedes any prior proposal, representation, or understanding between you and Licensor related to the Software. This is a legally-binding agreement and governs the conditions under which you and/or your organization may use the Software. 2. Term. This Agreement is effective on your opening of this package and shall continue until terminated as set forth in this Agreement. You may terminate this Agreement at any time by returning the Hardware and all copies of the Software to Licensor. Licensor may terminate this Agreement on the breach by you of any term of this Agreement, including without limitation your failure to pay any applicable fees described in this Agreement. On any such termination, you shall return to Licensor the Hardware and all copies of the Software. 3. Grant of Licenses. Licensor grants you the personal, nontransferable, nonsublicensable and nonexclusive right and license to execute the Software (in its executable, object-code form only) on the Hardware for the sole purpose of serving your personal needs or the internal needs of your business. You shall not assign, sublicense, transfer, pledge, lease, rent, or share your rights under this Agreement, whether by contract, operation or law or otherwise. Any use, copying, or 22
Privaris BPID™ LFBT Security Device, V1.4 distribution of the Software not expressly authorized by this Agreement shall automatically terminate your right and license hereunder. This grant shall be limited to use of the Software with the Hardware in accordance with the terms of this Agreement. 4. Trade Secret Protection. The Software contains substantial trade secrets of Licensor, and you shall employ reasonable security precautions to maintain the confidentiality of such trade secrets. You shall not "unlock," decompile, or reverse-assemble the binary or object code portions or versions of the Software, as the terms are generally used in the computer industry. 5. Fees. The fees for the use of the Software in accordance with this Agreement consist of the initial license fee that is incorporated as part of the purchase price of the Hardware purchased by you from Licensor, its authorized resellers or its authorized licensees. The dollar amount of such fees and the terms of payment are specified in the product invoice separately furnished to you. You shall pay such fees to Licensor in accordance with the terms of such product invoice. 6. Limited Warranty. Licensor warrants that the Software will, for a period of one (1) year following its delivery to you, be in good working order and will conform in all material respects to Licensor's published specifications. Licensor does not warrant that the operation of the Software will be uninterrupted or error-free, or that the functionality of the Software will meet your individualized requirements. The foregoing warranty does not cover repair for damages, malfunctions, or service failures caused by (1) actions of any non-Licensor personnel, you’re your failure to follow Licensor's installation, operation, or maintenance instructions, (3) attachment to or incorporation in the Software of non-Licensor products not supported or otherwise authorized by Licensor, or (4) or any factor beyond Licensor's control, including fire, explosion, lightning, pest damage, power surges or failures, strikes or labor disputes, water, acts of God, the elements, war, terrorism, civil disturbances, acts of civil or military authorities or the public enemy, transportation facilities, fuel or energy shortages, or acts or omissions of communications carriers. EXCEPT FOR THE WARRANTIES SET FORTH IN THIS SECTION 6, THE SOFTWARE IS LICENSED "AS IS," AND LICENSOR DISCLAIMS ANY AND ALL OTHER WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, QUALITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY, OR INTERFERENCE WITH YOUR ENJOYMENT OF THE SOFTWARE OR OF NON-INFRINGEMENT. YOUR SOLE REMEDY AGAINST 23
Privaris BPID™ LFBT Security Device, V1.4 LICENSOR, ITS AFFILIATES, SUBCONTRACTORS, AND REPRESENTATIVES FOR LOSS OR DAMAGE CAUSED BY ANY FAILURE OF THE SOFTWARE TO OPERATE IN CONFORMITY WITH THIS WARRANTY, REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT OR TORT, INCLUDING NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, SHALL BE (1) THE REPAIR OR REPLACEMENT OF THE SOFTWARE, PROVIDED THAT SUCH SOFTWARE IS RETURNED IN ACCORDANCE WITH THE CONDITIONS PROVIDED HEREIN OR (2) IF SUCH REPAIR CANNOT BE MADE OR AN EQUIVALENT REPLACEMENT CANNOT BE PROVIDED, THE REFUND OF AMOUNTS PREVIOUSLY PAID BY YOU BETWEEN DISCOVERY OF THE FAILURE OF THE SOFTWARE TO OPERATE IN CONFORMITY WITH THIS WARRANTY AND THE RETURN OF THE SOFTWARE AS REQUIRED BY THIS AGREEMENT. 7. Limitations on Liability. IN NO EVENT SHALL LICENSOR BE LIABLE FOR INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES, OR FOR LOST PROFITS, SAVINGS, OR REVENUES OF ANY KIND, OR FOR LOST DATA OR DOWNTIME, REGARDLESS OF WHETHER LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE CUMULATIVE LIABILITY OF LICENSOR TO YOUR ORGANIZATION FOR ALL CLAIMS RELATING TO THE SOFTWARE OR THIS AGREEMENT, REGARDLESS OF THE FORM OF ACTION, WHETHER IN CONTRACT OR TORT, INCLUDING NEGLIGENCE, STRICT LIABILITY, OR OTHERWISE, SHALL NOT EXCEED THE TOTAL AMOUNT OF ALL FEES PAID TO LICENSOR HEREUNDER. 8. Miscellaneous. The provisions of Sections 4, 6, 7 and this Section 8 shall continue to apply in accordance with their terms, notwithstanding the termination of this Agreement. References to "your organization" or "you" herein, for purposes of establishing the permitted use of the Software, shall include the operations of any direct or indirect parent or subsidiary company or of any direct or indirect subsidiary company of any such parent company. This Agreement and the rights and obligations of the parties with respect to the Software shall be governed by Virginia law, as it applies to a contract negotiated, executed, and performed in that state and without giving effect to principles of conflicts of law. Any legal action or proceeding arising under this Agreement shall only be initiated in the courts of the Commonwealth of Virginia. Execution and delivery of this Agreement by the parties indicates their intent to submit their disputes, their persons and their property, generally and unconditionally, to the jurisdiction of such courts. Venue shall be proper in any such court. If any action is brought by either 24
Privaris BPID™ LFBT Security Device, V1.4 party to this Agreement against the other party regarding the subject matter of this Agreement, the prevailing party shall be entitled to recover, in addition to any other relief granted, reasonable attorney fees and expenses of litigation. YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT AND UNDERSTAND THIS AGREEMENT AND THAT BY OPENING THIS PACKAGE, YOU MANIFEST YOUR ASSENT TO BE BOUND BY ITS TERMS AND CONDITIONS. 13. PERMISSIONS Portions of the software on the BPID™ Security Device may be subject to the following copyright notices: Copyright (c) 1990 The Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph are duplicated in all such forms and that any documentation, and other materials related to such distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the University may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Copyright (c) 1988, 1990, 1993 Regents of the University of California. 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. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``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 REGENTS 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. Copyright (c) 1982, 1986, 1989, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. (c) UNIX System Laboratories, Inc. All or some portions of this file are derived from material licensed to the University of California by American Telephone and Telegraph Co. or Unix System Laboratories, Inc. and are reproduced herein with the permission of UNIX System Laboratories, Inc. 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 25
Privaris BPID™ LFBT Security Device, V1.4 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 software developed by the University of California, Berkeley and its contributors. 4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``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 REGENTS 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 author of this software is David M. Gay. Copyright (c) 1991 by AT&T. Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software. THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR AT&T MAKES ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. Copyright 1989, 1990 Advanced Micro Devices, Inc. This software is the property of Advanced Micro Devices, Inc (AMD) which specifically grants the user the right to modify, use and distribute this software provided this notice is not removed or altered. All other rights are reserved by AMD. AMD MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS SOFTWARE. IN NO EVENT SHALL AMD BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH OR ARISING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS SOFTWARE. Copyright (C) 1993 C.W. Sandmann (C) Copyright 1992 Eric Backus This software may be used freely so long as this copyright notice is left intact. There is no warrantee on this software. Copyright (C) 1993 by Sun Microsystems, Inc. All rights reserved. Developed at SunPro, a Sun Microsystems, Inc. business. Permission to use, copy, modify, and distribute this software is freely granted, provided that this notice is preserved. (c) Copyright 1986 HEWLETT-PACKARD COMPANY To anyone who acknowledges that this file is provided "AS IS" without any express or implied warranty: permission to use, copy, modify, and distribute this file for any purpose is hereby granted without fee, provided that the above copyright notice and this notice appears in all copies, and that the name of Hewlett-Packard Company not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. 26
Privaris BPID™ LFBT Security Device, V1.4 Copyright (C) 2001 Hans-Peter Nilsson Permission to use, copy, modify, and distribute this software is freely granted, provided that the above copyright notice, this notice and the following disclaimer are preserved with no changes. THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Copyright (c) 2001 Christopher G. Demetriou 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. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``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 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. Copyright 2002 SuperH, Inc. All rights reserved This software is the property of SuperH, Inc (SuperH) which specifically grants the user the right to modify, use and distribute this software provided this notice is not removed or altered. All other rights are reserved by SuperH. SUPERH MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS SOFTWARE. IN NO EVENT SHALL SUPERH BE LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH OR ARISING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS SOFTWARE. Copyright (c) 1999 Kungliga Tekniska Hogskolan (Royal Institute of Technology, Stockholm, Sweden). 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. Neither the name of KTH nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY KTH AND ITS CONTRIBUTORS ``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 KTH 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. 27
Privaris BPID™ LFBT Security Device, V1.4 Copyright (c) 2000, 2001 Alexey Zelkin <phantom@FreeBSD.org> 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. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``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. Copyright (C) 1997 by Andrey A. Chernov, Moscow, Russia. 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. THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``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 REGENTS 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. Copyright (c) 1997-2002 FreeBSD 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. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``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. Copyright (c) 1984,2000 S.L. Moshier 28
Privaris BPID™ LFBT Security Device, V1.4 Permission to use, copy, modify, and distribute this software for any purpose without fee is hereby granted, provided that this entire notice is included in all copies of any software which is or includes a copy or modification of this software and in all copies of the supporting documentation for such software. THIS SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED WARRANTY. IN PARTICULAR, THE AUTHOR MAKES NO REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. Copyright (c)1999 Citrus 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. THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``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. Copyright (c) 1998 Todd C. Miller <Todd.Miller@courtesan.com> 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. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED ``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 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. Copyright (C) 1995-1997 Eric Young (eay@cryptsoft.com) 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 29
Privaris BPID™ LFBT Security Device, V1.4 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. Copyright (c) 1998-2000 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. Copyright (c) 1994, 1997, 2001, 2002 Red Hat Incorporated. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 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. The name of Red Hat Incorporated may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "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 RED HAT INCORPORATED 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. 30
Privaris BPID™ LFBT Security Device, V1.4 Copyright (c) 2001, Dr Brian Gladman <brg@gladman.me.uk>, Worcester, UK. All rights reserved. TERMS Redistribution and use in source and binary forms, with or without modification, are permitted subject to the following conditions: 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. The copyright holder's name must not be used to endorse or promote any products derived from this software without his specific prior written permission. This software is provided 'as is' with no express or implied warranties of correctness or fitness for purpose. 31

Navigation menu