Bitcoin Forum
April 27, 2024, 04:28:38 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2] 3 »  All
  Print  
Author Topic: [ANN] BitSafe Hardware Wallet Now Shipping  (Read 22076 times)
Inaba
Legendary
*
Offline Offline

Activity: 1260
Merit: 1000



View Profile WWW
March 13, 2013, 11:38:45 PM
 #21

This is a fantastic project for the bitcoin community and BFL would love to contribute to it.  Perhaps we can leverage our volume production capability to make these cheap enough to help spread bitcoin to the fringe interest crowd.  In the meantime, if we can help with the development by providing resources, please let us know.


If you're searching these lines for a point, you've probably missed it.  There was never anything there in the first place.
1714192118
Hero Member
*
Offline Offline

Posts: 1714192118

View Profile Personal Message (Offline)

Ignore
1714192118
Reply with quote  #2

1714192118
Report to moderator
1714192118
Hero Member
*
Offline Offline

Posts: 1714192118

View Profile Personal Message (Offline)

Ignore
1714192118
Reply with quote  #2

1714192118
Report to moderator
"The nature of Bitcoin is such that once version 0.1 was released, the core design was set in stone for the rest of its lifetime." -- Satoshi
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
allten (OP)
Sr. Member
****
Offline Offline

Activity: 455
Merit: 250


You Don't Bitcoin 'till You Mint Coin


View Profile WWW
March 14, 2013, 02:46:16 AM
 #22

Can you explain how it works?  How do you use it?

Advantages over a mass market encrypted USB stick?


Allten, could you answer these questions?  

Sure. Sorry for the slow response.

Currently, there is no client support so it doesn't work, yet. Someone42 was the first pioneer in open
source Hardware wallet and helped with a lot with the bitsafe.
Here is one of his first posts:
https://bitcointalk.org/index.php?topic=78614.0

Hopefully, you can get an idea of how it will work and how to use it from that thread.

What's an encrypted USB stick? Is it just a wallet file that is encrypted?

Something like this:
http://www.newegg.com/Product/Product.aspx?Item=9SIA0SF0CK3099

It has a keypad and is hardware encrypted and needs no drivers.  It does on the other hand not offer anything bitcoin specific. 

Ok, I see. With Bitsafe and also Trezor, the idea is that the private keys are never exposed to the PC. The PC doesn't even have
the authority to tell the hardware wallet to create a signature. The idea is the PC software will generate the data or transaction to be signed and then
pass it to the hardware wallet where it can be double checked on the little screen to verify nothing nefarious is going on. If all checks out
then a signature is sent to the PC only with the press of a button on the hardware wallet. This makes it impossible for viruses, malware, etc.
to get your bitcoins. It's like having a dedicated computer that you know for sure is clean just for your bitcoins, but it is even more secure than that
because the firmware is compiled directly for the hardware and doesn't need a OS of any kind. Someone42 could explain it better.
I've had my mind mostly in the hardware development side and am not fully up to speed on exactly how it will work.
allten (OP)
Sr. Member
****
Offline Offline

Activity: 455
Merit: 250


You Don't Bitcoin 'till You Mint Coin


View Profile WWW
March 14, 2013, 02:52:36 AM
 #23

This is a fantastic project for the bitcoin community and BFL would love to contribute to it.  Perhaps we can leverage our volume production capability to make these cheap enough to help spread bitcoin to the fringe interest crowd.  In the meantime, if we can help with the development by providing resources, please let us know.



Man. That is awesome! Your support is greatly appreciated. Having access to mass production capabilities will make this so much more affordable.

Thanks.

If we run out of prototypes then I may solicit for your help in the near future.
After finishing the prototypes, I don't ever want to see a soldering Iron again :-)

As for the mass producible versions, its months away, but I'll keep you posted.
ChipGeek
Full Member
***
Offline Offline

Activity: 198
Merit: 100


View Profile
March 14, 2013, 03:23:15 AM
 #24

This looks like a great product.  I have only 1 question:

What happens to my keys & bitcoins if I loose the device or it stops working because my dog chewed on it?

Tip jar: 1ChipGeeK7PDxaAWG4VgsTi31SfJ6peKHw
someone42
Member
**
Offline Offline

