Moderators: Quade, dexter, newsraider, DThor
Works fine under Mint 11/64bit/G2 Wine 1.4.
Anybody got any ideas?
Not a problem, but I must admit I'm mystified how the openssl can cause the problem when Newsbin doesn't even use it.
SSL Connection Failed: 5 Error 0 Success.
workaround is to add to /etc/postfix/main.cf
smtpd_tls_exclude_ciphers = RC4-MD5
fixme:wininet:INET_QueryOption INTERNET_OPTION_CONNECTED_STATE: semi-stub
fixme:wininet:InternetAttemptConnect Stub
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT
(60000): STUB
fixme:wininet:InternetSetOptionW
INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 60000
fixme:wininet:InternetSetOptionW
INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 300000
err:wininet:NETCON_secure_connect SSL_connect failed: 12157
Last message was generated in dlls/wininet/netconnection.c:
fixme:wininet:query_global_option INTERNET_OPTION_SECURITY_FLAGS: Stub
fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_SECURITY_FLAGS; STUB
err:wininet:HTTP_ParseDateAsAsctime unexpected weekday L"133"
err:wininet:HTTP_ParseDate unexpected date format L"1339699522"
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixme:ieframe:WebBrowser_Stop (0xb4de0)
fixme:ieframe:OleInPlaceObject_InPlaceDeactivate (0xb4de0)
fixme:heap:HeapSetInformation 0x1365000 0 0x23e900 4
fixme:heap:HeapSetInformation 0x1475000 0 0x23e960 4
Seems there is a kernel bug with the LTS 12.04 release of Ubuntu. I was able to register and download via SSL by performing the following:
echo 0|sudo tee /proc/sys/kernel/yama/ptrace_scope
This solution was found at:
http://www.codeweavers.com/support/wiki ... ubuntu1204
# The PTRACE system is used for debugging. With it, a single user process
# can attach to any other dumpable process owned by the same user. In the
# case of malicious software, it is possible to use PTRACE to access
# credentials that exist in memory (re-using existing SSH connections,
# extracting GPG agent information, etc).
#
# A PTRACE scope of "0" is the more permissive mode. A scope of "1" limits
# PTRACE only to direct child processes (e.g. "gdb name-of-program" and
# "strace -f name-of-program" work, but gdb's "attach" and "strace -fp $PID"
# do not). The PTRACE scope is ignored when a user has CAP_SYS_PTRACE, so
# "sudo strace -fp $PID" will work as before. For more details see:
# https://wiki.ubuntu.com/SecurityTeam/Ro ... ing#ptrace
#
# For applications launching crash handlers that need PTRACE, exceptions can
# be registered by the debugee by declaring in the segfault handler
# specifically which process will be using PTRACE on the debugee:
# prctl(PR_SET_PTRACER, debugger_pid, 0, 0, 0);
#
# In general, PTRACE is not needed for the average running Ubuntu system.
# To that end, the default is to set the PTRACE scope to "1". This value
# may not be appropriate for developers or servers with only admin accounts.
Users browsing this forum: Bing [Bot] and 2 guests