Cryptography: Explaining SHA-512. This is intended to give ...

"Mining" Coins in 2140+

One of the keys of Bitcoin is that loss of the private key means loss of access to Bitcoins. Many Bitcoins have already been lost due to destruction of the private key.
Stack Exchange hypothesizes that, given advances from Moore's law (which may or may not hold, it's never been tested on this kind of timeline), the first practical cracking of a Bitcoin private key will be in 60 years. At that point, it starts being economical to target known large stashes; and, for sufficiently large stashes, it becomes more profitable to change miners from trying to mine to trying to crack private keys. Likely the Bitcoin protocol would evolve in this time to use SHA512 or something else that's invented in the meantime, so coins transferred out of those accounts would be safe for another 60 years.
Doing this cracking seems, at first blush, like theft, but I think legally (but not as a lawyer nor as someone giving legal advice), this would likely fall under the category of treasure trove. If it's been 100 years since the last Bitcoin transaction from an address, it's probably safe to assume that whoever once had access to it has lost that access, and it's now up for the taking for whoever can take it.
submitted by sulphur_gargoyle to Bitcoin [link] [comments]

[Kali 17.1] JtR support for pkzip dropped?

Hi all, I'm just trying my hand on the okcupid challenge (view source of okcupid.com). It includes four encrypted zip files. I wanted to try the easy way first and use john, but it seems on Kali 17.1 JtR does not support the pkzip format anymore?
[email protected]:~# john --list=formats 
descrypt, bsdicrypt, md5crypt, bcrypt, scrypt, LM, AFS, tripcode, dummy, dynamic_n, bfegg, dmd5, dominosec, dominosec8, EPI, Fortigate, FormSpring, has-160, hdaa, ipb2, krb4, krb5, KeePass, MSCHAPv2, mschapv2-naive, mysql, nethalflm, netlm, netlmv2, netntlm, netntlm-naive, netntlmv2, md5ns, NT, osc, PHPS, po, skey, SybaseASE, xsha, xsha512, agilekeychain, aix-ssha1, aix-ssha256, aix-ssha512, asa-md5, Bitcoin, Blackberry-ES10, WoWSRP, Blockchain, chap, Clipperz, cloudkeychain, cq, CRC32, sha1crypt, sha256crypt, sha512crypt, Citrix_NS10, dahua, Django, django-scrypt, dmg, dragonfly3-32, dragonfly3-64, dragonfly4-32, dragonfly4-64, Drupal7, eCryptfs, EFS, eigrp, EncFS, EPiServer, fde, gost, gpg, HAVAL-128-4, HAVAL-256-3, HMAC-MD5, HMAC-SHA1, HMAC-SHA224, HMAC-SHA256, HMAC-SHA384, HMAC-SHA512, hMailServer, hsrp, IKE, keychain, keyring, keystore, known_hosts, krb5-18, krb5pa-sha1, kwallet, lp, lotus5, lotus85, LUKS, MD2, md4-gen, mdc2, MediaWiki, MongoDB, Mozilla, mscash, mscash2, krb5pa-md5, mssql, mssql05, mssql12, mysql-sha1, mysqlna, net-md5, net-sha1, nk, nsldap, o5logon, ODF, Office, oldoffice, OpenBSD-SoftRAID, openssl-enc, oracle, oracle11, Oracle12C, Panama, pbkdf2-hmac-md5, PBKDF2-HMAC-SHA1, PBKDF2-HMAC-SHA256, PBKDF2-HMAC-SHA512, PDF, PFX, phpass, pix-md5, plaintext, pomelo, postgres, PST, PuTTY, pwsafe, RACF, RAdmin, RAKP, rar, RAR5, Raw-SHA512, Raw-Blake2, Raw-Keccak, Raw-Keccak-256, Raw-MD4, Raw-MD5, Raw-SHA1, Raw-SHA1-Linkedin, Raw-SHA224, Raw-SHA256, Raw-SHA256-ng, Raw-SHA3, Raw-SHA384, Raw-SHA512-ng, Raw-SHA, Raw-MD5u, ripemd-128, ripemd-160, rsvp, Siemens-S7, Salted-SHA1, SSHA512, sapb, sapg, saph, 7z, sha1-gen, Raw-SHA1-ng, SIP, skein-256, skein-512, aix-smd5, Snefru-128, Snefru-256, LastPass, SSH, SSH-ng, Stribog-256, Stribog-512, STRIP, SunMD5, sxc, Sybase-PROP, tcp-md5, Tiger, tc_aes_xts, tc_ripemd160, tc_sha512, tc_whirlpool, VNC, vtp, wbb3, whirlpool, whirlpool0, whirlpool1, wpapsk, ZIP, NT-old, crypt
Am I missing something? Thanks!
submitted by mrquisda to AskNetsec [link] [comments]

