search for: scoundrels

...yeah, whatever you feel like doing. go ahead.' > User interface decisions are never driven by security. If security is mentioned then it is used as a fig-leaf to shut down dissent. Security when applied to these sorts of decisions is the patriotism of the FOSS world. The last refuge of scoundrels who have no desire to admit error and wish no discomfort from making any. The actual reasons for change usually come down to the aesthetic values of a small group of developers, or often a single individual, with the power to impose their vision on the rest of humanity. And the desire to do so....

...eel like doing. go ahead.' > User interface decisions are never driven by security. If security is > mentioned then it is used as a fig-leaf to shut down dissent. > > Security when applied to these sorts of decisions is the patriotism of > the FOSS world. The last refuge of scoundrels who have no desire to > admit error and wish no discomfort from making any. > > The actual reasons for change usually come down to the aesthetic > values of a small group of developers, or often a single individual, > with the power to impose their vision on the rest of humanity. A...

We''ve gotten several reports on #merb that each request gets a new session ID in 0.4.0. I quickly tested and verified. scoundrel tracked it down, and I think it''s fixed. If you need to apply this by hand to your 0.4.0 install, it''s a 1 line fix: Index: /trunk/lib/merb/controller.rb =================================================================== ---

We have an Asterisk server that speaks IAX2 to Magrathea to get to the PSTN. Our local phones are a mix of Cisco 7940s and Grandstream BT100s all configured for SIP with silence-suppression disabled. Everything is configured to use a-law encoding. The version is: sip*CLI> show version Asterisk CVS-05/06/04-18:45:57 built by root@sip on a i686 running Linux Incoming callers are complaining of

Vincent JARDIN <vincent.jardin at 6wind.com> writes: > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> In a first prototype i implemented a ivshmem[2] device for the >> hypervisor. That way we can share memory between virtual machines. >> Ivshmem is nice and simple but does not seem to be used anymore. >> And it >> does not define higher level devices,

Vincent JARDIN <vincent.jardin at 6wind.com> writes: > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> In a first prototype i implemented a ivshmem[2] device for the >> hypervisor. That way we can share memory between virtual machines. >> Ivshmem is nice and simple but does not seem to be used anymore. >> And it >> does not define higher level devices,

Henning Schild <henning.schild at siemens.com> writes: > On Thu, 12 Jun 2014 08:48:04 +0200 > Markus Armbruster <armbru at redhat.com> wrote: > >> Vincent JARDIN <vincent.jardin at 6wind.com> writes: >> >> > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> >> In a first prototype i implemented a ivshmem[2] device for the >>

Henning Schild <henning.schild at siemens.com> writes: > On Thu, 12 Jun 2014 08:48:04 +0200 > Markus Armbruster <armbru at redhat.com> wrote: > >> Vincent JARDIN <vincent.jardin at 6wind.com> writes: >> >> > On 10/06/2014 18:48, Henning Schild wrote:> Hi, >> >> In a first prototype i implemented a ivshmem[2] device for the >>