Closed anibal-acosta closed 5 years ago
makes sense, and btw, there could be other programs that write to the well-known directory, for other reasons than ACME support. see commit b3a488f3f116621280594682ceada179823acd29
would it make sense to add the possibility to include an arbitrary web.config? WinCertes generates one, but from your case i understand it might be not enough
In my case, the whole site is protected with asp.net forms authentication. So and cannot exclude well-known directory because has a dot ".well-known" in the beginning. So the solution was convert the ".well-known" to IIS application and add the web.config in root to allow anonymous access.
Can you please test this for both bugs. WinCertes-Debug.1.1.0.100.msi.zip
I download the source from github and for some reason this doesnt work, the console just show:
[DEBUG] PFX password will be: 6f832f86286141c3 [DEBUG] Current certificate expiration date is: And then terminate.
I ran the previous version and the process completes with success
El vie., 1 feb. 2019 a las 11:34, Alexandre Aufrere (< notifications@github.com>) escribió:
Can you please test this for both bugs. WinCertes-Debug.1.1.0.100.msi.zip https://github.com/aloopkin/WinCertes/files/2822006/WinCertes-Debug.1.1.0.100.msi.zip
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/aloopkin/WinCertes/issues/11#issuecomment-459741945, or mute the thread https://github.com/notifications/unsubscribe-auth/AcW4xQCbxAk6O3MyzYozaGf6d1gx2Kq4ks5vJFB8gaJpZM4aLgpm .
In this beta version, either -w (use existing web server) or -a (spawn built-in web server) must be set on the command line. I just made a change to clarify this. Overall, it is due to the addition of DNS validation methods.
fixed in version 1.1.1
I need to set a web.config in the .well-known directory to avoid forms authentication redirect. So, I need to keep this directory.
When WinCertes finish, try to cleanup those directories and got error because this is not empty
Maybe the solution is to delete only directories that WinCertes effective created in the process and not those already exists