UPDATES: Clients can exchange PEM/RSA keys

The official website is undergoing a facelift should be less then 24 hours till completed (I will post noticed when functional)
http://bitcoindevkit.com

Basically viruses, spyware, and trojans are a threat to computer users (PC, MAC OSX, etc). We all know this... but what we don't think about is how they can affect what once was encrypted communications on your computer.. Now you can't be too sure. You download so many files just browsing the internet even if you don’t ever click "Save" or "download" you had to download some files to get "there" to see those links. Files just basically freely come and go through your computer its unsure what viruses, spyware, etc are doing but what we DO know is that its unsafe to run encrypted communications AND work,browse, or what ever else it is you do this is because before your voice is encrypted, spyware can listen in to the microphone line "before" it is encrypted which effectively evades any encryption process. In effort to provide privacy I created an embedded encrypted device that uses multiple channels for Public key transfer to ensure no MITM attacks happen.

 When i was about to post my product on kick-starter I thought to my self "I have no screen, I have no interface on my embedded device, why would any-one invest in my device if they can't prove I know what im doing for all they know i just added sound in post-production of the demonstration video. So I thought.... and thought and thought. And my solution is to provide a P2P Encrypted solution for desktops just to demonstration that I have encryption knowledge and can build things up to PKCStandards.

So I present to you my desktop app (Known to only work with GCC/LINUX) right now; I'm in the process of building it, basically everyone logins with a Public Key, and clients to connect to other clients. Both clients identify them selves with public keys and exchange keys.

To prevent Man-In-The-Middle Attacks, clients will ask other clients around the world what they know about "everyone online" which is basically an IP address list with public key associated with them. Each client will save the list and extract the public keys they want to verify (as opposed to just specifically asking for a public key/IP pair which could lead to man-in-the-middle attacks as asking for specific public key and ip pairs). Essentially Bitcoin-Network but with out bitcoins its messaging.

Once a client feels they have enough verifications from each node they can start communicating with the client -- this is all transparent. (untrusted nodes will only slightly increase confidence, trusted nodes will drastically increase confidence).

Any ways once i feel that I have a user base I can release my embedded device on kick-starter when i feel it is time until then i will produce "confidence and trust" with the encryption communication community.

---

Programming Language: C
Source Code: https://github.com/Xenland/P2PCrypt-Server
Client Source Code: https://github.com/Xenland/P2PCrypt-Client
Website: (UNDER CONSTRUCTION) http://p2pcrypt.com

Looks like the error is fixed. The problem was that the check out page was redirecting you to the reciept.php page when the correct page is receipt.php
Let me know if you have any issues now.

Selling my "BDKp Donation Package" on BitcoinMall.net for 0.5 Bitcoins (If you want to donate more just send more Bitcoins to the receipt address and much will be appreciated!)
Here is the link to the donation page: http://cheaperinbitcoins.com/product.php?id=64
The check out page will ask for your email and I will send you a download link just for you thanks

Good to know!

Perhaps integrate bitcoins into the game?

Do what you can No rush, its the holidays mate!

Updates:

Added the following wiki page(completed): https://github.com/Xenland/Bitcoin-Development-Kit/wiki/BDK-Generate-Random-String

I forgot to mention that if your getting errors while trying to do the coin_authentication function; Keep in mind you have 20 minutes before the token to sign is invalid

More Updates:
The BDKp library will be featured in the upcoming "Mining Farm" updates(targeted for release in January)

How to use the BDKp for login authentication with out making contact to a database(A Free Tutorial - Usually a Donors Privilege)

Foreword:
Obviously the point of an authentication system is to "save" some data attached to that "account" that the user owns so although you'd probubly want a database to save user interaction information for your web site (or service) you can authenticate the visitor with their Bitcoin address (With out making contact with the database initially) and this is makes logins more powerful because for
one you need the Private Key to the Bitcoin address to even attempt to login which requires an attacker to gain access of your visitors computer/cellphone(Which are usually turned on/off constantly).
two there is no passwords stored on servers so this way if there is a database compromised users can feel safe to know that they don't have to change "ALL" their passwords for other websites that use the same pass that was compromised.
three this could add security to database compromise for sensitive information and provide control to the users, authenticated users can have their sensitive data encrypted to only open up with their private key this could force some business models to require user authorization before any data can be processed(This makes users feel safe online). Also if a business wanted the security of the encryption from database compromise but wanted to process data while the user is offline they can send their user data to a processing server that is separate from their website servers which would promote security for everyone. \

Okay so here is the example codes

---

Step 1
First off you need to ask the user what their Bitcoin address is. Once you have received that information you can then continue to "Step 1" of authenticating a user.
The first step requires you to enter the Bitcoin address into the function and it will spit out a string for the user to "Sign" with the in-putted Bitcoin address


Step 2
The user should be given a single line input text box to input the signature. once the user has pasted in their signature and presses submit, the form submission should tell the next page what the original data was (The BDK library will check the checksum if the data has been broken/altered)

So in the submission page it should look like this (With form variable-values already in-putted)

NOTES: The user has 20 minutes to sign the request and submit to server before it is invalid

My library for PHP could help you get started ASAP, contact me for integration details: http://bitcoindevkit.com

Actually for now I would like to stay with AGPL and if anyone needs different licensing please contact me, I would just like to do some surveys for those that plan on taking the library to the underground for their own uses and so the AGPL facilitates that process for me. In the future when I have enough survey data I plan to make it LGPL or even perhaps BSD/MIT but I need survey information and would like some compensation for my time so please be patient.

I have been freshing up on my FOSS licenses and I think I might release this library under LGPL instead of AGPL. Any thoughts? Conclusions? mishaps? Sounds like a great plan to me to benefit business and non-profit motivations.

Gewd to know!

How is that note attached to your address?

I'm sorry I don't know spanish but perhaps this could help?
http://bitcoindevkit.com

Source Code: https://github.com/Xenland/Bitcoin-Development-Kit

Note sure if this helps either but its worth a try: http://www.microsofttranslator.com/bv.aspx?from=&to=es&a=http%3A%2F%2Fxenland.github.com%2FBitcoin-Development-Kit%2F

Updates:
Added the function (considered completed and fully tested) called bdk_login_with_coin_address()
Its a function that does two steps into one, The first step is to output a randomize string (with some checksum/integrity and server signature data emedded into it aswell)
The user signs the string with their own Bitcoin address with the Bitcoin.org client. once signed they submit the signature and the original token data they had to sign (The token data could be embedded in a file string query if you prefer not to use a database). If the signature is valid to the Bitcoin address and the data is intact and the signature is still valid upon return then the user is authenticated. This function is just a mechanism for doing all the "authenticating" work for you, it dose not however add the "session" elements to your website that is for you to decide wheather its cookies, PHP sessions, database etc its up to you, this library will just make sure you properly authenticated the Bitcoin user correctly.

Wiki page for this function is going up soon!