Activity: 78
Merit: 10

Chris Chua


View Profile
March 14, 2013, 04:16:11 AM
 #25

is the firmware / source code posted somewhere like github or is it not developed yet??

I have been developing the firmware. You can get it from: https://github.com/someone42/hardware-bitcoin-wallet. It's in a state of flux, as the surrounding Bitcoin infrastructure changes. At the moment I'm working on implementing an interface based on protocol buffers, so that I can make it "Trezor compatible" (eg. see https://bitcointalk.org/index.php?topic=125383.0).

Can you explain how it works?  How do you use it?

Advantages over a mass market encrypted USB stick?

Here is an entirely fictitious depiction of what is possible:
  • You open multibit and plug the BitSafe into your computer. One of your greyed-out wallets becomes highlighted.
  • You navigate to bitmit.com, and purchase something for 1.815 BTC. Multibit handles the Bitcoin URI and gives you a payment prompt.
  • After approving multibit's payment prompt, a light flashes on the BitSafe and "Send 1.815 BTC to www.bitmit.net?" appears on the OLED display.
  • You press the "approve" button on the BitSafe and the relevant Bitcoin transaction propagates to the rest of the Bitcoin network.

During this story, there is no opportunity for malware to intercept your private keys. Private key storage and transaction signing is done entirely on the BitSafe. Malware does not even have the opportunity to redirect funds to another address; using a proposed payment protocol (see https://gist.github.com/gavinandresen/4120476), addresses and amounts are signed by the merchant (in this case www.bitmit.net), authenticated by the BitSafe and displayed on its OLED display.

It gets better than this. You could encrypt your wallet so that if you accidentally lose the BitSafe, any finders will have a harder time accessing your wallet. "Deluxe" versions of the BitSafe might include a USB port which will allow you plug in a USB keyboard. You could then enter passphrases without fear of (software) keyloggers. Maybe you could even use this keyboard to enter a brainwallet passphrase; the Deluxe BitSafe generates, uses, and erases the brainwallet independently of the host computer.

This looks like a great product.  I have only 1 question:

What happens to my keys & bitcoins if I loose the device or it stops working because my dog chewed on it?
Currently, the firmware implements a deterministic wallet based on the proposed BIP 0032 standard. So you would be able to do a wallet backup by writing a series of letters/numbers on a piece of paper. You would presumably place this paper in a physically secure location (eg. safe). If you lose the BitSafe or it breaks, you can entirely restore the wallet from this piece of paper.
Peter Todd
Legendary
*
Offline Offline

Activity: 1120
Merit: 1149


View Profile
March 14, 2013, 05:35:55 AM
 #26

Just bought one! It's great to see this happen for real.

Littleshop
Legendary
*
Offline Offline

Activity: 1386
Merit: 1003



View Profile WWW
March 14, 2013, 05:43:04 AM
 #27


Can you explain how it works?  How do you use it?

Advantages over a mass market encrypted USB stick?

Here is an entirely fictitious depiction of what is possible:
  • You open multibit and plug the BitSafe into your computer. One of your greyed-out wallets becomes highlighted.
  • You navigate to bitmit.com, and purchase something for 1.815 BTC. Multibit handles the Bitcoin URI and gives you a payment prompt.
  • After approving multibit's payment prompt, a light flashes on the BitSafe and "Send 1.815 BTC to www.bitmit.net?" appears on the OLED display.
  • You press the "approve" button on the BitSafe and the relevant Bitcoin transaction propagates to the rest of the Bitcoin network.

During this story, there is no opportunity for malware to intercept your private keys. Private key storage and transaction signing is done entirely on the BitSafe. Malware does not even have the opportunity to redirect funds to another address; using a proposed payment protocol (see https://gist.github.com/gavinandresen/4120476), addresses and amounts are signed by the merchant (in this case www.bitmit.net), authenticated by the BitSafe and displayed on its OLED display.


Thanks!  This is what I wanted to know, and this sounds very good. 

PartTimeLegend
Member
**
Offline Offline

Activity: 63
Merit: 10


View Profile
March 14, 2013, 11:18:05 AM
 #28

I'm currently building an open source POS for Bitcoin merchants.

Do you have any documentation on the API?

If possible I would like to integrate with my POS so that a customer comes in to pay via BTC, I raise the transaction at POS and present a USB port to the customer to plugin and approve the transaction.
SgtSpike
Legendary
*
Offline Offline

Activity: 1400
Merit: 1005



View Profile
March 14, 2013, 03:40:38 PM
 #29

This looks awesome!

One question:
Is it possible to make a paper backup of your wallet AND encrypt it?  Do you just make the paper backup while the wallet is not encrypted, or can you make the paper backup of the encrypted wallet and decrypt it once it has been digitized again?
Forlarren
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
March 14, 2013, 05:42:15 PM
 #30

Any way these things could get one of those new low power Bluetooth radios instead of USB, or would that break security?
SgtSpike
Legendary
*
Offline Offline

Activity: 1400
Merit: 1005



View Profile
March 14, 2013, 05:56:53 PM
 #31

Any way these things could get one of those new low power Bluetooth radios instead of USB, or would that break security?
1) You'd need battery power.
2) You'd need to integrate a resettable pin.
3) People scanning for bluetooth devices would know that a hardware wallet was nearby if yours was turned on.  Might be best to keep that information private.

