self-signed | Signed provides a working example | TLS library

I'm trying to port the file_serving example to use HTTPS.

I've attempted to move the spiff file server functionality to the existing https_server example inside esp-idf but I get the error: httpd_server_init: error in creating ctrl socket (112)

I realize that this is probably not the easiest way to do it and instead I should work on re-writing the original file_serving example code to use https instead. The function to start the server is in the file_server.c:

I have a fresh install of Visual Studio Community 2019 on a new computer. I started a web app project, ran it for the first time, and then when prompted to accept the self-signed certificate I somehow managed to click "Do Not Ask Again" and "No".

At this point, when running the web app, I get a ERR_CONNECTION_RESET and can't connect to anything. I've tried deleting and recreating the certificate using advice listed here: Re-Installing Visual Studio 2017 Localhost Certificate, as well as reinstalling VS entirely, but neither worked.

To be clear, I messed up, not Visual Studio. As far as I can tell, there's nothing particular about my set up or environment, and I've built web apps in Visual Studio before, I just clicked the wrong things this time and am trying to undo that without factory resetting this entire PC.

Does anyone have any idea how I can trigger that original prompt in Visual Studio and get a properly signed certificate to run a web application?

[SOLVED]

I have an application that uses Blazor and Docker that can run in multiple modes for multiple customers (loading various configurations and modules). I use the Profile feature in Visual Studio 2019 to change the environment variables, that decide which version of the application to run.

As standard the Docker profile is the active one. When I run the application in this mode, it starts no problem and the development SSL certificate is valid.

I have created some new profiles (and belonging appsettings.*.json files) that I can select here

When I do select one of these profiles they load up fine and the application runs, but for some reason they won't reuse the same development certificate that was working when I am running it in the 'Docker' Profile. How do I fix this?

I have tried the following:

1. In the secrets.json i have tried to add a line like so: "Kestrel:Certificates:#####Staging:Password": "" () is the same number as the Kestrel:Certificates:Development:Password one, that already exists in the file, without any changes to the behavior.
2. From this URL: https://docs.microsoft.com/en-us/dotnet/core/additional-tools/self-signed-certificates-guide I have tried to create a new certificate by doing this: "dotnet dev-certs https -ep $env:USERPROFILE.aspnet\https\aspnetapp.pfx -p crypticpassword" in the terminal (in VS). I switched USERPROFILE to the name of the environment variable, and crypticpassword to a new random guid. It said it already had a valid certificate.

• Do I have to generate a certificate per profile?
• Can I reuse the one that is already working for 'Docker'?
• How is this done?

I'm trying to access my web application served using the webpack DevServer from a virtual machine, but I'm able to connect through HTTPS only to the main URL - all sub-URLs fail with ERR_SSL_PROTOCOL_ERROR error.

I'm running webpack DevServer on a host machine with macOS. My virtual machine is running Windows 10 (VMware Fusion in bridged network mode). Webpack DevServer uses custom self-signed SSL certificates (generated using the mkcert tool).

Here is my DevServer configuration (@angular-builders/custom-webpack:dev-server):

since a week I am trying to create android app bundle from a flutter app and I've followed from Create an upload keystore given official flutter website

in Mac OS I've tried following command in terminal

I'm trying to connect two node.js servers via websocket using the ws package. Here is some code:

Client server:

i am trying to build a IOS IPA for generic device, followed all the instructions, added signing certificates, team etc. but i am unable to build the product. any one please help me to resolve this issue.

here is my signing config. checked to automatically managed. added device in developer site.

sent 435785657 bytes received 92 bytes 58104766.53 bytes/sec total size is 435732165 speedup is 1.00 Warning: unable to build chain to self-signed root for signer "Apple Development: ********" /Users/Saif/Library/Developer/Xcode/DerivedData/Runner-bemaxobcrmqabgcgltuauohrwrje/Build/Intermediates.noindex/ArchiveIntermediates/Runner/InstallationBuildProductsLocation/Applications/myapp.app/Frameworks/App.framework/App: errSecInternalComponent Command PhaseScriptExecution failed with a nonzero exit code

i am just stuck on this error for about 3 days. tried each and every solution available on stackoverflow and apple developer stack.

Flutter : 2.0.1 Xcode : 11.2.1

I want to create a simple TLS 1.3 server socket listener, which uses a self-signed certificate.

First I created a RSA public / private key pair:

We are connecting to IBM MQ from Java client we have successfully established the connection when sslauth is set to optional SSLCAUTH(OPTIONAL). But when we change it to required SSLCAUTH(REQUIRED) we are getting

AMQ9637E: During handshake, the remote partner sent no certificate

I have checked below link

Connecting to a Websphere MQ in Java with SSL/Keystore

T.Rob's answer mentions about "the QMgr must have your application's self-signed cert or a CA root cert that signed your app's cert in its keystore"

and below link

.Net and IBM MQ Managed connection SSL using pfx ca cert

which exactly quotes the exception/error that we are getting at Server / Queue Manager's end.(During handshake, the remote partner sent no certificate.)

As quoted by Daniel in one the comment of above answer "the MQ server needs all the CA certs of your certificate". I feel this may be issue in my case too.

My question is

In response section for AMQ9637E in IBM doc's

https://www.ibm.com/docs/en/ibm-mq/9.0?topic=multiplatforms-amq9xxx-remote

It is mentioned that "Look at the key repository on the remote side of this channel, and make sure the appropriate certificates are present, with correct labels.".

Here I am not very much sure about what labels is referring to is it referring to Alias name that we have given to certificate ?