Derek Wilson jderekwil...@gmail.com added the comment:
Any chance this patch will be accepted (or at least reviewed) soon?
--
type: behavior - crash
versions: +Python 3.3, Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Derek Wilson jderekwil...@gmail.com added the comment:
This should be higher priority as one of the major benefits of the
multiprocessing module is remote process management in a completely transparent
manner. socket timeouts are very important in this context as blocking forever
waiting
Derek Wilson jderekwil...@gmail.com added the comment:
While having multiprocessing use a timeout would be great, I didn't really have
the time to fiddle with the c code.
Instead of using the socket timeout, I'm modifying all the sockets created by
the socket module to have no timeout
Derek Wilson jderekwil...@gmail.com added the comment:
I was wrong about exit behavior of a process that has put to a queue -- it
seems to behave as expected. i had been playing with a proxy to a queue rather
than a queue (to which, if you put, the process can exit right away because
Derek Wilson jderekwil...@gmail.com added the comment:
Thanks, Jim, here is an updated patch.
1) I feel like it is clearly not-a-feature. Currently 2.7 crashes if remote
managers are used and socket.setdefaulttimeout is anything other than None.
Crashing seems bad and all this does is keep
Derek Wilson added the comment:
Attached patch mentioning availability of md5 under FIPS compliance and the use
of OpenSSL algorithms when available and altering the initial example to use
sha1 instead of md5.
--
keywords: +patch
nosy: +Derek.Wilson
Added file: http://bugs.python.org
Changes by Derek Wilson jderekwil...@gmail.com:
--
nosy: +Derek.Wilson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18233
___
___
Python-bugs
Derek Wilson added the comment:
Custom cert validation may make sense in edge cases, so this looks interesting.
But I got here looking to file a bug on the returning empty dict from
SSLContext.getpeercert - I don't feel like that makes sense. Its not like a
peer cert doesn't exist just
New submission from Derek Wilson:
the ssl.get_server_certificate function is very useful for just requesting a
cert. It would also be very useful to have a parallel function, possibly
ssl.get_server_cert_chain that does the same thing except but provides a tuple
of PEM encoded certs
Derek Wilson added the comment:
very cool - i had seen a couple of those patches and they look good. Most of
what I asked for is implemented in supporting bits for those issues.
Is their anything you could use some help on? I'm very interested in seeing
better ssl support in python
Derek Wilson added the comment:
For ssl.match_hostname to work with this, you need to get the info dict first.
I've attached at patch for it.
--
nosy: +underrun
Added file:
http://bugs.python.org/file31047/ssl_pyx509cert_match_hostname_fix.patch
Derek Wilson added the comment:
actually, i suppose rather than change a bunch of existing functions/methods to
handle X509 certs it would make more sense to add new methods to the X509 cert
class (like match_hostname) so that old stuff doesn't break
New submission from Derek Wilson:
ssl.get_server_certificate does not allow advanced options like what ciphers to
use (for ssl2 for instance) or SNI for virtual hosts with multiple ssl sites on
one IP address.
Adding **kwargs enables any current and future SSLSocket options to be passed
New submission from Derek Wilson:
Escaping strings for serialization or display is a common problem. Currently,
in python3, in order to escape a sting, you need to do this:
'my\tstring'.encode('unicode_escape').decode('ascii')
This would give you a string that was represented like this:
'my
Derek Wilson added the comment:
using repr(x)[1:-1] is not safe for my use case as i need this for encoding and
decoding data. the deserialization of repr would be eval, and aside from the
security issues with that, if I strip the quotes off I can't reliably eval the
result and get back
Derek Wilson added the comment:
ast.literal_eval('%s' % e)
this doesn't work if you use the wrong quote. without introspecting the data in
e you can't reliably choose whether to use '%s' '%s' '%s' or
'''%s'''. which ones break (and break siliently) depend on the data.
e.encode().decode
New submission from Derek Wilson:
It is common when setting up a logger to create both a handler and a formatter.
Nice format strings make logging better. Like this:
fmt_string = %(asctime)s [%(levelname)-9s] %(name)s: %(message)s
We would use it like so:
from logging import getLogger
Derek Wilson added the comment:
e.encode('latin1', 'backslashreplace').decode('unicode-escape')
this works, but still the quotes are backslash escaped.
translate will do what i need for my use case, but it doesn't support streaming
for larger chunks of data.
it is nice
Derek Wilson added the comment:
dictConfig and fileConfig are nice for static needs, but when I want to quickly
enable a complex (but not complicated) logging flow I find it just as tedious
as the current situation with the direct API.
... as at the very least every handler would need
Derek Wilson added the comment:
Any update on this? Just so you can see what my work around is, I'll paste in
the code I'm using. The major issue I have with this is that performance
doesn't scale to large strings.
This is also a bytes-to-bytes or str-to-str encoding, because this is the type
Derek Wilson added the comment:
this would still be nice to have fixed ... any progress?
--
nosy: +underrun
versions: +Python 3.4, Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5715
Derek Wilson added the comment:
any thoughts on this? there's a lot of room for improvement in python ssl...
--
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18616
Derek Wilson added the comment:
I could really use this sooner than later... and sometimes having a
full-featured (or even secure) interface is not what you want.
Consider zmap and masscan etc and ssl mapping (similar to what the EFF did a
couple years back - https://www.eff.org/observatory
Derek Wilson added the comment:
could this be reconsidered for 3.5+? most of the legacy code that you were
worried about breaking would not port without tonnes of work anyway.
it would also be nice to modify quitter's repr actually exit (so you don't get
that ridiculously annoying Use exit
New submission from Derek Wilson:
calling exit() or quit() is actually very cumbersome especially as most other
commandline tools that have a command interface allow you to exit or quit by
typing exit or quit and not by calling a function.
if quitter's builtins are only available
Derek Wilson added the comment:
sslv2 should not be deprecated yet.
in the field of security research it is highly valuable to locate servers that
are still using sslv2 because it is a security risk.
i'm fine with making it not used by default, but there is no reason to remove
the capability
Derek Wilson added the comment:
It is worth noting that the do exist some domains that have been registered in
the past that work with IDNA2003 but not IDNA2008.
There definitely needs to be IDNA2008 support, for my use case I need to
attempt IDNA2008 and then fall back to IDNA2003.
When
New submission from Derek Wilson:
If I create an argument parser like:
parser = argparse.ArgumentParser()
parser.add_argument('somebytes', type=bytes, help='i want some bytes')
parser.parse_args()
the parse_args() call will raise an exception printing usage info indicating
that an invalid
Derek Wilson added the comment:
First off, +1 for this feature. It's not just for twisted, but anyone doing
anything with binary data (storage, compression, encryption and networking for
me) with python since 2.6 will very likely have been using .format for building
messages. I know I have
Derek Wilson added the comment:
sorry, terry's patch does handle padding - just with the caveats i listed
later. i should have removed that bullet.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue3982
Derek Wilson added the comment:
> It's not an ideal world. Sorry, but I think this change is too invasive to
> consider.
Obviously its not ideal, which is why my suggestion doesn't require intelligent
3rd party libraries and is explicitly not invasive. As I said in my previous
comment,
Derek Wilson added the comment:
Gregory - I'm glad that you're willing to consider this again. It still is a
constant issue for me, and .format with variable width fields in binary
protocols is so the right tool for the job. If there is anything I can do to
help get this added to 3.6 let me
New submission from Derek Wilson:
Issue #17618 introduced base85 options into the base64 module including b85 and
a85/adobe variants.
There has since been introduced a variant that is easier to work with
specifically as it avoids " ' \ characters which avoids quoting/escaping issues
Derek Wilson added the comment:
z85 avoids all of:
` \ " ' _ , ;
Backtick and semicolon increase the number of places that z85 can be used
without issue over b85. All of these might not be as big an issue in python
as in other tools/languages but interoperability would still be imp
Derek Wilson added the comment:
why the downgrade from security to enhancement and critical to high?
this is a significant issue that can impact everything from phishing to TLS
certificate domain validation and SNI.
--
___
Python tracker
<ht
35 matches
Mail list logo