That said, it's rarely a bad idea to have more options instead of fewer, and this could potentially open the door for hardware wallet + mobile device, which would be neat.  I think the security is still there, as you would still have to physically push buttons to authorize transactions with the wallet.
Icoin
Hero Member
*****
Offline Offline

Activity: 585
Merit: 501



View Profile WWW
March 14, 2013, 09:01:22 PM
Last edit: March 14, 2013, 09:22:37 PM by Icoin
 #32

Quote
1) You'd need battery power
Why not use a GPL supercapacitor instad? And a battery just as option ?
https://bitcointalk.org/index.php?topic=101559.msg1582402#msg1582402
http://vimeo.com/51873011#

Wouldnt it become possibe to build that safe even smaller? I assume that the acutal design is cause of the lithium battery.

fellowtraveler
Sr. Member
****
Offline Offline

Activity: 440
Merit: 250


View Profile
March 14, 2013, 09:10:57 PM
 #33

Here is an entirely fictitious depiction of what is possible:
  • You open multibit and plug the BitSafe into your computer. One of your greyed-out wallets becomes highlighted.
  • You navigate to bitmit.com, and purchase something for 1.815 BTC. Multibit handles the Bitcoin URI and gives you a payment prompt.
  • After approving multibit's payment prompt, a light flashes on the BitSafe and "Send 1.815 BTC to www.bitmit.net?" appears on the OLED display.
  • You press the "approve" button on the BitSafe and the relevant Bitcoin transaction propagates to the rest of the Bitcoin network.

