Hello,
The obfs4 executable shipped currently misses a fix (commit
`393aca86cc3b1a5263018c10f87ece09ac3fd5ed`) that should in theory make
the traffic truly indistinguishable.
This is the Tor Browser ticket:
https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40791
And this is
intrigeri wrote:
> Hi,
>
> s7r:
>> It would be neat to get some help - I have tried unsuccessfully reaching
>> to the debian cryptocoin team as well as some package maintainers that I
>> saw maintain packages related to this area, but nothing. I am still
>>
intrigeri wrote:
> Hi s7r,
>
Hello,
[SNIP]
>
> Any news?
> What kind of timeline do you have in mind for the next steps?
Unfortunately news are slow to come for this.
The phishing vulnerability is fixed, servers have all implemented DoS
protection to survive the DoS attacks, c
Hi,
intrigeri wrote:
> Hi,
>
> first, thanks a lot to everyone who contributed to this thread!
>
> s7r:
>> mithrandi is of course interested into continuing to maintain Electrum
>> in Debian and will do so, but we should find other people also to work
>> a
s for the project. I'm personally really not
>>> thrilled at the idea of spending a lot of time dealing with this
>>> situation.
>>
>> Yep. That's in line with our decision a couple years ago to remove
>> Electrum unless someone stepped up to maintain its integr
u wrote:
> Hi!
>
> On 19.03.19 18:07, sajolida wrote:
>
>> If we decide not to ship the AppImage, we could also try to contact the
>> Debian maintainer.
>
> I'll do that right away.
>
> Cheers!
> u.
Hello,
Thank you very much sajolida for the write up! Very, very well and
clearly written.
I
s7r wrote:
> Hello,
>
> intrigeri wrote:
>> Hi,
>>
>> adding s7r, who is maintaining the integration of Electrum in Tails,
>> into the loop:
>>> node.ad...@secmail.pro:
>>> I run a ElectrumX on a hidden service
>>
>>> 4yi77lkjgy4
Hello,
intrigeri wrote:
> Hi,
>
> adding s7r, who is maintaining the integration of Electrum in Tails,
> into the loop:
> > node.ad...@secmail.pro:
>> I run a ElectrumX on a hidden service
>
>> 4yi77lkjgy4bwtj3.onion port 50001 for TCP and port 50002
>
out the "won't work" arguments, but as I see it this will
complicate things for users, leave more attack surface and place for
mistakes from average users this degrading their security level
considerably, with no actual real benefit.
I can see you have some knowledge in this field, so inst
Hello again,
intrigeri wrote:
> Hi s7r & list,
>
> s7r:
>> intrigeri wrote:
>> That was a great idea, got countless appreciations for that and also,
>> based on the feedback I receive and discussions the feature is *very*
>> popular in Tails. We should def
Hello intri
intrigeri wrote:
> Hi!
>
> 2.5 years ago we added the Electrum lightweight Bitcoin client
> to Tails. It's hard to tell for sure how popular this feature is, but
> the fact is that at least a few people (who either are already using
> Electrum in Tails, or would like to) are very voca
Hello intrigeri, Michael,
intrigeri wrote:
> Hi Michael,
>
> Michael English:
>> It also helps to reduce blockchain UTXO (unspent transaction
>> outputs) bloat,
>
> This makes me curious. How does this help with that property, exactly?
> My intuition tells me that by restricting the set of coins
on external backup of the seed in addition
> to using persistence, as suggested by s7r. 2. Apply the grammar
> fixes and phrasings suggested by Michael. 3. Make the warning about
> SPV less scary and more useful by focusing on transaction
> confirmation. I was quite convinced by the d
except slight performance issues (sometimes it
takes little longer to connect, because servers are behind DoS
mitigation services which filter Tor, etc.).
On 12/4/2015 5:12 PM, Michael English wrote:
> s7r,
>
> Since we will probably have to wait for at least one more release
> of El
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/5/2015 10:38 PM, Michael English wrote:
> You have thoroughly criticized my documentation to help users
> secure Electrum in Tails. I ask you again what would you change in
> the current documentation where it warns about SPV. Would you
> remo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/5/2015 6:30 PM, Michael English wrote:
> My main goal with the documentation is informing users of the
> vulnerabilities of Electrum in Tails to promote secure practices.
>
> I don't think that Bitcoin should be installed in Tails in the
> f
e notes. If you think that the
> behavior itself might be confusing, then I guess that this should
> be solved upstream (in their documentation or the software
> directly).” S7r and I disagree. Simply noting the change of default
> base unit could have a big impact in avoiding confusion.
&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello Sajolida, Michael,
See inline.
On 11/22/2015 2:00 PM, sajolida wrote:
> Michael English:
>> Sajolida, please forward this message to s7r.
>
> Done.
>
Thanks!
>> s7r,
>>
>> If you do not have any spec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/26/2014 3:47 PM, intrigeri wrote:
> Hi,
>
> Lunar wrote (26 Feb 2014 11:13:28 GMT) :
>> tailsgnuli...@gmail.com:
>>> I have set up a new Tor mirror. It is located in the United
>>> States. The url is http://tor.mirrors.tailsgnulinux.org/.
>
>> S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/15/2014 12:25 AM, intrigeri wrote:
> winterfa...@riseup.net wrote (14 Feb 2014 15:05:56 GMT) :
>> Electrum sounds interesting, if we want a Bitcoin client in
>> Tails.
>
> At least, anyone who has been doing some Tails user support knows
> for su
20 matches
Mail list logo