Native Bitcoin Escrow is live, launch countdown!

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, After many hours spent coding and researching, we have finished our initial Bitcoin Multisig Wallet payment system and are glad to announce we have created the first true bitcoin escrow marketplace that allows vendors and customers to transact without fear of having coins stolen as no one party is able to use the bitcoins without 1 other party signing the transaction, all from a simple to use interface. We have built this feature as part of our larger plan to create a completly distributed platform which will take a long time so we felt that we must first ensure that users would be 100% safe if a malicous party takes control of our servers. All code is unit and functional tested to above 85% coverage and we have completed the following: * Full product catalog that allows sorting and filtering by domestic * Bitcoin Multisig payment system * Enforced encryption message system * Dispute resolution centor * Vendor & item reviews We hope to get feedback from users and we will be creating a new i2p forum and wiki in the coming days for community members to converse and learn more. We will also be putting guides for both vendors and customers alike on the wiki. You can acess the marketplace for now at it's B32 I2P address (Put in address bar and go): http://r35rdglu7cjmsxh5qn3v6o5q7cnejanwg4h2viuvaqavpbf5uqaq.b32.i2p If you are a vendor and would like to have your shop setup before launch, it is imperative you contact us at [email protected] Thanks, TMPSchultz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (Darwin) Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJSgdotAAoJEBLtEWOvmHDdiBAIAMZ+I7ZB96RHO2kAcmcXmb+I qsQA8rWgTH6TF0ISvdBY20baHgi41edJ+xRtac8p6xD4JT2ryR6dBqpZr+EU1Yub L3l4bTf6Z9rXFOg9xlud7PtL+jD6JsxWwJ+W8nwJ0vyur7gVlKmyn6EfOqQ9CSny Kqgm5vOPbeC85lrX/ayn7eLg+chfRdqrHn32tgDkekJeFaU+uwxYDROu3JAGGL2W 3506qnH9OcqsiNd517q+rD8mkLa79E3mDkuVZ+srsfhGTCnFTsALeYtUNu6iKZio NvdJzy0TefjsY126JMvSW/8jef1r4bdOKCYR8FDTZ+qOxBIQ9XbcsSEAIAIkrWo= =FJw3 -----END PGP SIGNATURE----- 
submitted by TMPSchultz to themarketplace [link] [comments]

bitcoin-dev Digest, Vol 5, Issue 2 | digitsu at gmail.com | Oct 01 2015

digitsu at gmail.com on Oct 01 2015:
Because Bitcoin XT is 1.0.0
;-)
---------- Forwarded message ----------
From: Marcel Jamin <marcel at jamin.net>
Date: 2015-10-01 11:39 GMT+02:00
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release schedule
To: Btc Drak <btcdrak at gmail.com>
I guess the question then becomes why bitcoin still is <1.0.0
I'd say it's safe to say that it's used in production.

Regards,
On Thu, Oct 1, 2015 at 6:57 PM, null
<bitcoin-dev-request at lists.linuxfoundation.org> wrote:
Send bitcoin-dev mailing list submissions to
bitcoin-dev at lists.linuxfoundation.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
or, via email, send a message with subject or body 'help' to
bitcoin-dev-request at lists.linuxfoundation.org
You can reach the person managing the list at
bitcoin-dev-owner at lists.linuxfoundation.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of bitcoin-dev digest..."
Today's Topics:
  1. Re: Design Competition (odinn)
  2. Re: Bitcoin Core 0.12.0 release schedule
    (Wladimir J. van der Laan)
  3. Re: Bitcoin Core 0.12.0 release schedule (Marcel Jamin)
  4. Re: Bitcoin Core 0.12.0 release schedule (Btc Drak)
  5. Fwd: Bitcoin Core 0.12.0 release schedule (Marcel Jamin)
  6. Re: Fwd: Bitcoin Core 0.12.0 release schedule
    (Wladimir J. van der Laan)
Message: 1
Date: Thu, 01 Oct 2015 04:38:50 +0000
From: odinn <odinn.cyberguerrilla at riseup.net>
To: Richard Olsen <richard.olsen at lykkex.com>, bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Design Competition
Message-ID: <560CB8DA.6060801 at riseup.net>
Content-Type: text/plain; charset=windows-1252
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Grosses me out that you have enforced KYC as part of what you are
doing for anyone who would decide to get involved:
https://wiki.lykkex.com/?id=start#lykke_citizens
Good luck with that, I'm sure not going to be a part of it, and I
recommend that no-one else does either.
  • - O