During this story, there is no opportunity for malware to intercept your private keys. Private key storage and transaction signing is done entirely on the BitSafe. Malware does not even have the opportunity to redirect funds to another address; using a proposed payment protocol (see https://gist.github.com/gavinandresen/4120476), addresses and amounts are signed by the merchant (in this case www.bitmit.net), authenticated by the BitSafe and displayed on its OLED display.

It gets better than this. You could encrypt your wallet so that if you accidentally lose the BitSafe, any finders will have a harder time accessing your wallet. "Deluxe" versions of the BitSafe might include a USB port which will allow you plug in a USB keyboard. You could then enter passphrases without fear of (software) keyloggers. Maybe you could even use this keyboard to enter a brainwallet passphrase; the Deluxe BitSafe generates, uses, and erases the brainwallet independently of the host computer.

Quote from: ChipGeek
What happens to my keys & bitcoins if I loose the device or it stops working because my dog chewed on it?

Currently, the firmware implements a deterministic wallet based on the proposed BIP 0032 standard. So you would be able to do a wallet backup by writing a series of letters/numbers on a piece of paper. You would presumably place this paper in a physically secure location (eg. safe). If you lose the BitSafe or it breaks, you can entirely restore the wallet from this piece of paper.


Kudos for someone42 for this post. This is exactly what I was coming onto this thread to write.

Especially the part where he says, "[then] a light flashes on the BitSafe and "Send 1.815 BTC to www.bitmit.net?" appears on the OLED display."

This is exactly what I need for Open-Transactions.

We have now gotten OT to where it installs on 64bit Linux through apt-get (using custom repo).

What do I need to make happen, in order to test OT on your device? Is there any comparable hardware I can buy now at home, which I can use to simulate running OT on your device? (So I can prepare OT to run on your device...)

This project is very interesting and important, especially the open-source aspect of it. May I recommend also that you choose an open-source license with patent protections built in so that your work doesn't later become subject to patent trolling. That will impact companies who try to use your hardware designs.

I am available fellowtraveler@rayservers.net for any discussion. Great work!


co-founder, Monetas
creator, Open-Transactions
theymos
Administrator
Legendary
*
Offline Offline

Activity: 5180
Merit: 12900


View Profile
March 14, 2013, 09:18:43 PM
 #34

This is a wonderful idea. I've wanted something like this for a long time.

Does the device store transaction data, or does it just look at transactions given to it by the PC to determine how many bitcoins the transaction is sending?

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
jayez
Newbie
*
Offline Offline

Activity: 25
Merit: 0


View Profile
March 14, 2013, 11:49:31 PM
 #35

SOON.

https://i.imgur.com/XYktA8R.jpg
cbeast
Donator
Legendary
*
Offline Offline

Activity: 1736
Merit: 1006

Let's talk governance, lipstick, and pigs.


View Profile
March 15, 2013, 02:21:11 AM
 #36

I was going to have one encrusted in gold and gems with a USB cable disguised as a gold rope chain, but I didn't have the money. ;-)

Any significantly advanced cryptocurrency is indistinguishable from Ponzi Tulips.
someone42
Member
**
Offline Offline

Activity: 78
Merit: 10

Chris Chua


View Profile
March 15, 2013, 03:56:55 AM
 #37

I'm currently building an open source POS for Bitcoin merchants.

Do you have any documentation on the API?

If possible I would like to integrate with my POS so that a customer comes in to pay via BTC, I raise the transaction at POS and present a USB port to the customer to plugin and approve the transaction.
This is a wonderful idea. I've wanted something like this for a long time.

Does the device store transaction data, or does it just look at transactions given to it by the PC to determine how many bitcoins the transaction is sending?
The device doesn't store blocks, block headers, or any transaction data. This makes it somewhat difficult to use in a POS situation. It's still possible: there is a "get master public key" command which allows the POS terminal to derive every address in a wallet. From there, the POS terminal can scan the blockchain and build a transaction. This is a lot of legwork for the POS terminal. Another disadvantage is that the user sacrifices privacy, since the POS terminal knows every address in the wallet.

A description of the wire protocol can be found at https://github.com/someone42/hardware-bitcoin-wallet/blob/master/PROTOCOL. I'm trying to make it like the one described here: https://bitcointalk.org/index.php?topic=125383.0.

This looks awesome!

One question:
Is it possible to make a paper backup of your wallet AND encrypt it?  Do you just make the paper backup while the wallet is not encrypted, or can you make the paper backup of the encrypted wallet and decrypt it once it has been digitized again?
You would need to have the correct encryption key in order to initiate a backup, but once you do, the paper backup can be encrypted or unencrypted. Encrypted paper backups can buy you time if the paper is compromised, whereas unencrypted paper backups protect you against you forgetting the wallet passphrase Smiley.
allten (OP)
Sr. Member
****
Offline Offline

Activity: 455
Merit: 250


You Don't Bitcoin 'till You Mint Coin


View Profile WWW
March 15, 2013, 04:29:02 AM
 #38

Grin no I just knocked that up when I saw this thread today first time I heard about this, look forward to getting my hands on one  Grin

What amazes me about your add is that you took the time to get the LED colors correct. To my knowledge, no photos have been posted with the LEDs on.

For reference:
https://bitcointalk.org/index.php?topic=152517.msg1621501#msg1621501
allten (OP)
Sr. Member
****
Offline Offline

Activity: 455
Merit: 250


You Don't Bitcoin 'till You Mint Coin


View Profile WWW
March 15, 2013, 06:18:37 AM
 #39


This project is very interesting and important, especially the open-source aspect of it. May I recommend also that you choose an open-source license with patent protections built in so that your work doesn't later become subject to patent trolling. That will impact companies who try to use your hardware designs.

I am available fellowtraveler@rayservers.net for any discussion. Great work!

Thanks for the interest and enthusiasm.
I really don't know squat about licensing.
The way I view open source projects or community projects: when you see something lacking or something that needs to be done then that is your call to make it happen.
Are you up to it? That is, take care of all the licensing?

Between Family and work, like many here, I can only do so much. Hopefully, I can help foster an atmosphere where people feel welcome to jump right in and be part of this
in anyway they feel useful. No permission needed. I hope I'm not perceived as the owner of this initiative;
I'm just the guy who was passionate enough to dump a couple thousand (wife wasn't too happy) to make some prototypes after I saw the proof of concept and all the work
Someone42 had done.

