How does Chrome proceed after "SSL alert number 46"? - google-chrome

Say, you have a webserver that you access with Chrome.
The webserver does not provide a valid certificate, so Chrome will show up the warning:
In addition, the server receives an alert which indicates this error back to the server:
error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown
This alert is fatal for the connection, so the server closes it down.
But does anyone know how the exact behavior is after you click Advanced → Proceed to localhost? I'd expect that the error message sslv3 alert certificate unknown is no longer sent by the browser, but I can see spot it in the server's traces. This error leads to closing of the connection. However, not all connections seem to be closed: the website is loaded properly.
Is there a fall-back such as "use only 1 TCP connection for this server" or the like? What does Chrome exactly do after you accept the risk?
I'm not interested in fixing the certificate errors. I just want to know what does exactly happen between client and server after you hit Proceed to localhost.

Related

Google Chrome: Failed to load resource: the server responded with a status of 407 (Proxy Authentication Required)

I'm connecting to the internet using a Proxy server. I already set the manual proxy setup with my IP address and the port. Now the issue is when I'm browsing on the internet chrome requires proxy username and password. I remember my proxy username and password but to enter those the popup window is not popping up. In Console I have this error and browser window is keep refreshing continuously with blank window.
Is there any way I can give proxy server username and password from Chrome settings? This happens only in chrome non incognito mode. I tried with Incognito mode, it asks the proxy username and password and thereafter everything working perfectly,
Note: This was listed in 2009 as a bug but I didn't found any solution to this https://bugs.chromium.org/p/chromium/issues/detail?id=6666
Since there is no answer over the internet, I will post the way I solved the issue. Actually this is not the proper way to solve the issue but at least you can connect to the internet using this method.
Proxy authentication details are stored some ware in your chrome account which associated with your email. After struggling few hours, what I did was, login to the chrome with another email so here it wont affect the settings on the previous Gmail account. Thereafter it asks the proxy username and password.
Note: Don't click the Never button if dialogue box pops up and ask to store the username and password.
I hope this will help for someone in future.

Server Error in '/' Application. While trying to Access stackoverflow

I am writing this from my mobile, So I keep it short. After installing Avast Free Antivirus, I cannot open the Stackoverflow webpage anymore, I get the Error "Server Error in '/' Application. Runtime Error. Description: an Exception occurred while Processing your request.additonally, another Exception occured while executing the Custom Error Page for First Execution. The request has been Terminated. Help, i am a total web noob :(
I solved this by following this guide:
https://answers.microsoft.com/en-us/msoffice/forum/msoffice_o365admin-mso_other-mso_o365b/server-error-in-application-cleared-my/78b3a5d6-78d4-4c42-8a0f-638fae7c9fb7?auth=1
1.Open your browser (such as Chrome) -> use Ctrl +shift+ delete to clear all browser data again.
2.Go to Control Panel > User Accounts > Credential Manager > Windows Credentials > under Generic Credentials, remove all credentials.
3.Open Chrome and check the result again.
same problem happened!
Just use proxy ultrasurf extension! (Any other proxy also will work) No need to delete any certificates or credentials.
In case you delete any certificates or credentials it might cause some errors in future(some applications may crash).

Error when running with Fiddler4 and decrypting HTTPS alongside SSIS

I am currently using SSIS to connect to and transfer data from a Microsoft Project Online (Cloud-based) database to an on-prem SQL Server db. The issue is that the SSIS package executes as expected when not running Fiddler4.
While troubleshooting with MS techs, it has been requested we capture a Fiddler trace and decrypt HTTPS traffic. We were able to do this in months past, but as of late, it will cause the SSIS package to fail with the following error:
"Cannot acquire a managed connection from the run-time connection manager."
I have followed the instructions to remove certificates a few times, as well as a few other net suggestions, but still having the issue. We are at a point where MS cannot troubleshoot further unless I can capture a trace.
Full error:
Information: 0x4004300A at TimeSet, SSIS.Pipeline: Validation phase is beginning.
Error: 0xC020801F at TimeSet, OData Source [2]: Cannot acquire a managed connection from the run-time connection manager.
Error: 0xC0047017 at TimeSet, SSIS.Pipeline: OData Source failed validation and returned error code 0xC020801F.
Error: 0xC004700C at TimeSet, SSIS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at TimeSet: There were errors during task validation.
Thanks for any and all help!
Edit: Went through my CA store and saw that the FiddlerRoot was not part of the Trusted CA list. Attempted to explicitly import the CA certificate in my security store, but the cert is still not showing in the trusted list. The Cert is named (for some reason) DO_NOT_TRUST_FiddlerRoot. Could this be part of what I have been seeing if the CA is marked to not be trusted?
Stepping back a bit: The Fiddler root certificate is always called DO_NOT_TRUST_FiddlerRoot and its name has no impact on anything (other than what is shown in the UI).
Does Fiddler properly collect HTTPS traffic from your web browsers?
If so, there are several possible explanations for what's going on here, but the most likely is that the Fiddler root certificate isn't trusted by the process that is using the connection; by default, for instance, Fiddler only tries to trust the root certificate in the per-user certificate store, but sometimes things run in a different user account (e.g. a service account) and thus the root must be placed in the per-machine certificate store.
You can try the following:
In Fiddler’s Tools > Fiddler Options > HTTPS tab, click Export Root Certificate to Desktop.
Launch mmc.exe.
Click File > Add/Remove Snap-In.
Select the Certificates snap-in and press Add.
When prompted This snap-in will always manage certificates for: choose Computer Account
Click Local Computer, then Finish, then OK.
Open the Certificates (Local Computer) node.
Right-click the Trusted Root Certificate Authorities folder and choose All Tasks > Import.
Choose the file you exported in step #1 and import it.

Chrome error after hitting back to safety on the security page

So after i hit back when seeing the message on chrome saying that my connection isnt secure on a HTTPS
now i can not access this page on my network and can only access it on my vps... is there any way I can fix this i searched all over the web and im so blown cause now i can't access my own webpage..
PS: I have tried accessing the page on another computer on the same network and i get the same error message of ERR_CONNECTION_TIMED_OUT when ever i try to go to the page, and yes i have tryed connecting on another router and the page loads fine and is a live copy of the page. please help me
Your connection is not private
Attackers might be trying to steal your information from xxxxx.com (for example, passwords, messages, or credit cards).
Back to safety Hide advanced
This server could not prove that it is (website).com; its security certificate is from server1.(website).com. This may be caused by a misconfiguration or an attacker intercepting your connection.
Proceed to (website).com (unsafe)
NET::ERR_CERT_COMMON_NAME_INVALID

Refresh at Dartium raises a SocketException in websocket server

I've been testing websocket client and server with Dart. Basic concept comes from Seth Ladd's blog:
Server: http://blog.sethladd.com/2012/04/dart-server-supports-web-sockets.html
Client: http://blog.sethladd.com/2012/07/simple-dart-websocket-demo.html
Everything works as expected ie. server responds clients requests and if I open a new Dartium window both clients works. When I close a client window it closes related connection (onDone:).
If I hit the refresh-button in Dartium, server raises an exception and closes. The error code is: "SocketException: Write failed, (OS Error: server closed connection, errno 10053, address = 127.0.0.1, port = 8080".
Is this a bug or should I add some code somewhere? I can't find the place where this error comes from. The last message I can find by debuging is onDone: (same as when closing the client).
Could be releated to this issue. The comments mention that it should be fixed in next release on monday.