Richard Olsen via bitcoin-dev:
All,
We are looking for participants in a Bitcoin related competition:
the aim is to build a trading platform (initially for foreign
exchange, other assets will follow) which lets participants settle
their trades through the blockchain via coloured coins. To
facilitate a quicker trade reconciliation, the use of a sidechain
is a suggestion but by no means a requirement. There will be an
online briefing event today where we will outline the requirements
in more detail, though much of it we have posted on our website
www.lykkex.com .
As we want this to be a community driven effort rather than
something turning into a proprietary technology, all contributions
will be made available under a MIT license on Github.
I look forward to answering your questions at the online briefing
event or over email,
Thank you and kind regards, Richard Olsen
_______________________________________________ bitcoin-dev mailing
list bitcoin-dev at lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
http://abis.io ~
"a protocol concept to enable decentralization
and expansion of a giving economy, and a new social good"
https://keybase.io/odinn
-----BEGIN PGP SIGNATURE-----
iQEcBAEBCgAGBQJWDLjaAAoJEGxwq/inSG8CkQAH/i6603ivtZXjNw5ZlH1W2p7z
c88sb5CcTuTUi+zEx6Q0MRUFfdYcrcBrGsua3CKU9226rpL4acD2Bby5kUPZ1h2/
Rl5EiZa11oeqZaZaO5ZmXZ33BOaO2gxqqYEF1zBOzDgky6cqRrj8t4VAj5CKsxsP
ktM98UqVXdcuOfBP7y/xqX1Yw9e55PpwUCtaazLo8UkPLMrtdzrbKVZBtjqGxMnG
ZxmYku8g6xdmZAMz9xn9oVGtuMHrEjhIVycz3FMHBjoZNLE9yK4YeWyEvLI4YPFt
KBR7HvGDava3dzMM5ugw3hgFShfegjrIunWQ/vC9RCjBMLVGVX5RgEblgQe29eY=
=41DC
-----END PGP SIGNATURE-----
Message: 2
Date: Thu, 1 Oct 2015 10:50:59 +0200
From: "Wladimir J. van der Laan" <laanwj at gmail.com>
To: Luke Dashjr <luke at dashjr.org>
Cc: Bitcoin development mailing list
<bitcoin-dev at lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release schedule
Message-ID: <20151001085058.GA10010 at amethyst.visucore.com>
Content-Type: text/plain; charset=utf-8
On Wed, Sep 30, 2015 at 05:57:42PM +0000, Luke Dashjr wrote:
On Thursday, September 24, 2015 11:25:56 AM Wladimir J. van der Laan via
bitcoin-dev wrote:
2015-12-01
  • Feature freeze
Where is "Consensus freeze"? Shouldn't this be put off until after the HK
workshop in case a hardfork is decided on? Or have we de-coupled it from the
release process entirely anyway (since old versions need an update for it
too)?
In principle, "feature freeze" means that any large code changes will no longer go into 0.12, unless fixing critical bugs.
I'm not keen on postponing 0.12 for such reasons - after the HK workshop I'm sure that it will take some development/testing/review before code makes it into anything. Apart from that there's a good point to decouple consensus changes from Bitcoin Core major releases.
We've seen lot of release date drift due to "this and this change needs to make it in" in the past, that was a major reason to switch to a time-based instead of feature-based release schedule.
We can always do a 0.12.1.
Wladimir
Message: 3
Date: Thu, 1 Oct 2015 11:05:59 +0200
From: Marcel Jamin <marcel at jamin.net>
To: "Wladimir J. van der Laan" <laanwj at gmail.com>
Cc: Bitcoin development mailing list
<bitcoin-dev at lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin Core 0.12.0 release schedule
Message-ID:

Content-Type: text/plain; charset="utf-8"
Any particular reason bitcoin versioning doesn't follow the SemVer spec?
2015-10-01 10:50 GMT+02:00 Wladimir J. van der Laan via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org>:
On Wed, Sep 30, 2015 at 05:57:42PM +0000, Luke Dashjr wrote:
On Thursday, September 24, 2015 11:25:56 AM Wladimir J. van der Laan via
bitcoin-dev wrote:
2015-12-01
  • Feature freeze
