On Fri, Feb 14, 2014 at 02:45:06PM -0500, Michael Carbone wrote:
> On 02/14/2014 01:54 PM, Nathan Freitas wrote:
> > On 02/14/2014 12:06 PM, Jack Murphy wrote:
> >>
> >> I've considered buying an android smartphone, but I've held off in
> >> the past because the max password length was a crackable
14.02.2014 18:29, Rusty Bird:
> Sebastian G. :
>> 14.02.2014 15:12, Rusty Bird:
>>> 2. That data gets sent to corridor-helper-update, which atomically
>>> updates a Linux ipset (a list of IP-address:TCP-port entries accessible
>>> in constant time) named tor_relays.
>>
>> Atomically is anatomically
On 02/14/2014 01:54 PM, Nathan Freitas wrote:
> On 02/14/2014 12:06 PM, Jack Murphy wrote:
>>
>> I've considered buying an android smartphone, but I've held off in
>> the past because the max password length was a crackable mere 16
>> characters in length.
>>
>> Does anyone here who's running Jel
On 02/14/2014 12:06 PM, Jack Murphy wrote:
>
> I've considered buying an android smartphone, but I've held off in the past
> because the max password length was a crackable mere 16 characters in length.
>
> Does anyone here who's running Jelly Bean know what that max password length
> for devic
Sebastian G. :
> 14.02.2014 15:12, Rusty Bird:
>> 2. That data gets sent to corridor-helper-update, which atomically
>> updates a Linux ipset (a list of IP-address:TCP-port entries accessible
>> in constant time) named tor_relays.
>
> Atomically is anatomically acceptable, but automatically appear
Hi.
I've considered buying an android smartphone, but I've held off in the past
because the max password length was a crackable mere 16 characters in length.
Does anyone here who's running Jelly Bean know what that max password length
for device encryption is these days?
Thanks,
Jack
--
tor-t
Hi Patrick,
Patrick Schleizer:
> Do you know Whonix [0]?
I know the design, but haven't used it so far.
> What's the threat model here? As I understand, it's ensuring stream
> isolation for one workstation while another workstation is
> compromised.
The goal is to make each workstation (or even
14.02.2014 15:12, Rusty Bird:
> ## Principle of operation
>
> 1. Either run the corridor-data-consensus daemon script, which opens a
> Tor control connection and subscribes to NEWCONSENSUS events
> (announcements listing all public relays), or pipe any number of
> "Bridge" lines into corridor-data
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Rusty,
this is an interesting concept.
Do you know Whonix [0]? (Full disclosure: I am a maintainer of
Whonix.) It is an Isolating Proxy [1] with an additional Transparent
Proxy [2] (Anonymizing Middlebox), which can be optionally disabled.
Rust
https://github.com/rustybird/corridor - I sign all commits.
Now follows the README.md, but it's easier on the eyes at GitHub.
Rusty
**This is a very early release. HERE BE DRAGONS! Not affiliated with the
Tor Project.**
# corridor, a Tor traffic whitelisting gateway
There are several transpar
* on the Thu, Feb 13, 2014 at 08:21:26PM +0100, Andreas Krey wrote:
>> Given that today we have narrowband codecs and that over high-latency
>> channel we can pack several 20ms sample together easily (also in packets
>> of 100ms size to reduce the amount of packets/s), the effective overhead
>> o
11 matches
Mail list logo