Today, I received two messages from two different people that are taking the initiative to build a case for this first version. With a 3D printer, I believe.
That was great news!

This has encouraged me to start and manage some bounties. I would like to start with these two: one for case or enclosure and another for the licensing to be taken care of.

Open Source Licensing Bounty: 1DVXwuBuR4qLyW7axAq8tuTxPnTiGyvk5P
Case/enclosure Bounty: 1Jj3RkgLydBef2jpUrAUDxDYf1A5wvLsU
Icoin
Hero Member
*****
Offline Offline

Activity: 585
Merit: 501



View Profile WWW
March 15, 2013, 08:15:31 AM
Last edit: March 15, 2013, 08:30:07 AM by Icoin
 #40

Hardware Design Public License Version 0.04

? Graham Seaman 2000 (graham@opencollector.org)
Preamble

[meta]This license contains three parts: the license proper; comments, explaining the intent of the license proper, and separated from it by [comment]...[/comment], and meta-comments, which will be removed from the license once it has been completed. Meta-comments are separated by [meta]...[/meta]. All comments are in italics. [/meta]
[comment]This license is intended to achieve similar goals to those of the GPL (http://www.gnu.org/copyleft/gpl.html) in the context of hardware designs. It is not intended to achieve all the different goals those working on free hardware designs may have, some of which may require radically different licenses. However, it is intended to cover hardware designs of all types, including designs for PCBs, ICs, and Programmable Logic Devices. [/comment]

[meta] Trying to keep it this general has made the current version sound horribly long-winded. It is more of an exercise in finding out what the problems are in developing this kind of license, and what the goals should be, than a practical license, since there is no organization behind it. [/meta]

Any version of this license with version number greater than or equal to 1.0 may be copied and used verbatim. For versions before 1.0, the license may not be used; however, it may be copied, and meta-comments may be changed or added at will.

[meta]This license is incomplete, and has never been looked at by a lawyer. Maybe one day there will be a final valid version 1.0. In the mean time, you're welcome to use any useful ideas in it (as I have also borrowed ideas), just not to use the whole thing under this name. The main sources of the ideas (and parts of the text) in the license are:

Ian Carr de Avelon
Reinoud Lambert
And above all, the FSF
[/meta]
DEFINITIONS

"Manufacturing files" include any files which can be used as direct input to a process the purpose of which is to permanently change the electrical or electronic properties of an object. This includes, but is not limited to, gerber or other files for PCB manufacture; mask works for IC manufacture.
"Programming files" include any files which can be used as direct input to a process the purpose of which is to temporarily change the electrical or electronic properties of an object. This includes, but is not limited to, programmable logic device configuration data for FPGAs or PLDs; executable files for processors.
The "hardware design" (or simply "the Design") is the set of files associated with this license by being placed in the same directory as the license, or subdirectories of the directory containing the license, including but not limited to manufacturing files and programming files. Where these files have a textual format, they should contain a reference to this license (or in the case of software or documentation any license recognised by the Free Software Foundation as compatible with licenses issued by the Free Software Foundation).
[meta]This is the key to the whole license; it avoids the almost impossible to task of finding a completely general definition of a hardware design. Note that the legality of covering binary files with a copyright license is not settled, but that this has become current practice (eg. Xilinx uses this for FPGA bitstreams)[/meta]
A "readable" file must be in a format which can be read by software available to the general public, whether free or for a fee, with the exception that it must not be encrypted, obfuscated, or have its readability in any way artifically obstructed.
"Hardware Design Public License" (abbreviated to "HDPL") refers to this or later versions of this license.
Terms And Conditions

The HDPL covers all files included in the hardware design, except the license itself. You may not impose any further restrictions on use or distribution of the hardware design than those contained in the HDPL.
You may copy and distribute verbatim copies of the hardware design in any medium. You may charge a fee for the physical act of transferring a copy via a non-networked medium (such as a CDROM), and you may offer warranty protection, instructional support, or other services in exchange for a fee. You may not charge a fee for the sole purpose of providing access to the hardware design via a network.
[comment]"Verbatim" implies the inclusion of ALL files making up the hardware design, including the license file itself.[/comment]
You may freely modify this hardware design (with the exception of the HDPL file itself), thus forming a work based on the hardware design, and copy and distribute such modifications under the terms of section 2 above, provided that you also meet all these conditions:
You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
You must in no way alter any copyright or mask work right symbols and information contained in the design
You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the hardware design or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this license
You must ensure that all files in the modified design are readable in the sense defined above.
[comment]Clause 3.3 implies that you may not include in your modification any work covered by patent or other rights which would invalidate this license[/comment]
[meta]Clause 3.4 is not in the spirit of the gpl. It would be desirable, but not practical to insist that only free software formats can be used. As it is, this clause leaves it open to a company to use a proprietary and secret format only usable by in-house software, and then to offer that software for sale at a ridiculous price, in order to satisfy the letter of this clause. This clause may change in future versions.[/meta]
The requirements of section 3 apply to the modified work as a whole. If identifiable sections of that work are not derived from the hardware design, and can reasonably be considered independent and separate works in themselves, then this license, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on this hardware design, the distribution of the whole must be on the terms of this license, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.
[comment]For example, say the design is a System-On-Chip computer. A person who adds a UART to this system may distribute the UART design separately under a different license. But if that person wishes to distribute the SOC computer design with the inclusion of the UART, the UART design must fall under the original license[/comment]
You may copy and distribute the manufacturing and programming files contained within the hardware design (or a work based on it, under sections 3,4) separately from the remainder of the hardware design, provided that you also do one of the following:
Accompany them with a prominently displayed URL for a network site available to the general public for a period of at least 3 years and with no access restrictions from which the complete hardware design (or the work based on it, as appropriate) may be downloaded in readable form.
Accompany them with the information you received as to the offer to distribute the corresponding complete hardware design (this alternative is allowed only if you received the manufacturing and programming files with such an offer, and have not subsequently modified these files).
[comment]This section has 4 principal purposes:

To apply similar conditions to those of the gpl to any software included in the hardware design
To apply similar conditions to those of the gpl to any programming information such as fpga bitstreams included in the design
To prevent users under section 6 from taking the design and modifying it by adding secret interfaces so that the manufactured design becomes effectively unusable.
To enforce the availability of documentation for any manufactured version of the design, via the following clause.
[/comment]
You may use manufacturing files contained in the hardware design for the purpose for which they were intended as defined above (definition 1).
For the purposes of this license, such use is to be considered as a form of distribution of the manufacturing files, and hence falls under section 5, with the same requirements.
[meta]The remainder of this license is copied almost word for word from the GPL. It is likely that extra clauses will have to be added to deal with potential patent violations and lack of implied warranty[/meta]

You may not copy, modify, sublicense, or distribute the Design except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Design is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the design or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the hardware design (or any work based on the Design), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the design or works based on it.
Each time you redistribute the Design (or any work based on the Design), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Design subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the design at all. For example, if a patent license would not permit royalty-free redistribution of the design by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Design.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free hardware design distribution system, which is implemented by public license practices. Many people have made generous contributions to the growing range of hardware designs distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute a design through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

If the distribution and/or use of the Design is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Design under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
Each version of the HDPL is given a distinguishing version number. If the Design specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version.
If you wish to incorporate parts of the Design into other free designs whose distribution conditions are different, you may write to the author to ask for permission.hello

Pages: « 1 [2] 3 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!