-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-08-27 07:22, Achim Patzner wrote:
> Am 25.08.2016 um 21:33 schrieb johnyju...@sigaint.org:
>
>> While it's a bit slower, I prefer booting from DVD, a read-only
>> medium.
>
> There are verifyably hardware-controlled (physical switch)
> unwr
On Saturday, August 27, 2016 at 2:49:52 PM UTC, johny...@sigaint.org wrote:
> >> Whether using an "isolating proxy" (multiple machines) or not, using a
> >> white-listing proxy like Corridor can help ensure all of your traffic
> >> passes through Tor (Entry Guard, at least).
> >>
> >
> > That's rig
>> Whether using an "isolating proxy" (multiple machines) or not, using a
>> white-listing proxy like Corridor can help ensure all of your traffic
>> passes through Tor (Entry Guard, at least).
>>
>
> That's right. Also, using Firefox with those extensions is *not* the same
> as
> using Tor Browser
> Am 25.08.2016 um 21:33 schrieb johnyju...@sigaint.org:
>
>> While it's a bit slower, I prefer booting from DVD, a read-only medium.
>
> There are verifyably hardware-controlled (physical switch) unwritable
> USB storage devices. A bit expensive but you can get one.
I might look into that, it wou
Am 25.08.2016 um 21:33 schrieb johnyju...@sigaint.org:
> While it's a bit slower, I prefer booting from DVD, a read-only medium.
There are verifyably hardware-controlled (physical switch) unwritable
USB storage devices. A bit expensive but you can get one.
Achim
--
You received this message b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-08-25 21:49, 3n7r0...@gmail.com wrote:
> On Thursday, August 25, 2016 at 7:34:01 PM UTC, johny...@sigaint.org
> wrote:
>> Setting up Tor and Firefox (with noscript, ssl observatory, adblocker) to
>> use it as a proxy is essentially the same
johnyju...@sigaint.org:
>
>> I just use Whonix within Qubes and I like it. I'm glad it comes out of
>> the box since 3.1
>
> I've retreated to only using Fedora. Setting up Tor and Firefox (with
> noscript, ssl observatory, adblocker) to use it as a proxy is essentially
> the same effect as Whon
On Thursday, August 25, 2016 at 7:34:01 PM UTC, johny...@sigaint.org wrote:
> Setting up Tor and Firefox (with
> noscript, ssl observatory, adblocker) to use it as a proxy is essentially
> the same effect as Whonix (or tbb). Even if tor/firefox are on the same
> vm rather than separated, you're be
> I am too paranoid for using tails other than the reccomended method (two
> usb drives updating each other - I have two pairs of three).
No aware of the two drive method. Is that just updating to the next
version from the previous version, onto another USB drive?
While it's a bit slower, I pref
On 08/25/2016 01:54 AM, johnyju...@sigaint.org wrote
> (Although accepting the password change on a Tor exit, and then refusing
> that on a non-Tor https: connection was rather weird. Would they silently
> fail a password change? Oh well, I won't stress over it, but will keep a
> close eye on thi
On 08/25/2016 01:54 AM, johnyju...@sigaint.org wrote
> (Although accepting the password change on a Tor exit, and then refusing
> that on a non-Tor https: connection was rather weird. Would they silently
> fail a password change? Oh well, I won't stress over it, but will keep a
> close eye on thi
> My guess is that Paypal is giving you a hard time just because of the
> tor exits you use to interact with their website.
Could be. At first I didn't see how/why, but I guess refusing a legit
password from what they judge as a dodgy IP address is a possibility.
(Although accepting the password
My guess is that Paypal is giving you a hard time just because of the
tor exits you use to interact with their website.
So it seems to me all that you are saying is really related to using tor
via sys-whonix or manually trough the traditional means.
The sigaint episode is easily explained through
>> When I returned home, I tried logging in again, but from a different VM.
>> Failed repeatedly. I figured I must have messed up the password. No
>> luck
>> trying other possibilities.
I'm still a bit suspicious that one of my VM's has been compromised. I
still saw password problems after rest
> When I returned home, I tried logging in again, but from a different VM.
> Failed repeatedly. I figured I must have messed up the password. No luck
> trying other possibilities.
Update: a signed message from SIGAINT indicating it was a system problem:
-BEGIN PGP SIGNED MESSAGE-
Hash:
15 matches
Mail list logo