I wanted to try out your faucet... Just to see how it works. Couldn't claim for a bech32 address: tb1qfxfnzhqymu5vt0fv7ykkevct4g3nmyezqj47vs You entered an invalid Testnet Bitcoin address!
|
|
|
|
Big Thank All of You !!! You get me axact information what I search.
So now it's your turn, what is your ultimate goal with this/these public keys? I'm sure it's not just so you can fire up some software... Doesn't really matter, does it... I couldn't care less if the OP found a piece of software that promised him he could reverse engineer a private key starting from a public key. Some people just need to learn the hard way, if he tries to reverse engineer a private key all he'll do is infect his pc with malware and/or waste a lot of his time... Doesn't have any impact on me either way  If he's just trying to learn, kudos to him... I can only encourage people that want to broaden their knowledge. |
|
|
|
I think this is not an advantage but a disadvantage of the technology that the project is building. Transactions must be irreversible or there is room for manipulation. And no one will approve of that.
It should be clear to discuss about crypto or bitcoin only.
With crypto, yes there are possible reversible transactions especially if the cryptocurrency you are talking about is a centralized cryptocurrency. Like ETH, Ripple, or any other same crypto projects.
With bitcoin, it is irreversible in theory and in reality it is almost irreversible. Reversibility can only be gotten if one pool has more than 51% of the total hashrates on the network, that is difficult. And the pool need to maintain such huge hashrate long enough. On bitcoin network, with long confirmed transactions, more than 30 confirmations, it is safe enough to say they are irreversible.
Reversible transaction will lower trust level in the network
Doesn't sound like good news for me. There is a reason why cryptocurrency transactions are irreversible. The feature was added, because scammers were making use of the reversibility with payment mediums such as Paypal. Now if we make cryptocurrency transactions similar to those with PayPal, then what will be the difference between the two payment mediums?
You guys really don't read any other post in a discussion do you.... Really... I've made an effort and actually surfed to the service and read some press releases, and i concluded that this service is NOT about making transactions reversible but it's merely a service that used a clever workaround to make an irreversible transaction LOOK reversible for a very small window in time. I've already posted my findings twice, but nobody seems to be interested in a discussion, everybody just keeps blurting out the first things that comes to their mind, without reading any other post, without putting in a very small amount of effort. All in all, this service is just a workaround, i wouldn't use it very often myself, but i do see a potential usecase... |
|
|
|
Privkey for bc1 and the pubkey will be the same or different  ? Different... The private key will always be different from the pubkey... otherwise it wouldn't be called private key vs public key |
|
|
|
Bro, as I right understand this is pubkey: "txinwitness": [ "30440220476ef5c395dd30dacac4c5476cc7c6d258de9c8e7581c26304f27dded4e810f50220100 163a5f440f01442ec1eaafece26e43a54d11ab1d686fd3bae22ae3c1e66db01", "036346635ba513c63eb3b2afbc4e9d34ae5b5de9208e703ad0d3173c25c97626b4" ], "sequence": 4294967295 But - this is 2 legit pubkey for 2 btc adresses ? What pubkey is need to use ? 30440220476ef5c395dd30dacac4c5476cc7c6d258de9c8e7581c26304f27dded4e810f50220100 163a5f440f01442ec1eaafece26e43a54d11ab1d686fd3bae22ae3c1e66db01 = signature 036346635ba513c63eb3b2afbc4e9d34ae5b5de9208e703ad0d3173c25c97626b4 = public key Or are you talking about the fact that you see 3 unique signatures and 2 unique public keys? That's because this transaction uses 1 unspent output funding the address you're investigating, and 2 unspent outpust from a different address (most likely both addresses belong to the same wallet). |
|
|
|
--snip-- Bro, and how to fined exact pubkey ? I was found pubkey in this raw transaction, but I was know pubkey and use search/ How many bytes I need sheft fo start of raw transaction, or enother method get pubkey from raw transaction. Explain this more datailed please If you have bitcoin core installed locally (or on a server you can access), you can just do bitcoin-cli decoderawtransaction [rawtx] You'll see the unspent outputs being used as an input to your transaction (vin), and you'll see the pubkey straight away... If you don't have bitcoin core, just use google and search for something like "decode raw bitcoin transaction online"... There are tons of tools to help you do exactly this... bitcoin-cli decoderawtransaction 01000000000104e1a701c900e771b6036122eb10a8c81f36fd82358da4e9aea8e45601bca55635110000006a473044022058d69a6f391e29906402ba8e33f5ce80890ebfc94122a5938b170128abb14da202200c1a846dc9f92b75f2dfd9227f5bc630d5b27b30711aeca4cbd50026cb239ea6012102c1befa3c4b3e4380aa6819f6f511db6b798db3ea5da69b0903eb25fea9076c20ffffffffdabcee894ef2216a128998e9fa2225cf93f9e62f66a634c4fc6b219359155ac70000000000ffffffff1c525d5f6424653b09ac89e5f7075d4c622d8e9acc3c205cfdc24770248c76510000000000ffffffffd737f1c9ff1a3aee2a6fb384b7b81f71ba17678710ab149843e0f0267842b99a0000000000ffffffff0270fe9500000000001976a91455fdac3573f34c67b1547de4ae0989ae94a71d1488acb05d7b0000000000160014b530b2573aab9d86fede0f0c5eb3315b16d654c80002483045022100b2e6dbc3f08615514ce81c9a8f6fd2a76f1e6cdbfe853b6995400b972668668602200af9225ac7aff3c8bf7a71c21adca097bb31ad64a52f7ae3bddfde4c23215a0e012103409f1b64a5c66599feafaf4cadfa84ab5c058aa3ef29e128582ae83717b19c5702483045022100e6805ee02d063d784d568318aa911b200afd138954bea2e52dc50777470fdac502203d48664a3ea3ebdd962364a3f373b6d4f182b7e3306dcbf0063ed5e2c5d87654012103409f1b64a5c66599feafaf4cadfa84ab5c058aa3ef29e128582ae83717b19c57024730440220476ef5c395dd30dacac4c5476cc7c6d258de9c8e7581c26304f27dded4e810f50220100163a5f440f01442ec1eaafece26e43a54d11ab1d686fd3bae22ae3c1e66db0121036346635ba513c63eb3b2afbc4e9d34ae5b5de9208e703ad0d3173c25c97626b400000000
{
"txid": "c24ba1552914fc6ff3c13b4f566374b1191b1203136de961c5d62825c3729920",
"hash": "a20d5717f0d8e25107f570009970da305e0e68f7c1a7d97c1321a62f95f796c4",
"version": 1,
"size": 671,
"vsize": 427,
"locktime": 0,
"vin": [
{
"txid": "3556a5bc0156e4a8aee9a48d3582fd361fc8a810eb226103b671e700c901a7e1",
"vout": 17,
"scriptSig": {
"asm": "3044022058d69a6f391e29906402ba8e33f5ce80890ebfc94122a5938b170128abb14da202200c1a846dc9f92b75f2dfd9227f5bc630d5b27b30711aeca4cbd50026cb239ea6[ALL] 02c1befa3c4b3e4380aa6819f6f511db6b798db3ea5da69b0903eb25fea9076c20",
"hex": "473044022058d69a6f391e29906402ba8e33f5ce80890ebfc94122a5938b170128abb14da202200c1a846dc9f92b75f2dfd9227f5bc630d5b27b30711aeca4cbd50026cb239ea6012102c1befa3c4b3e4380aa6819f6f511db6b798db3ea5da69b0903eb25fea9076c20"
},
"sequence": 4294967295
},
{
"txid": "c75a155993216bfcc434a6662fe6f993cf2522fae99889126a21f24e89eebcda",
"vout": 0,
"scriptSig": {
"asm": "",
"hex": ""
},
"txinwitness": [
"3045022100b2e6dbc3f08615514ce81c9a8f6fd2a76f1e6cdbfe853b6995400b972668668602200af9225ac7aff3c8bf7a71c21adca097bb31ad64a52f7ae3bddfde4c23215a0e01",
"03409f1b64a5c66599feafaf4cadfa84ab5c058aa3ef29e128582ae83717b19c57"
],
"sequence": 4294967295
},
{
"txid": "51768c247047c2fd5c203ccc9a8e2d624c5d07f7e589ac093b6524645f5d521c",
"vout": 0,
"scriptSig": {
"asm": "",
"hex": ""
},
"txinwitness": [
"3045022100e6805ee02d063d784d568318aa911b200afd138954bea2e52dc50777470fdac502203d48664a3ea3ebdd962364a3f373b6d4f182b7e3306dcbf0063ed5e2c5d8765401",
"03409f1b64a5c66599feafaf4cadfa84ab5c058aa3ef29e128582ae83717b19c57"
],
"sequence": 4294967295
},
{
"txid": "9ab9427826f0e0439814ab10876717ba711fb8b784b36f2aee3a1affc9f137d7",
"vout": 0,
"scriptSig": {
"asm": "",
"hex": ""
},
"txinwitness": [
"30440220476ef5c395dd30dacac4c5476cc7c6d258de9c8e7581c26304f27dded4e810f50220100163a5f440f01442ec1eaafece26e43a54d11ab1d686fd3bae22ae3c1e66db01",
"036346635ba513c63eb3b2afbc4e9d34ae5b5de9208e703ad0d3173c25c97626b4"
],
"sequence": 4294967295
}
],
"vout": [
{
"value": 0.09830000,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 55fdac3573f34c67b1547de4ae0989ae94a71d14 OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a91455fdac3573f34c67b1547de4ae0989ae94a71d1488ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"18qgKo15Q3sMWFw89UtUuv6iaixP4XF1k7"
]
}
},
{
"value": 0.08084912,
"n": 1,
"scriptPubKey": {
"asm": "0 b530b2573aab9d86fede0f0c5eb3315b16d654c8",
"hex": "0014b530b2573aab9d86fede0f0c5eb3315b16d654c8",
"reqSigs": 1,
"type": "witness_v0_keyhash",
"addresses": [
"bc1qk5cty4e64wwcdlk7pux9ave3tvtdv4xgl2uf6g"
]
}
}
]
}
|
|
|
|
Probably because they haven't updated their code since segwit...
and indicrypto cant fined pubkey for this adress, i think becouse no transction !
yup... If you haven't spent any unspent outputs funding a certain address, the public key has not yet been broadcasted... Bro how you get pubkey for bc1 ? I very need it. Explain please how to get pubkey for bc1 ?
There are many ways, but you can just use a blockexplorer if you want to... Or you can fetch the raw, signed transaction spending unspent outputs funding the address and decode said transaction... https://www.blockchain.com/btc/address/bc1qzgkzgavk6xveej7zpl9pwn2fw5l3lufwjyaze8or... here's the (only) raw tx spending funds that were previously funding bc1qzgkzgavk6xveej7zpl9pwn2fw5l3lufwjyaze8 01000000000104e1a701c900e771b6036122eb10a8c81f36fd82358da4e9aea8e45601bca55635110000006a473044022058d69a6f391e29906402ba8e33f5ce80890ebfc94122a5938b170128abb14da202200c1a846dc9f92b75f2dfd9227f5bc630d5b27b30711aeca4cbd50026cb239ea6012102c1befa3c4b3e4380aa6819f6f511db6b798db3ea5da69b0903eb25fea9076c20ffffffffdabcee894ef2216a128998e9fa2225cf93f9e62f66a634c4fc6b219359155ac70000000000ffffffff1c525d5f6424653b09ac89e5f7075d4c622d8e9acc3c205cfdc24770248c76510000000000ffffffffd737f1c9ff1a3aee2a6fb384b7b81f71ba17678710ab149843e0f0267842b99a0000000000ffffffff0270fe9500000000001976a91455fdac3573f34c67b1547de4ae0989ae94a71d1488acb05d7b0000000000160014b530b2573aab9d86fede0f0c5eb3315b16d654c80002483045022100b2e6dbc3f08615514ce81c9a8f6fd2a76f1e6cdbfe853b6995400b972668668602200af9225ac7aff3c8bf7a71c21adca097bb31ad64a52f7ae3bddfde4c23215a0e012103409f1b64a5c66599feafaf4cadfa84ab5c058aa3ef29e128582ae83717b19c5702483045022100e6805ee02d063d784d568318aa911b200afd138954bea2e52dc50777470fdac502203d48664a3ea3ebdd962364a3f373b6d4f182b7e3306dcbf0063ed5e2c5d87654012103409f1b64a5c66599feafaf4cadfa84ab5c058aa3ef29e128582ae83717b19c57024730440220476ef5c395dd30dacac4c5476cc7c6d258de9c8e7581c26304f27dded4e810f50220100163a5f440f01442ec1eaafece26e43a54d11ab1d686fd3bae22ae3c1e66db0121036346635ba513c63eb3b2afbc4e9d34ae5b5de9208e703ad0d3173c25c97626b400000000
Bro, does pubkey for bc1 dresses not start with "xpub" nope Is no error in 03409f1b64a5c66599feafaf4cadfa84ab5c058aa3ef29e128582ae83717b19c57 ?? no |
|
|
|
You can always combine tor with a good vpn while on a public wifi network in a place without CCTV camera's, then while connected trough tor + vpn put your funds trough several "hops"... A mixer => a no-KYC on the fly exchange to monero => some transactions between monero wallets => using a different no-KYC on the fly exchange back to btc => To the hotwallet of a no-KYC casino (gamble a bit) / withdraw afterwards => Coinjoin If you want to be completely anonymous, use the funds from the previous steps, rent a VPS, setup p2pool, rent some hashrate on miningrigrentals (or an equivalent service) and mine several blocks using a brand-new, never-used, offline created address as a coinbase address.... All these steps have to be done over tor+vpn. You can even go more paranoid than this (for example, by routing all your traffic over one or more bulletproof vps's that were purchased with mixed coins over tor/vpn)... But each step you add will cost you some extra funds... And a single screwup and it'll all have been in vain... I'd like to see the 3 letter agency that can tie the coinbase reward back to the initial funds  |
|
|
|
Well, a lot of people missed my first post (apparently), and they started a big fuss about changes in the bitcoin codebase, or even go as far as dragging erc20 tokens in the mix. i still couldn't find any real whitepaper (not that i spent that much time looking for it tough), but like i said before: this company is just developing a workaround.... Basically, right now, when i pay someone for a good or service, it basically boils down to: - The seller provides me with an address
- My wallet software creates a transaction, using unspent outputs funding my own addresses, creating a new unspent output funding the seller's address
- My wallet software signs said transaction
- My wallet software broadcasts said transaction
- As soon as the transaction reaches the first node, it's allmost irreversible... Sure, there are some tricks i can pull as long as it's unconfirmed... But those tricks are hard, and they work only untill the first confirmation...
What this company is doing, IF i understand this correctly: - The seller provides me with an address
- My wallet software creates a transaction, using unspent outputs funding my own addresses, creating a new unspent output funding the seller's address
- My wallet software signs said transaction
- My wallet contacts this company's server and saves an encrypted version of my transaction onto the company's server
- The seller receives a decryption key?
- Using this key, the seller can retrieve and decrypt the UNBROADCASTED transaction and verify it
- If the transaction's value is ok, and if it's indeed funding one of the seller's addresses, the seller now broadcasts the transaction? There's probably some automation involved so the wallet actually does the checking (and potentially even retrieving and decrypting the transaction from the previous step?)
- If something goes wrong, the buyer can always delete the unbroadcasted transaction from the server, as long as the seller hasn't decrypted and broadcasted it.... This way, the illusion of an undo button is created
At least, without a some clear documentation, this is what i believe the workflow more or less looks like... No hacks, no bitcoin code changes, no craptokens,.... Just a company that has developed a reasonably clever way of having an undo button that can be used as long as the receiver didn't broadcast the transaction. I, for one, think this is a clever trick... I have no problems with this, but i don't think i'd use the service quite that often tough... Maybe when i'm paying a newbie and i'm not 100% sure he/she gave me the correct address... |
|
|
|
Any stats about your default routing fees or total routed transaction? I believe you could earn a bit more if you set routing fees slightly higher than default.
For me, it was clear from the start that running a lightning node would make little to no money, so i left all fee-related settings completely default... cli/lightning-cli listconfigs
{
"# version": "v0.8.2-354-g7981f4c",
"lightning-dir": "/--snip--/.lightning",
"network": "bitcoin",
"allow-deprecated-apis": true,
"rpc-file": "lightning-rpc",
"plugin": "--snip--/pay",
"plugin": "--snip--/bcli",
"plugin": "--snip--/autoclean",
"plugin": "--snip--/keysend",
"plugin": "--snip--/fundchannel",
"plugins": [
{
"path": --snip--s/pay",
"name": "pay"
},
{
"path": "--snip--/bcli",
"name": "bcli",
"options": {
--snip--
}
},
{
"path": "--snip--/autoclean",
"name": "autoclean",
"options": {
"autocleaninvoice-cycle": null,
"autocleaninvoice-expired-by": null
}
},
{
"path": "--snip--/keysend",
"name": "keysend"
},
{
"path": "--snip--/fundchannel",
"name": "fundchannel"
}
],
"disable-plugin": [],
"always-use-proxy": false,
"daemon": "false",
"wallet": "sqlite3:--snip--",
"wumbo": false,
"wumbo": false,
"rgb": "03301e",
"alias": "mocacinno",
"pid-file": "--snip--g/lightningd-bitcoin.pid",
"ignore-fee-limits": false,
"watchtime-blocks": 144,
"max-locktime-blocks": 2016,
"funding-confirms": 3,
"commit-fee-min": 200,
"commit-fee-max": 2000,
"cltv-delta": 14,
"cltv-final": 10,
"commit-time": 10,
"fee-base": 1000,
"rescan": 15,
"fee-per-satoshi": 10,
"max-concurrent-htlcs": 30,
"min-capacity-sat": 10000,
"addr": "--snip--",
"offline": "false",
"autolisten": true,
"disable-dns": "false",
"enable-autotor-v2-mode": "false",
"encrypted-hsm": false,
"rpc-file-mode": "0600",
"log-level": "DEBUG",
"log-prefix": "lightningd",
"log-file": "debug.log"
}
Sure, i could probably make a "lot" more if i'd open extra channels and raised the fees, but i'm not really interested in this... I mean, even if this settings would multiply my income by 100, i'd still only make enough to buy 1 or 2 beers a year... Defenately not worth my troubles |
|
|
|
and the strange things is that i fund my password in that list - and i use a really long and complex password for coinomi ...
This changes everything... If there is even a shred of evidence this would mean that they were caught sending sensitive data "home" for the second time... Do be careful, the first time (when they allegedly sent seeds to Google) they spent loads of time, effort and money to "bury" the guy that uncovered the alleged infractions. |
|
|
|
hmm you enlighten me a bit. I mean i don't want to install node on my machine since it's already on network. I would like to install a server and that connect to it my electrum wallet. I want to connect only to this one desired node since. Thanks for explanation, would this https://github.com/kyuupichan/electrumx be fine for my case? aaaah... I start to see what you're aiming for here... So, basically: - somebody has a full node running on your network. It does have txindex=1, right? If not, start looking at something like electrs instead of electrumx
- you want to install an electrum server on your own machine, using this full node as a backend
- you want your electrum wallet connected to your electrum node
To be honest, i've only installed instances in which the full node and the electrum server were located on the same machine... That being said, your setup should be doable, i have no idear if there will be caveats though... Electrumx is a decent electrum server, i think it should be able to do what you want to achieve You'll probably want to point your env var DAEMON_URL to the remote node you're using as a backend... https://github.com/kyuupichan/electrumx/blob/master/docs/environment.rst |
|
|
|
|
Nope... Transactions are still irreversible, even with this platform...
There is no whitepaper available, but after reading a couple press releases (with very limited technical details), it looks like they just require the receiver to validate the transaction funding his wallet before said transaction is actually broadcasted. This way, it becomes harder for a hacker, copy/paste virus or a simple mistake to happen (since the sender does no longer just broadcast the transaction, but basically forces the receiver to validate before the transaction is broadcasted). If the validation fails, it's like nothing happens.
But nothing happening =/= reversibility
It's just a clever workaround that gives the impression of reversibility...
|
|
|
|
|
I have a hard time following which problem you're trying to solve, and which steps you actually took...
You install a server (OS), on this server you install a litecoin node... You use litecoin-cli to query this node.
But in your post, you're talking about setting up a server (while linking to the setup instructions for a full node), then you say that you have a (second?) node on your network aswell? Then you connect your server (which in your case should be a node, since you followed instructions on how to setup a node) to a (second?) node... Why?
Usually, you just setup a node, it'll use a dns seed to find other nodes and it'll do an initial sync from these other nodes... No need to connect to one specific node.
Maybe it's best if you describe your setup in more detail, and maybe look in the debug.log to see if your node is healthy and fully synced...
|
|
|
|
|
I'm defenately not a fan of coinomi... But it would seem strange if they actually used your pc for bruteforcing salted md5 hashes...
I have no idear who you are, what your technical knowledge is, and how clean you keep your computer... But my first tought would be that you downloaded some malware, even a fake version of coinomi, and the malware is using your computer's resources to crack passwords...
Only my first tought tough... No idear if coinomi messed up, but the odds are bigger that you downloaded some malware next to coinomi.
Did your system load increase dramatically while this event was happening?
|
|
|
|
If i'm not mistaking, bluewallet supports electrum's custom seed format... https://github.com/BlueWallet/Not 100% sure tough (i've heared this statement before, but never tested it) |
|
|
|
I see you guys have a theoretical discussion, and i'm not really interested in trying to actively promote nor discourage the lightning network... I'm merely interested in testing out this stuff... And i don't mind sharing my stats: cli/lightning-cli getinfo
{
"id": "03301e633b25d769377bf75ce6b6ed2ec570270bc06c8c02bf33c5bd2aa47da098",
"alias": "mocacinno",
"color": "03301e",
"num_peers": 21,
"num_pending_channels": 0,
"num_active_channels": 17,
"num_inactive_channels": 0,
"address": [
{
"type": "ipv4",
"address": "--snip--",
"port": 9735
}
],
"binding": [
{
"type": "ipv4",
"address": "--snip--",
"port": 9735
}
],
"version": "v0.8.2-354-g7981f4c",
"blockheight": 637493,
"network": "bitcoin",
"msatoshi_fees_collected": 88909,
"fees_collected_msat": "88909msat",
"lightning-dir": "--snip--"
}
I don't quite remember when i started running a lightning node, but it was before there were any good explorers available... Defenately > 1 year ago. So, less than 100 sat/year... You do need to run a full node, and c-lightning on top... So you need a semi-decent server for this, defenately not worth your time or energy bill... But if you run a node anyways, i don't see a problem with running a lightning node on top of it aswell... |
|
|
|
@o_e_l_e_o: you are 100% correct, but you messed up the quote in your previous post... I never claimed that: Private key 1 = Hash(seed +"1") Private key 2 = Hash (seed + "2") I was quoting BlackHatCoiner when he assumed this fact, but the quote has been messed up so it looks like i was the one who made this assumption |
|
|
|
I use a blockchain.com for a long time and I think that it is a good and compfortable in usage wallet. It is safe.
So, because you have used blockchain.com for a while and didn't suffer any loss, you are comfortable endorsing it... Blockchain.com stores your wallet on their servers (they claim it's encrypted, but you never know). Blockchain users have fallen victim to phising scams. Blockchain users are vulnerable to malicious browser plugins. Blockchain is known for bugs (some critical, some annoying). Blockchain support is slow and usually not really helpfull. My dad used to smoke and work with asbestos on a daily basis for 45 years, and he still doesn't have lung cancer (i really hope he stays safe tough...), maybe it's time for him to start declaring that smoking is safe and asbestos is not dangerous either? |
|
|
|
Yes but isn't easier for someone to brute force a seed? Sorry, but I don't get how the seed works. You say that by having it you have access to all of your keys. Does it work like that?
Private key 1 = Hash(seed +"1")
Private key 2 = Hash (seed + "2")
And so on.
Many interesting discussions have been devoted to this topic... For example: bitcointalk.org/index.php?topic=1716725.0 Bottom line is pretty simple: no, it's not easy to brute force a seed... A seed might look like just 12 words out of a fixed wordlist... So a normal person would assume it's as safe as a 12 character password... But it's not... It's as safe as a 12 character password using random characters out of a 2048 character set (well, the last word is a checksum)... And to top it off, one iteration while brute-forcing a seed is very resouce intensive (seed => master private key => derivation of private key 1 => public key 1 => address 1 => checking for balance... derive the next private key, check all derivation paths,...). So far, i haven''t heared about any key collisions that weren't caused by some bug in the rng... It's just one of those things that are hard to grasp, a seed looks really easy to brute-force since it's just a string of 12 words you actually know... But if you'd try to write a small script to scan the complete keyspace, you'd very soon learn that it's basically "allmost impossible" (defenately with the hardware we currently have) |
|
|
|
|
Show Posts
