Am 24.10.2013 um 09:02 schrieb Tobias Oberstein :
>> I just tried to register so I could do that. When I clicked on the register
>> button
>> after filling out the username/password fields my browser (firefox) brought
>> up a notice that the security certificate is invalid because of unavailable
Am 24.10.2013 um 08:08 schrieb Daniel Sank :
> When I clicked on the
> register button after filling out the username/password fields my
> browser (firefox) brought up a notice that the security certificate is
> invalid because of unavailable issuance chain information. Knowing
> absolutely nothin
Ah, right. Seems Chrome changed it's behavior .. at one point it wasn't able to
load intermediate certs .. and hence I assumed from the dialog that Twisted
cert has the intermediate cert contained. Wrong.
FWIW, you can manually concatenate certs .. this is what we do (also for
StartSSL):
$
Am 24.10.2013 um 09:48 schrieb Tobias Oberstein :
> FWIW, you can manually concatenate certs .. this is what we do (also for
> StartSSL):
>
>$ cat myserver_plain_cert.crt > myserver.crt
>$ cat ../sub.class1.server.sha2.ca.pem >> myserver.crt
>$ cat ../ca.pem >> myserver.crt
>
> A co
> > A concatenated cert like above works today without the new code that is
> upcoming in Twisted. Which is cool also.
>
> That is completely new to me. Are you sure you're not mixing up Twisted's
> behavior with nginx?
>
> If what you say is true, there would have never been the need for #2061 a
>
> On 03:46 pm, grindi...@gmail.com wrote:
> >Hi everybody
> >
> >I a came across a surprising problem when using the epoll based
> >reactor.
> >(ticket here https://twistedmatrix.com/trac/ticket/6796)
> >
> >As you can see on the ticket, the epoll object seems to share some
> >state
> >even after
> > 2. Arrange for the epoll object (or FD) to be closed after fork, but
> > before exec, so that the child process can't fiddle with it
>
> See also:
>
> http://bugs.python.org/issue8713
>
> ...which suggests Python 3.4 added fork+exec support to multiprocessing.
> On Unix and older Python versi
Am 24.10.2013 um 11:10 schrieb Tobias Oberstein :
>>> A concatenated cert like above works today without the new code that is
>> upcoming in Twisted. Which is cool also.
>>
>> That is completely new to me. Are you sure you're not mixing up Twisted's
>> behavior with nginx?
>>
>> If what you say
> Your server definitely sends three certificates - that's surprising/confusing.
>
> Could you double-check how you've achieved that? If you google for chain
> certs & Twisted you'll find all kinds of monkey patches to achieve that; and
> when I run twistd -n web with a pem that has multiple certi
Am 24.10.2013 um 12:44 schrieb Tobias Oberstein :
>> Your server definitely sends three certificates - that's
>> surprising/confusing.
>>
>> Could you double-check how you've achieved that? If you google for chain
>> certs & Twisted you'll find all kinds of monkey patches to achieve that; and
>
On 10/23/2013 12:50 PM, Phil Mayers wrote:
This is a multiprocessing bug IMHO.
This issue with multiprocessing appears in other places too. E.g. if
you're using stdlib logging, child processes will try to rotate the
parent process logs.
Basically multiprocessing on Unix is utterly broken a
On 11:19 am, ita...@itamarst.org wrote:
On 10/23/2013 12:50 PM, Phil Mayers wrote:
This is a multiprocessing bug IMHO.
This issue with multiprocessing appears in other places too. E.g. if
you're using stdlib logging, child processes will try to rotate the
parent process logs.
Basically mu
maybe the mailing list disallows >2 attachments .. again:
http://picpaste.com/pics/step1-NB1LoEVR.1382620207.png
http://picpaste.com/pics/step2-6zVhXeE6.1382620274.png
http://picpaste.com/pics/step3-KTao4B2V.1382620308.png
-Ursprüngliche Nachricht-
Von: Tobias Oberstein
Gesendet: Donner
>
> To expand on that just a bit, the form of sharing that you get when you
> fork() but you don't exec() is very difficult to use correctly (I think
> it's an open question whether it's *possible* to use correctly in a Python
> program).
>
> The argument here is similar to the argument against sha
On Oct 24, 2013, at 12:48 AM, Tobias Oberstein
wrote:
> However: this all does not explain (at least I dont understand) why the OP
> has that issue showing up .. Firefox is able to load intermediate CA certs
> from the net .. I have seen it .. also for StartSSL certs. Something is
> breaking
On 10/23/13 7:30 PM, David Bolen wrote:
Lloyd Carothers writes:
For such a use case I'm surprised not to find an example. I think I
just need a push in the right direction. Is producers/consumers the
right approach?
It's a bit dated at this point, but maybe this might spark some ideas:
Hi everyone,
I've yet to hear back from anyone testing the prerelease - if you're
able to, please do!
Especially of interest to be tested would be the new HostnameEndpoint,
which tries to connect to both the IPv4 and IPv6 addresses from a DNS
lookup, and uses whichever is first - it makes Gl
> That will atomically combine the propagation of initial state with the
> provision of the
> back-propagation channel for updates to that state.
My understanding of Cacheable is that it propagates initial state to
the RemoteCache and then sends subsequent updates also to the
RemoteCache. What I
18 matches
Mail list logo