Where is "Consensus freeze"? Shouldn't this be put off until after the HK
workshop in case a hardfork is decided on? Or have we de-coupled it from
the
release process entirely anyway (since old versions need an update for it
too)?
In principle, "feature freeze" means that any large code changes will no
longer go into 0.12, unless fixing critical bugs.
I'm not keen on postponing 0.12 for such reasons - after the HK workshop
I'm sure that it will take some development/testing/review before code
makes it into anything. Apart from that there's a good point to decouple
consensus changes from Bitcoin Core major releases.
We've seen lot of release date drift due to "this and this change needs to
make it in" in the past, that was a major reason to switch to a time-based
instead of feature-based release schedule.
We can always do a 0.12.1.
Wladimir
bitcoin-dev mailing list
bitcoin-dev at lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <[http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151001/5dca9e61/attachment-0001.html](http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151001/5dca9e...[message truncated here by reddit bot]...
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-Octobe011326.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

Payment update - 3 way escrow to keep Bitcoins safe

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 A signed version of this message is here http://pastebin.com/p5MBmT2L -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (Darwin) Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJSdhe1AAoJEBLtEWOvmHDd0V4IAMZ2AOT2S3LA3txwGN+Arv9x A/HZ2lmcggyxDb7uGPQ7weBrQM0BlUdFQ0xhdLCrihEoehhwJrrj9pc4hwnw3hnf j5nBLLpwpLcvR7WNKwphy0cSsrhjrIyK3R9XYhIwGNRT5SqNd6CJPRbfaRIEtjk9 CRWE3hzkeN9sTJY9Een8w7hD4g42ORxWHp+u99UKb5tI+vODXN7k9y2E++oHmDZF 2TwCcXc9LayRRB2E0oOgvrl7wAw9RooDLd9z7ge9Q/3R6aYMj3YaroVUWaxc6cI1 Z9SDNCryByV3ajkAE1KrVxwFTF2/ZC04HWs/5+/N2nqo2xBKu4y492EQJI5bg/w= =C46E -----END PGP SIGNATURE----- 
Hi,
We would like to update everyone with some our plan for going live. We have been speaking together latley about payment processing and have decided that we will be delaying our launch to work on native Bitcoin Multi Signature payments.
We believe that the only way to be able to feel secure using a market place is with forced multi layer encryption, forced encrypted communication and the knowledge that it is not possible to have your bitcoins stolen from you. To understand how this will work, we first must give a basic explanation of how bitcoin works.
Every address does not actually hold real funds, rather your private key proves that you own "outputs" on the chain. Each of these outputs is a previous transaction and your wallet GUI shows you the sum of your unspent outputs.
For example, when you send a transaction, your wallet does the following:
* Get's all unspent outputs belonging to you * If the amount you are sending is more than the biggest output available, it continues adding these outputs as inputs till it has enough to cover the total you are sending, otherwise it will get the smallest output that covers the amount you are sending and use that as an input. * It creates an output of the amount you are sending and the wallet you are sending too. * If the total amount of all the inputs is more than you are sending, it creates another output called a "change wallet" which belongs to you and recieves whatever is left over (E.G, total output size is 30, you send 20, change is 10). * It signs this transaction with the private keys of the outputs that is is claiming and broadcasts it amongst its peers. 
Bitcoin supports multi signature addresses which is a unique bitcoin address actually created by using 3 public keys of bitcoin addresses and any funds sent must use private keys - in this case, 2 - of the original 3 public keys to sign the transaction, thus preventing any 1 party from claiming these inputs on their own.
Our idea is that when a customer places an order, they will input their enforced pgp encrypted shipping address and a bitcoin signing address and will then be given a new 3 way multi sig address generated from a mediator (Us), vendor and their own address. Any funds sent to this address will require 2 of the 3 parties to sign before they are able to be spent.
* For refunds, we will create a transaction with 2 outputs vendor and customer, splitting the original amount between both outputs and allow the vendor or customer to sign and broadcast. * Before an order is accepted and shipped by a vendor you are able to cancel the order and we will provide a signed transaction allowing you to void the contract. * If the vendor is offline for 7 days, all disputes created will include a signed transaction enabling a customer to cancel the contract. * If the order is finalized, we will provide a signed transaction sending 1% of the amount to an emengency wallet and the rest to the vendor. The customer and vendor could send eachother encrypted messages to get around this fee but we hope that they won't do that. This 1% will be sent to a wallet that will be controlled by the community and be for emergency situations. 
This means that in the case of an emergency, alternative temporary forums could be put up by community members to facilitate the disbursment of in-escrow payments and prevent the loss of any bitcoins at all. We can't steal your bitcoins, the vendor can't steal your bitcoins and no malicous party can steal your bitcoins. Users would be paid a small bounty for finalizing their payments. This would be funded by the 1% fee and managed by trusted community members.
This also means that we do not need to be tumbling coins and it will also be extremly difficult to analyze payments between vendor and customer. Each payment will look like any other multi signature payment on the network (Though there are not many multi signature payments currently as it is a new feature) and have no affiliation with any previous Marketplace transaction. We hope that P2SH becomes more standard as that would allow us to create more complex rules that would create an even more decentralized platform.
We feel the typical flow for a user would be: * Use a Bitcoin Broker to buy bitcoins via cash deposits and send funds to blockchain.info wallet * Send funds to trusted external bitcoin tumbler (e.g, bitcoingfog) to wash for a day or two * Purchase items and input a bitcoin address public key and send funds from tumbler to wallet given * Recieve items, click finalize, review.
The worst case flow would stop at clicking finalize and would continue more like: * Community forums setup, vendor creates thread to get money for shipped items * Users will sign the transactions for the vendor and recieve a payout from the emergency wallet managed by vendors (also escrow protected) * If a user did not recieve, they would be eligible to request a refund from the vendor but they would not recieve any bounty and the vendor can refuse or the user could withold the funds preventing them ever being by anyone.
We will not be charging vendors a set fee per order but we hope that vendors pay our requested fee % of their own accord, this may change in the future if it proves unviable.
We hope that this gets people excited about what is to come and allows our customers and vendors to feel a lot more safe. We hope to roll this out in the next few weeks and we will be connecting our payment servers to the Bitcoin Testnet to allow people to send real test bitcoins on the Testnet - https://en.bitcoin.it/wiki/Testnet.
Regards, TMPSchultz
submitted by TMPSchultz to themarketplace [link] [comments]

Top 5 Most POWERFUL Speeches You Need To Hear Today ... Boursorama - YouTube Mobilegeeks.de - YouTube OKLMofficial - YouTube

SHA-512 ist eine Funktion des kryptographischen Algorithmus SHA-2, der eine Weiterentwicklung des berühmten SHA-1 ist.. SHA-512 ist Sha-256 sehr ähnlich, außer dass es 1024 Bits "Blöcke" verwendet und als Eingabe eine maximale Länge von 2^128 Bits akzeptiert. SHA-512 hat auch andere algorithmische Modifikationen im Vergleich zu Sha-256. SHA-512 Algorithmus Übersicht [] SHA-256 wird in verschiedenen Teilen des Bitcoin-Netzwerks verwendet: Beim Mining wird SHA-256 als Proof-of-Work-Algorithmus verwendet. SHA-256 wird bei der Erstellung von Bitcoin-Adressen verwendet, um die Sicherheit und den Datenschutz zu verbessern. Siehe auch auf BitcoinWiki . Cloud Mining; Satoshi Nakamoto; Ressourcen This is intended to give you a basic understanding about what actually happens during the execution of a hashing algorithm. I’ve used the SHA-512 algorithm in order to help explain the inner ... Pseudocode []. Pseudocode for the SHA-256 algorithm follows. Note the great increase in mixing between bits of the w[16..63] words compared to SHA-1. h0 := 0x6a09e667 h1 := 0xbb67ae85 h2 := 0x3c6ef372 h3 := 0xa54ff53a h4 := 0x510e527f h5 := 0x9b05688c h6 := 0x1f83d9ab h7 := 0x5be0cd19 k[0..63] := 0x428a2f98, 0x71374491, 0xb5c0fbcf, 0xe9b5dba5, 0x3956c25b, 0x59f111f1, 0x923f82a4, 0xab1c5ed5 ... SHA-512 is a function of cryptographic algorithm SHA-2, which is an evolution of famous SHA-1.. SHA-512 is very close to Sha-256 except that it used 1024 bits "blocks", and accept as input a 2^128 bits maximum length string. SHA-512 also has others algorithmic modifications in comparison with Sha-256.

[index] [27175] [29368] [25640] [17396] [48402] [28056] [43583] [9456] [47571] [23458]

Top 5 Most POWERFUL Speeches You Need To Hear Today ...

Audible free book: http://www.audible.com/computerphile Hashing Algorithms are used to ensure file authenticity, but how secure are they and why do they keep... Les vidéos d'aquaportail http://www.aquaportail.com concerne le site portail d'aquariophilie et sont destinées à présenter des scènes de vie aquatique en aqu... Mobile technology news and reviews: tablets, netbooks, smartphones, ultrabooks, notebooks, eBooks, superphones and more. You name it, we cover all the curren... Enjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube. Small Faces with P.P. Arnold - Tin Soldier Live performance on French TV (Bouton Rouge program) March 2 1968 - dubbed over version.

#