In condizioni base le custom ROM aftermarket (NO cert/support OEM) NON passano obv né GPI device/strong né HW_attestation in enforced verified.
Ecco perché e.g. GrapheneOS propone a sviluppatori app di "whitelistare" le sue chiavi, impostando OK HW_attestation pure per SelfSigned...
⬇️5/6
Ecco perché e.g. GrapheneOS propone a sviluppatori app di "whitelistare" le sue chiavi, impostando OK HW_attestation pure per SelfSigned...
⬇️5/6
July 28, 2025 at 8:12 PM
In condizioni base le custom ROM aftermarket (NO cert/support OEM) NON passano obv né GPI device/strong né HW_attestation in enforced verified.
Ecco perché e.g. GrapheneOS propone a sviluppatori app di "whitelistare" le sue chiavi, impostando OK HW_attestation pure per SelfSigned...
⬇️5/6
Ecco perché e.g. GrapheneOS propone a sviluppatori app di "whitelistare" le sue chiavi, impostando OK HW_attestation pure per SelfSigned...
⬇️5/6
Okay! Finally got the solution.
I had to:
-install a leaked windows 10 ARM7
build on the Surface RT
- enable dev mode
-by hand install a selfsigned cert
- Install the appx via power shell
All because Microsoft turned off the Dev License servers for Win8 last year.
I had to:
-install a leaked windows 10 ARM7
build on the Surface RT
- enable dev mode
-by hand install a selfsigned cert
- Install the appx via power shell
All because Microsoft turned off the Dev License servers for Win8 last year.
Developing windows 8 applications is insanely frustrating in 2024.
- Microsoft turned off the server to obtain developer licenses in late 2023 which is required for sideloading
- there currently is no way to run APPXes
- while a jailbreak exists to run unsigned ARM binaries, you can't run built...
- Microsoft turned off the server to obtain developer licenses in late 2023 which is required for sideloading
- there currently is no way to run APPXes
- while a jailbreak exists to run unsigned ARM binaries, you can't run built...
November 8, 2024 at 12:34 PM
Okay! Finally got the solution.
I had to:
-install a leaked windows 10 ARM7
build on the Surface RT
- enable dev mode
-by hand install a selfsigned cert
- Install the appx via power shell
All because Microsoft turned off the Dev License servers for Win8 last year.
I had to:
-install a leaked windows 10 ARM7
build on the Surface RT
- enable dev mode
-by hand install a selfsigned cert
- Install the appx via power shell
All because Microsoft turned off the Dev License servers for Win8 last year.
Danke für den Link. Hat sehr geholfen. Der hat mir neue Infos gegeben, so dass ich es jetzt per hostname und ssl hinbekommen habe. Nun habe ich noch Probleme mit dem selfsigned certificate.
July 25, 2025 at 8:40 PM
Danke für den Link. Hat sehr geholfen. Der hat mir neue Infos gegeben, so dass ich es jetzt per hostname und ssl hinbekommen habe. Nun habe ich noch Probleme mit dem selfsigned certificate.
(i needed to use the selfsigned cert or else the host would be different and the signatures would be wrong and id need to recalculate them which would be difficult to do with Just nginx)
November 15, 2024 at 1:18 AM
(i needed to use the selfsigned cert or else the host would be different and the signatures would be wrong and id need to recalculate them which would be difficult to do with Just nginx)
#Windows #ProtectedEventLogging suits businesses & personal devices. Requires generating #TrustedCertificate into the #CertificateStore. #Create #SelfSigned #certificates on #WindowsHome edition in #PowerShell w/ #Admin #Privileges. #TechSupport #ITpro @computers8networks.bsky.social tr.ee/wim7nV
Premium IT Services | Computers And Networks
We C.A.N. help you with computer, network and cybersecurity needs
tr.ee
July 7, 2025 at 2:11 AM
#Windows #ProtectedEventLogging suits businesses & personal devices. Requires generating #TrustedCertificate into the #CertificateStore. #Create #SelfSigned #certificates on #WindowsHome edition in #PowerShell w/ #Admin #Privileges. #TechSupport #ITpro @computers8networks.bsky.social tr.ee/wim7nV
one of my servers wont connect to jortage for some reason so i have an nginx proxy on a different server for it which is using a selfsigned cert that i added to the cert authority on the other server, lol lmao
maybe you could do some jank shit like that until theres a proper fix?
maybe you could do some jank shit like that until theres a proper fix?
November 15, 2024 at 1:17 AM
one of my servers wont connect to jortage for some reason so i have an nginx proxy on a different server for it which is using a selfsigned cert that i added to the cert authority on the other server, lol lmao
maybe you could do some jank shit like that until theres a proper fix?
maybe you could do some jank shit like that until theres a proper fix?
[Friday CVE Analysis Drop]
We tackled an interesting CVE, reverse engineering it to show how it works Despite many challenges including selfsigned certificates and brute-forcing with a Python script we completed a detailed analysis of PaperCut
#cybersecurity
blog.securelayer7.net/analysis-of-...
We tackled an interesting CVE, reverse engineering it to show how it works Despite many challenges including selfsigned certificates and brute-forcing with a Python script we completed a detailed analysis of PaperCut
#cybersecurity
blog.securelayer7.net/analysis-of-...
Analysis of CVE-2023-39143 – PaperCut RCE
Overview CVE-2023-39143 is a path traversal vulnerability found in Papercut MF/NG, a print management solution. This particular CVE only affects Windows installations prior to version 22.1.3. With...
blog.securelayer7.net
May 24, 2024 at 1:57 PM
[Friday CVE Analysis Drop]
We tackled an interesting CVE, reverse engineering it to show how it works Despite many challenges including selfsigned certificates and brute-forcing with a Python script we completed a detailed analysis of PaperCut
#cybersecurity
blog.securelayer7.net/analysis-of-...
We tackled an interesting CVE, reverse engineering it to show how it works Despite many challenges including selfsigned certificates and brute-forcing with a Python script we completed a detailed analysis of PaperCut
#cybersecurity
blog.securelayer7.net/analysis-of-...
• Set ES_HOST=https://localhost in .env.production
• Set ES_CA_FILE=/path/to/selfsigned/cert
(b) I had to carefully set the maximum Java heap size, even though I thought I had plenty of RAM.
This last point confused me for sometime. I am running ES on the same VPS as my mastodon instance, which
• Set ES_CA_FILE=/path/to/selfsigned/cert
(b) I had to carefully set the maximum Java heap size, even though I thought I had plenty of RAM.
This last point confused me for sometime. I am running ES on the same VPS as my mastodon instance, which
February 11, 2025 at 9:26 AM
• Set ES_HOST=https://localhost in .env.production
• Set ES_CA_FILE=/path/to/selfsigned/cert
(b) I had to carefully set the maximum Java heap size, even though I thought I had plenty of RAM.
This last point confused me for sometime. I am running ES on the same VPS as my mastodon instance, which
• Set ES_CA_FILE=/path/to/selfsigned/cert
(b) I had to carefully set the maximum Java heap size, even though I thought I had plenty of RAM.
This last point confused me for sometime. I am running ES on the same VPS as my mastodon instance, which
• Set ES_HOST=https://localhost in .env.production
• Set ES_CA_FILE=/path/to/selfsigned/cert
(b) I had to carefully set the maximum Java heap size, even though I thought I had plenty of RAM.
This last point confused me for sometime. I am running ES on the same VPS as my mastodon instance […]
• Set ES_CA_FILE=/path/to/selfsigned/cert
(b) I had to carefully set the maximum Java heap size, even though I thought I had plenty of RAM.
This last point confused me for sometime. I am running ES on the same VPS as my mastodon instance […]
Original post on colquitt.xyz
colquitt.xyz
February 11, 2025 at 9:21 AM
• Set ES_HOST=https://localhost in .env.production
• Set ES_CA_FILE=/path/to/selfsigned/cert
(b) I had to carefully set the maximum Java heap size, even though I thought I had plenty of RAM.
This last point confused me for sometime. I am running ES on the same VPS as my mastodon instance […]
• Set ES_CA_FILE=/path/to/selfsigned/cert
(b) I had to carefully set the maximum Java heap size, even though I thought I had plenty of RAM.
This last point confused me for sometime. I am running ES on the same VPS as my mastodon instance […]
SSL/TLS Zertifikate für die Nutzung im internen Netz (apache#ca #certificate #selfsigned #ssl #zertifikat
buff.ly/2PeOvnG
buff.ly/2PeOvnG
SSL/TLS Zertifikate für die Nutzung im internen Netz (apache)
Um verschiedene Dienste im LAN sicher zu nutzen, werden SSL-Zertifikate benötigt. Wir verwenden dafür in manchen Fällen ein selbstsigniertes Zertifikat. Das SSL-Zertifikat enthält Informationen über den Namen des Inhabers, den öffentlichen Schlüssel, eine Gültigkeitsdauer und gegebenenfalls den Namen der Zertifizierungsstelle. Mit dem öffentlichen Schlüssel kann das Zertifikat der Zertifizierungsstelle überprüft werden. Das SSL-Zertifikat muss zuerst als vertrauenswürdig eingestuft werden, dazu sind bestimmte Rangordnungen der Autoritäten notwendig. Der Browser verfügt über Listen mit Zertifizierungsstellen deren SSL-Zertifikate bedingungslos vertraut werden. Beim Aufrufen einer SSL-verschlüsselten Website, prüft der Browser das Zertifikat auf Gültigkeit der Referenzen und des Herausgebers der Webadresse. Kennt der PC oder Browser den Herausgeber des Zertifikates nicht, meldet er einen Zertifikatsfehler. Diesen Fehler kann man übergehen und seinen Besuch auf der Website fortsetzen. Selbstsignierte Zertifikate geben diesen Fehler logischerweise immer, da sie nicht von einer Zertifizierungsstelle als gültig und sicher geprüft wurden. Hier signiert der Server selbst für seine Dienste, die von den jeweiligen Clients besucht werden. Ich zeige euch, wie wir das Zertifikat erstellen und manuell in den Firefox-Browser hinterlegen. Zuerst müssen wir einen Private-Key erstellen, der immer bei uns verbleibt. Niemand außer uns sollte Zugriff auf diese Datei haben, da der Private-Key später untrennbar von unserem Zertifikat ist. […]
buff.ly
February 26, 2025 at 3:40 AM
SSL/TLS Zertifikate für die Nutzung im internen Netz (apache#ca #certificate #selfsigned #ssl #zertifikat
buff.ly/2PeOvnG
buff.ly/2PeOvnG
Hello ! Je ne suis pas sûr mais un post sur stackoverflow d'il y a 2 ans semble indiquer que *.localhost est refusé par les navigateurs ?
stackoverflow.com/questions/68...
stackoverflow.com/questions/68...
What is the correct way to generate a selfsigned cert for *.localhost ('wildcard')
I can't for the life of me get chrome to work with a wildcard cert ("*.localhost")
Here is what I'm doing to generate said cert.
First I gen my ca
openssl genrsa -out priv/cert/ca.key 2048
stackoverflow.com
April 15, 2024 at 4:53 PM
Hello ! Je ne suis pas sûr mais un post sur stackoverflow d'il y a 2 ans semble indiquer que *.localhost est refusé par les navigateurs ?
stackoverflow.com/questions/68...
stackoverflow.com/questions/68...
"Developing locally with http://ASP.NET Core under HTTPS, SSL, and Self-Signed Certs" http://feeds.hanselman.com/~/562584530/0/scotthanselman~Developing-locally-with-ASPNET-Core-under-HTTPS-SSL-and-SelfSigned-Certs.aspx #dev #feedly
December 15, 2024 at 9:27 PM
"Developing locally with http://ASP.NET Core under HTTPS, SSL, and Self-Signed Certs" http://feeds.hanselman.com/~/562584530/0/scotthanselman~Developing-locally-with-ASPNET-Core-under-HTTPS-SSL-and-SelfSigned-Certs.aspx #dev #feedly
SelfSigned
cert-manager configuration: SelfSigned Issuers
cert-manager.io
December 21, 2024 at 6:26 AM
Die Aufregung um #selfsigned Zertifikate in der #ITSecurityIndustrie ist jedes Mal wieder amüsant. Ich persönlich vertraue meiner eigenen #rootCA blind – mehr als jedem undurchsichtigen, kommerziellen #SSL-Anbieter.
July 10, 2025 at 7:23 AM
Die Aufregung um #selfsigned Zertifikate in der #ITSecurityIndustrie ist jedes Mal wieder amüsant. Ich persönlich vertraue meiner eigenen #rootCA blind – mehr als jedem undurchsichtigen, kommerziellen #SSL-Anbieter.