Hi, I installed tails to USB and when I start it, I get problem with tor connections, here is copy/paste from controlpanel-messagelog-advanced:
Mar 16 17:58:46.091 [Notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686)
Mar 16 17:58:46.096 [Notice] Initialized libevent version 1.4.13-stable using method epoll. Good.
Mar 16 17:58:46.097 [Notice] Opening Socks listener on 127.0.0.1:9050
Mar 16 17:58:46.097 [Warning] /var/run/tor is not owned by this user (amnesia, 1000) but by debian-tor (106). Perhaps you are running Tor as the wrong user?
Mar 16 17:58:46.097 [Warning] Before Tor can create a control socket in "/var/run/tor/control", the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.)
Mar 16 17:58:46.097 [Notice] Closing partially-constructed listener Socks listener on 127.0.0.1:9050
Mar 16 17:58:46.097 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
Mar 16 17:58:46.097 [Error] Reading config failed--see warnings above.
Mar 16 17:58:46.091 [Notice] Tor v0.2.2.35 (git-73ff13ab3cc9570d). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686)
Mar 16 17:58:46.096 [Notice] Initialized libevent version 1.4.13-stable using method epoll. Good.
Mar 16 17:58:46.097 [Notice] Opening Socks listener on 127.0.0.1:9050
Mar 16 17:58:46.097 [Warning] /var/run/tor is not owned by this user (amnesia, 1000) but by debian-tor (106). Perhaps you are running Tor as the wrong user?
Mar 16 17:58:46.097 [Warning] Before Tor can create a control socket in "/var/run/tor/control", the directory "/var/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (On some Unix systems, anybody who can list a socket can conect to it, so Tor is being careful.)
Mar 16 17:58:46.097 [Notice] Closing partially-constructed listener Socks listener on 127.0.0.1:9050
Mar 16 17:58:46.097 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
Mar 16 17:58:46.097 [Error] Reading config failed--see warnings above.
> It looks like you tried to start Tor yourself, didn't you?
>
> Please report a bug [[as documented|doc/first_steps/report_a_bug]]
> so that we get the information we need to help you.
The kernel documentation reads (`debugging-via-ohci1394.txt`):
> The alternative firewire-ohci driver in drivers/firewire uses
> filtered physical DMA by default, which is more secure but not
> suitable for remote debugging. Compile the driver with
> `CONFIG_FIREWIRE_OHCI_REMOTE_DMA` [...] to get unfiltered
> physical DMA.
Given:
1. `CONFIG_FIREWIRE_OHCI_REMOTE_DMA` is not set in Debian's Linux 3.2.
1. Only the new FireWire stack (`firewire-ohci`) is shipped in
Debian's Linux 3.2.
... Tails seems to be immune from the physical memory attacks via
FireWire/DMA we know.
Resources
=========
* [Physical memory attacks via Firewire/DMA - Part 1: Overview and Mitigation (Update)](http://www.hermann-uwe.de/blog/physical-memory-attacks-via-firewire-dma-part-1-overview-and-mitigation)
* [Using physical DMA provided by OHCI-1394 FireWire controllers for debugging](http://feishare.com/debug/using-physical-dma-provided-by-ohci-1394-firewire-controllers-for-debugging)
As there are still many Apple PowerMac G3 and G4 computers running in the world and some companies do use them, too, support for this arcitecture would be a good thing. Maybe, a layered virtualization could solve this problem along with others.
> Closing as duplicate of [[todo/powerpc_support]].
Linux 3.2 adds a "Speaker" channel for some sound cards.
> That channel has been there since forever for some cards.
...
...
@@ -19,4 +17,12 @@ We need to patch `/usr/share/alsa/utils.sh` the same way alsa-utils
>> I'm the bug reporter, you set the "Speaker" volume as 80%. Doesn't this mean 80% master x 80% speaker = 64% total volume? If I didn't get it wrong it should be same for Headphones (80% x 80% = 64%). If so, please set the other channels at maximum and decrease the master if needed so we could change the volume only by controlling the master channel
>>Can anybody answer this?
>> Can anybody answer this?
>>> All such mixer levels are set to 80% in the initscript shipped by
>>> the alsa-utils Debian package. Hardware is wired in many
>>> "interesting" ways, that may or may not satisfy the equation
>>> you're guessing, so I doubt there's any better general setting.
>>> I suggest you talk to the maintainers of the alsa-utils Debian
>>> package if you want to contribute to improve this area of Debian
