Bitcoin is entirely different. Tor has a few centralized servers that can distribute certificates, but Bitcoin does not. You could use encryption without authentication, but this would not prevent men-in-the-middle from intercepting your traffic: it would just be obfuscation. Including secure encryption might be impossible without some sort of friend-to-friend system.
Ahem.. Key exchange. Generate a cert upon install. The official client won't make outgoing connections to non-standard ports, so this would not be good for the network.
I want this bundled with the official client. I'm not looking for a fork. Just use Tor with Bitcoin, then. They've already got this stuff solved.
99.99% of average people have no clue how to setup Bitcoin to use Tor. Assuming that other people know as much as you/I/us know will kill this project. If we want mass adoption this software has to be robust, simple to use, and "just work". This includes when China/North Korea/"Insert bad government" blocks it. We need to be proactive here. Not reactive. Telling people to install another program and educate them on how to chain them together is not a fix. It's a giant ugly "hack". Edit: A key cache similar to how SSH handles keys could be added to Bitcoin to prevent MITM attacks. |
|
|
|
1) SSL would require all clients to upgrade.
How so? The current build links against openssl already. Preserving the existing port 8333 listener thread would maintain backward compatibility for some time. 2) Random TCP ports could be annoying for users running other services on their computers on certain ports when Bitcoin decides to use them.
It's random selection upon install. The user can, of course, change the port. Look at how I2P works upon first install. 3) UPnP would really be useful with all those NAT gateways.
Uh huh.  |
|
|
|
Hello all, I am offering a personal bounty of $2K USD $250 USD for the following features to be added into Bitcoin. I'd code them myself, but time restraints won't permit me to. Let me hire you. 1. Bitcoin should run its P2P operations in straight SSL. It should look like FF talking to Apache to any DPI. See the Tor source code. Most of the work is done already. REPEALED - See discussion.2. On first run Bitcoin should select a random high TCP port (>1024) and save it to the bitcoin.conf. (something like "listenerport=8972"). This port should contain the new SSL-only listener. Do we need to keep the old port 8333 listener running for compatibility for a while? REPEALED - The port number should be selectable by the user; not random. See discussion.3. UPnP support. Bitcoin should port forward the chosen high TCP port automatically. (Possibly port 8333/tcp too, if the answer to the question above is "Yes"). The GUI/command line should have a UPnP off/on toggle. It should be "on" by default. $250 Bounty still offered. UPnP should be off by default on the Linux build.It's just a matter of time before Bitcoin is blocked in all of "those" countries that have oppressive regimes. We need to resist stuff now before Bitcoin gains traction. I'm not looking to reinvent the wheel here (Tor). I just want to make it more resistant to DPI blocking-related attacks. Better off with a distribution of Bitcoin with Tor included. Hopefully those under repressive regimes already know about/use Tor. Having Tor installed offers other benefits besides Bitcoin.If these 3 features are implemented in the next 30 days, I'll throw in an additional $500 USD. Payable in Bitcoin or in pre-loaded VISA cards from Bitcoin2CC - your choice.The Madhatter |
|
|
|
2 million dollar market cap is really nothing. However, it's a great start.  If the US were to implement such a network there would be a lot of people writing software to circumvent it. I also would suspect that the hosting/IT industries in the US would take quite a financial hit as people hosted their sites elsewhere. Does the US economy need another large blow? I know! We should bundle and sell Internet 2 futures!  (sarcasm) Lots of fiber has been setup to purposely bypass the USA in recent years. (Probably due to the NSA/AT&T spying fiasco.) The infrastructure for a large hosting shift is already in place. What about the end users being locked into this Internet 2 control grid? - You may ask. The uber geeks would install satellite internet services purchased from other countries to bypass it and run 802.11s (mesh) to propagate "clean" Internet. They just can't win this one. lol! Does the US government expect every private corporation to replace all of their routers to handle these authenticated packets? At whose expense? This won't happen. (See: IPv6) Some examples of failures that "they" are still trying to implement: - Look at the migration to IPv6. It's a disaster! Unless IPv6 is designed as a backwards-compatible extension to IPv4, migration will never happen. - Look at DNSSEC. It's only a 18 year old project that doesn't work. Collectively all of the DNSSEC-enabled hosts are a giant DDoS amplifier. The host hashes can be inverted easily with GPUs, NXDOMAIN requests are unsigned (so they can still be spoofed). I could go on and on here. Cheers! The Madhatter |
|
|
|
|
I can confirm that db4.7 and db4.8 work perfectly on FreeBSD. I have not tried switching db versions on active Bitcoin installations. I had suspected the file formats may be different.
|
|
|
|
|
*cough* *cough* Usury! *cough* *cough*
|
|
|
|
|
Every "free" nation on the globe is controlled by the same evil schmucks.
"Permit me to issue and control the money of a nation, and I care not who makes its laws." - Amschel Mayer Rothschild
|
|
|
|
Hello all, I can confirm that our version of the TSA in Canada (called "CATSA" here) now performs a similar molestation even on domestic flights. My beautiful country is lost too. It saddens me so....  The Madhatter |
|
|
|
Here is the complete makefile.unix that I used to build Bitcoin 0.3.19 on FreeBSD-8.1-RELEASE/amd64: You'll need to install the following from ports: gmake boost-all db47 (you can use db48, but you'll have to change the makefile a bit) openssl (from ports works best) After you drop in this makefile.unix file, just run "gmake -f makefile.unix bitcoind" and you'll have a "bitcoind" binary. # Copyright (c) 2009-2010 Satoshi Nakamoto
# Distributed under the MIT/X11 software license, see the accompanying
# file license.txt or http://www.opensource.org/licenses/mit-license.php.
INCLUDEPATHS= \
-I"/usr/local/include/wx-2.9" \
-I"/usr/local/lib/wx/include/gtk2-unicode-release-2.9" \
-I"/usr/local/include/db47" \
-I"/usr/local/include"
LIBPATHS= \
-L"/usr/local/lib/db47" \
-L"/usr/local/lib" \
-L"/usr/lib"
# for wxWidgets 2.9.1, add -l Xxf86vm
WXLIBS= \
-Wl,-Bstatic \
-l wx_gtk2ud-2.9 \
-Wl,-Bdynamic \
-l gtk-x11-2.0 \
-l SM
# for boost 1.37, add -mt to the boost libraries
#LIBS= \
# -Wl,-Bstatic \
# -l boost_system \
# -l boost_filesystem \
# -l boost_program_options \
# -l boost_thread \
# -l db_cxx \
# -l crypto \
# -Wl,-Bdynamic
# for boost 1.37, add -mt to the boost libraries
LIBS= \
-Wl,-Bstatic \
-l boost_system \
-l boost_filesystem \
-l boost_program_options \
-l boost_thread \
-l db_cxx \
-l ssl \
-l crypto \
-Wl,-Bdynamic \
-l z \
-l pthread
DEFS=-D__WXGTK__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -D__BSD__
DEBUGFLAGS=-g -D__WXDEBUG__
CFLAGS=-O2 -march=nocona -fstack-protector -Wno-invalid-offsetof -Wformat $(DEBUGFLAGS) $(DEFS) $(INCLUDEPATHS) $(LIBPATHS)
HEADERS=headers.h strlcpy.h serialize.h uint256.h util.h key.h bignum.h base58.h \
script.h db.h net.h irc.h main.h rpc.h uibase.h ui.h noui.h init.h
OBJS= \
obj/util.o \
obj/script.o \
obj/db.o \
obj/net.o \
obj/irc.o \
obj/main.o \
obj/rpc.o \
obj/init.o \
cryptopp/obj/sha.o \
cryptopp/obj/cpu.o
all: bitcoin
obj/%.o: %.cpp $(HEADERS)
g++ -c $(CFLAGS) -DGUI -o $@ $<
cryptopp/obj/%.o: cryptopp/%.cpp
g++ -c $(CFLAGS) -O3 -o $@ $<
obj/sha256.o: sha256.cpp
g++ -c $(CFLAGS) -msse2 -O3 -march=nocona -o $@ $<
bitcoin: $(OBJS) obj/ui.o obj/uibase.o obj/sha256.o
g++ $(CFLAGS) -o $@ $^ $(WXLIBS) $(LIBS)
obj/nogui/%.o: %.cpp $(HEADERS)
g++ -c $(CFLAGS) -o $@ $<
bitcoind: $(OBJS:obj/%=obj/nogui/%) obj/sha256.o
g++ $(CFLAGS) -o $@ $^ $(LIBS)
clean:
-rm -f obj/*.o
-rm -f obj/nogui/*.o
-rm -f cryptopp/obj/*.o
-rm -f headers.h.gch Edit: If you want the GUI you'll need to install "x11-toolkits/gtk20" from ports, and install wxwidgets 2.9 from source (it's not in the ports tree). Use the makefile above and run "gmake -f makefile.unix bitcoin". |
|
|
|
|
I like the tentacle-covered rothchild thing! Haha
|
|
|
|
Do you actually get any xactions for that?
Yes, but not very often. If you are Canadian (I'm presuming you are), have you considered Interac email money transfers? Or do you prefer the papertrail-free route?
My mailboxes are in Canada. I don't accept Interac transfers for the reasons presented by nanaimo gold. Chargebacks, etc. Cheers! The Madhatter |
|
|
|
Lol! I should put some 'Canada permanent stamps' on Bitcoin Gadgets. |
|
|
|
I have to agree with nanaimogold. Accepting PayPal for Bitcoin is a very bad idea. It is just a matter of time before you are scammed into oblivion. I wish I had better news for you, but I've seen it happen way too many times.  The Madhatter |
|
|
|
Hello all, The title is self-explanatory. I'll just leave this here. Cheers! The Madhatter Edit: For those who don't already know, Bitcoin4Cash is here. |
|
|
|
|
Yes, we ship to Mexico. Shipping is free.
|
|
|
|
Too many adults still have a childlike faith in the abilities of the police.
Ain't that the truth. The police here couldn't find their ass with both hands. They'd likely just have glazed-over eyes if you tried to report a stolen wallet.dat file. If you were really lucky they'd find something to charge you with. Perhaps a burnt out tail light on your car? |
|
|
|
You just answered my question. I was googling for "bitcoin zen cart" earlier when bitcoingadgets.com popped up. I thought: "Cool. I wonder whose site this is?" Now that I know it's trustworthy, I'm going to go back and order one of those TV-B-gones.
The site is more or less a partnership. I'm handling the Bitcoins/running the website, and a friend of mine is handling the shipping and updating the catalog. Do you really have 1000 in stock? No. Probably a hundred at most. (Not my department so I don't know off hand.) Zen cart is weird. It requires stock. So for now I just went into the database and set all of the quantities to 1000. How much trouble was it to get Zen Cart working? I've heard it can be a pain.
It wasn't too bad. I ended up just hacking the money order payment module and making it dish out a Bitcoin address at the end of the order. I also had to build a simple script on a crontab that polls the Bitcoin exchange rate and sets it in the zen cart database. My partner insisted on us pricing the goods in US Dollars internally, and displaying the prices in BTC. I had no objections. I know the module and crontab work because the other site ( Bitcoin Sex Toys), has had a few successful orders already. Oh, and since you're the Mad Hatter, I think you should sell magic mushroom tea.
 |
|
|
|
|
Show Posts
