Search content
Sort by
Showing 8 of 8 results by Juinyu
Re: [SDC] ShadowCash | POSV3 | Untraceable E-Cash | NIZKP | HD+BIP32 | ShadowMarket*
To be honest, just stick with ShadowMarket. Who the fuck cares if the word 'shadow' has a negative connotation? Don't censor yourself. You should be proud of the name ShadowCash / Market. And especially don't Darkcoin / Dash this awesome project by rebranding. If whoever has a problem with this project's name, tell them to stop being whiny cunts and to go fuck themselves.
Re: [SDC] ShadowCash | POSV3 | Untraceable E-Cash | NIZKP | HD+BIP32 | ShadowMarket*
I2P: Not merged, but there is a repo available with I2P support. You can send me a message, and I'l gladly help.
You'd need to setup your box to do the following, (Shadow -> I2P) -> Tor. It's not an easy setup to do, you can however do it with Whonix. On a VPS? I don't think so, unless I2P supports proxies.
We have support of Tails, with persistence to an USB. We haven't tested Qubes OS or Subgraph OS but we will explore that in the future.
^Check our github repo for the tails script.
You'd need to setup your box to do the following, (Shadow -> I2P) -> Tor. It's not an easy setup to do, you can however do it with Whonix. On a VPS? I don't think so, unless I2P supports proxies.
We have support of Tails, with persistence to an USB. We haven't tested Qubes OS or Subgraph OS but we will explore that in the future.
^Check our github repo for the tails script.
Hi there, thanks for your response!
Well, instead of pushing all the Shadow traffic through Tor, I'd rather use I2P for that matter. Also Shadow -> I2P -> Tor isn't a very good idea, simply because you'd be leeching without any contribution to either one of them, according to Whonix's documentation:
Quote
Installing I2P inside Whonix-Workstation (I2P over Tor)
It is possible to run I2P inside the Whonix-Workstation.
user -> Tor -> I2P
Advantages:
Anonymity is provided by Tor.
I2P router console works normal inside Tor Browser. No need to install a graphical user interface on the Whonix-Gateway.
Eepsites (.i2p) can be reached directly from Tor Browser.
I2P's end-to-end encryption will be used like usual.
Disadvantages:
Adds load to Tor.
Adds load to I2P.
It's slower than I2P directly on Whonix-Gateway or the ordinary usage.
No contribution to the I2P network (leeching).
It is possible to run I2P inside the Whonix-Workstation.
user -> Tor -> I2P
Advantages:
Anonymity is provided by Tor.
I2P router console works normal inside Tor Browser. No need to install a graphical user interface on the Whonix-Gateway.
Eepsites (.i2p) can be reached directly from Tor Browser.
I2P's end-to-end encryption will be used like usual.
Disadvantages:
Adds load to Tor.
Adds load to I2P.
It's slower than I2P directly on Whonix-Gateway or the ordinary usage.
No contribution to the I2P network (leeching).
Source: https://www.whonix.org/wiki/I2P
Could you please be so kind and point me to the Tails script? Checked Github and I'm not able to find it
Would I have to reinstall Shadow every time I fire up Tails? Although that wouldn't be a problem as long as it's pretty straightforward to backup the vital data, especially the wallets. Do you have any best pratices advice?Also another question: Does one have to buy SDC before being able to get SDT? Or is it also possible to directly buy SDT? From an anonymity / privacy point of view what would the devs recommend?
Since DeepDotWeb and other media outlets have written nice articles about the Shadow Project, and the ongoing blockchain analysis by the federal cunstables, being able to run Shadow on Tails would be huge! If there's any documentation available on how to install it on Tails or any other anonymity / privacy oriented distribution please make them more accessible, this project really deserves more attention, so please don't bury yourselves in all those Slack holes
I2P has a tunnal wizard, what tunnel should one create for Shadow? Setting those up is really easy. Will Shadow have an option which allows to choose between I2P or Tor?
If by any chance you happen to have instructions on how to get it done, I'd gladly try it out and post my experiences on setting up Shadow in Tails, also sending thinking about sending a little guide to DeepDotWeb and spreading the word.
To the devs: Are you planning to have I2P support built-in before the market gets released? In my opinion any anonymity / privacy feature should be viable, otherwise our asses would be at stake. Also please don't go the OpenBazaar route, by releasing the software without giving a few thoughts to OpSec. The OB people chose to butt rape anonymity a la "Hey OB uses UDP, Tor doesn't support it, but hey you could use a VPN..." lol.
Cheers!
Re: [SDC] ShadowCash | POSV3 | Untraceable E-Cash | NIZKP | HD+BIP32 | ShadowMarket*
https://i.imgur.com/hcZJizJ.jpg
Another great start of the month with lots of changes and improvements! We've given our lead developer Rynomster a bit of well deserved time off last week, but he's back to development again. The other team members didn't stand still, they have been busting their asses again in an effort to create the tools the community needs.
Read more at
https://blog.shadowproject.io/2016/04/07/back-on-track/
Another great start of the month with lots of changes and improvements! We've given our lead developer Rynomster a bit of well deserved time off last week, but he's back to development again. The other team members didn't stand still, they have been busting their asses again in an effort to create the tools the community needs.
Read more at
https://blog.shadowproject.io/2016/04/07/back-on-track/
Great news! I, we, really appreciate all your hard work! I think this will pay off once ShadowMarket is here. Honestly there should be a option (or maybe forced) to pay a small fee everytime one places an order.
Also what's the status on the I2P support? Would it work to have a I2P router on a VPS and tunnel the SAM bridge through Tor and SSH? Since OpenBazaar uses UDP (Tor supports TCP), the Shadow Project has a huge possibility to actually do something for the anonymity and privacy of their users.
Did someone manage to install Shadow in Qubes OS / Subgraph OS / Tails (what about editing Tails' persistence.conf to store ShadowCash permanently on the persistent volume)? Would this also be able to work on Unix (e.g. FreeBSD)?
http://cointelegraph.com/news/homeland-security-bitcoin-task-force-revealed-by-department-of-justice-indictment-form
Don't expect those government cunts to respect our financial privacy. Also let's abolish those fucking AML / KYC "laws" (lol).
To quote George Hotz (Geohot):"I live by morals, I don't live by laws," he went on. "Laws are something made by assholes."
Re: [SDC] ShadowCash | POSV3 | Untraceable E-Cash | NIZKP | HD+BIP32 | ShadowMarket*
Hi devs,
have you heard of Subgraph OS?
https://subgraph.com/
https://motherboard.vice.com/read/subgraph-os-wants-to-make-using-a-secure-operating-system-less-of-a-headache
https://thehackernews.com/2016/03/subgraph-secure-operating-system.html
I wonder if Subgraph OS could be a viable option for security minded people who don't like using crap like Windows for their finances.
Sandboxing the Shadow wallet, routing all traffic through I2P / Tor and denying clear net connections.
have you heard of Subgraph OS?
https://subgraph.com/
https://motherboard.vice.com/read/subgraph-os-wants-to-make-using-a-secure-operating-system-less-of-a-headache
https://thehackernews.com/2016/03/subgraph-secure-operating-system.html
I wonder if Subgraph OS could be a viable option for security minded people who don't like using crap like Windows for their finances.
Sandboxing the Shadow wallet, routing all traffic through I2P / Tor and denying clear net connections.
Re: [SDC] ShadowCash | POSV2 | Untraceable E-Cash | NIZKP | HD+BIP32 | ShadowMarket*
https://github.com/shadowproject/tails-scripts
Enjoy ...
This will compile the ShadowCore QT client and download verified blockchain and set that up. Once you start the Shadow client you will have at most "a few days" of data to sync.
So aside from the time taken to compile and download you will be up and running in minutes.
Enjoy ...
This will compile the ShadowCore QT client and download verified blockchain and set that up. Once you start the Shadow client you will have at most "a few days" of data to sync.
So aside from the time taken to compile and download you will be up and running in minutes.
That's really great news! Thank you and all the devs!
There's a 'Call for testing: 2.0~beta1' https://tails.boum.org/news/test_2.0-beta1/index.en.html
Quote
You can help Tails! The first beta for the upcoming version 2.0 is out. We are very excited and cannot wait to hear what you think about it
What's new in 2.0?
Tails 2.0 will be the first version of Tails based on Debian 8 (Jessie). As such, it upgrades essentially all included software.
The most noticeable change is probably the move to GNOME Shell, configured in Classic mode. This desktop environment provides a modern and actively developed replacement for the aging GNOME "Flashback". GNOME Shell also paves the way for better supporting touchscreens in the future.
Under the hood, an amazing amount of code was ported to more modern technologies. This, in turn, allowed us to do lots of small changes all around the place, that will make the Tails experience both safer, and more pleasant. For example, all custom system services are harder to exploit thanks to the use of Linux namespaces, set up by systemd. And the way Tails tells the user that "Tor is ready" is now more accurate.
But really, there are simply too many changes to describe them all here, so just try Tails 2.0~beta1 yourself!
Technical details of all the changes are listed in the Changelog.
There is only one piece of bad news, that makes us a bit sad, though: we had to remove the Windows camouflage feature, since our call for help to port it to GNOME Shell (issued in January, 2015) was unsuccessful.
What's new in 2.0?
Tails 2.0 will be the first version of Tails based on Debian 8 (Jessie). As such, it upgrades essentially all included software.
The most noticeable change is probably the move to GNOME Shell, configured in Classic mode. This desktop environment provides a modern and actively developed replacement for the aging GNOME "Flashback". GNOME Shell also paves the way for better supporting touchscreens in the future.
Under the hood, an amazing amount of code was ported to more modern technologies. This, in turn, allowed us to do lots of small changes all around the place, that will make the Tails experience both safer, and more pleasant. For example, all custom system services are harder to exploit thanks to the use of Linux namespaces, set up by systemd. And the way Tails tells the user that "Tor is ready" is now more accurate.
But really, there are simply too many changes to describe them all here, so just try Tails 2.0~beta1 yourself!
Technical details of all the changes are listed in the Changelog.
There is only one piece of bad news, that makes us a bit sad, though: we had to remove the Windows camouflage feature, since our call for help to port it to GNOME Shell (issued in January, 2015) was unsuccessful.
Since they are switching to Debian Jessie, do you know if it will be more easy to compile ShadowCash on Tails due to dependencies?
May I suggest that the devs contact DeepDotWeb who had written very nice and informative articles about ShadowCash, e.g. https://www.deepdotweb.com/2015/01/28/shadowcash-zero-knowledge-anonymity/
To inform them that it is possible to compile ShadowCash on Tails, also a Reddit posting or a tweet could be nice for awareness
Re: [SDC] ShadowCash | POSV2 | Untraceable E-Cash | NIZKP | HD+BIP32 | ShadowMarket*
Only slightly familiar with Tails. Is there an option to save data permanently in Tails? Downloading the blockchain every time Tails boots would be very inconvenient.
Yes, Tails has an option to enable an encrypted persistent volume.
My understanding is Tails has an option for "persistent volume" ... in which case it should work. I have not tested it though yet and would certainly weaken some of its appeal.
In reference to TOR/I2P .. you can run the wallet on a normal PC and point the Proxy (Tor) or SAM Bridge (I2P) to the Tails device.
On a side note, I2P works best when it has been running for a few hours (preferably days) ... so your best bet is to have a dedicated device which runs the I2P router and pointing the SAM Bridge connection from the Shadow wallet to it .. a RPI would be perfect for this and support the I2P network.
In reference to TOR/I2P .. you can run the wallet on a normal PC and point the Proxy (Tor) or SAM Bridge (I2P) to the Tails device.
On a side note, I2P works best when it has been running for a few hours (preferably days) ... so your best bet is to have a dedicated device which runs the I2P router and pointing the SAM Bridge connection from the Shadow wallet to it .. a RPI would be perfect for this and support the I2P network.
I really like the idea of separation, therefore having everything Bitcoin / ShadowCash related on a different 'machine' sounds neat.
Yes, a RPI could be nice for running I2P 24/7. Additionally having the possibility to install ShadowCash on Tails could potentially help the project, especially with the market around the corner. Also the user don't have to configure / install I2P or Tor since Tails already provides both. But being able to install it on Tails offers another useful thing: One solid base OS, there lots of Tails users out there, which could also become ShadowCash users and there it could be easier to offer instructions on how to get it to work. I hope you get what I mean.
Hello,
I've found instructions on how to install Armory's offline bundle on Tails 1.3 (http://bitzuma.com/posts/offline-installation-of-armory-on-tails-and-ubuntu-linux/).
My question is: I'd like to use multiple USB devices, one for the offline bundle which creates wallets, functions as a cold storage and signs offline transactions, a second one which is used on a Tails 1.8 device with enabled persistence in conjunction with bitcoind or bitcoin-qt to download the Blockchain (according to https://tailsjoin.github.io/guides/install_guide.html bitcoind or bitcoin-qt work on Tails, however enough free space to actually store the Blockchain is necessay). And a third USB device or read-only CD with PGP encrypted offline transactions to transfer it to the device which will broadcast it.
Is this possible to achieve? Do I need all the listed .deb packages which are in the first link? And could the Armory offline bundle simply be 'turned' on by being installed on a Tails device which has the Blockchain on it?
Sorry, for my bad English and many thanks in advance! Could some dev please be so kind and take a look at this, any help would be really appreciated.
Cheers,
Juinyu
I've found instructions on how to install Armory's offline bundle on Tails 1.3 (http://bitzuma.com/posts/offline-installation-of-armory-on-tails-and-ubuntu-linux/).
My question is: I'd like to use multiple USB devices, one for the offline bundle which creates wallets, functions as a cold storage and signs offline transactions, a second one which is used on a Tails 1.8 device with enabled persistence in conjunction with bitcoind or bitcoin-qt to download the Blockchain (according to https://tailsjoin.github.io/guides/install_guide.html bitcoind or bitcoin-qt work on Tails, however enough free space to actually store the Blockchain is necessay). And a third USB device or read-only CD with PGP encrypted offline transactions to transfer it to the device which will broadcast it.
Is this possible to achieve? Do I need all the listed .deb packages which are in the first link? And could the Armory offline bundle simply be 'turned' on by being installed on a Tails device which has the Blockchain on it?
Sorry, for my bad English and many thanks in advance! Could some dev please be so kind and take a look at this, any help would be really appreciated.
Cheers,
Juinyu
Re: [SDC] ShadowCash | POSV2 | Untraceable E-Cash | NIZKP | HD+BIP32 | ShadowMarket*
Great update! Regarding I2P / Tor support: Dear devs, please post instructions on how to install ShadowCash on Tails 1.8, since it comes both with I2P and Tor already pre-installed and pre-configured.