Renamed the Signpath blog post for clarity

justinclift · justinclift · commit 724bb4958bdf · 2024-11-11T21:58:37.000+10:00
diff --git a/content/blog/2024-11-08-our-journey-with-signpath.md b/content/blog/2024-11-08-our-journey-with-signpath.md
@@ -1,8 +1,8 @@
 ---
-title: Our journey with SignPath
+title: Signing Windows executables - Our journey with SignPath
 author: SeongTae Jeong
 date: '2024-11-08'
-slug: our-journey-with-signpath
+slug: signing-windows-executables-our-journey-with-signpath
 categories:
   - db4s
 tags:
diff --git a/docs/blog/index.html b/docs/blog/index.html
@@ -68,7 +68,7 @@
     <h2 class="archive-title">2024</h2>
     
     <article class="archive-item">
-      <a href="/blog/our-journey-with-signpath/" class="archive-item-link">Our journey with SignPath</a>
+      <a href="/blog/signing-windows-executables-our-journey-with-signpath/" class="archive-item-link">Signing Windows executables - Our journey with SignPath</a>
       <span class="archive-item-date">
         2024-11-08
       </span>
diff --git a/docs/blog/index.xml b/docs/blog/index.xml
@@ -8,11 +8,11 @@
     <language>en-us</language>
     <lastBuildDate>Fri, 08 Nov 2024 00:00:00 +0000</lastBuildDate><atom:link href="/blog/index.xml" rel="self" type="application/rss+xml" />
     <item>
-      <title>Our journey with SignPath</title>
-      <link>/blog/our-journey-with-signpath/</link>
+      <title>Signing Windows executables - Our journey with SignPath</title>
+      <link>/blog/signing-windows-executables-our-journey-with-signpath/</link>
       <pubDate>Fri, 08 Nov 2024 00:00:00 +0000</pubDate>
       
-      <guid>/blog/our-journey-with-signpath/</guid>
+      <guid>/blog/signing-windows-executables-our-journey-with-signpath/</guid>
       <description>Our Journey with SignPath: Code Signing for Windows Binaries When distributing software, code signing is essential to ensure our users can trust the software they download, especially on an operating system like Windows that displays security warnings for unsigned software.
 So for us, code signing is not just an option, but a necessity to validate software binaries, prevent tampering, and for the convenience of our users.
 A Little Background on This Journey It&amp;rsquo;s not difficult to code sign and notarize software binaries for Apple macOS.</description>
diff --git a/docs/blog/signing-windows-executables-our-journey-with-signpath/index.html b/docs/blog/signing-windows-executables-our-journey-with-signpath/index.html
@@ -6,8 +6,8 @@
 <meta name="generator" content="Hugo 0.111.3">
 
 
-<title>Our journey with SignPath - DB Browser for SQLite</title>
-<meta property="og:title" content="Our journey with SignPath - DB Browser for SQLite">
+<title>Signing Windows executables - Our journey with SignPath - DB Browser for SQLite</title>
+<meta property="og:title" content="Signing Windows executables - Our journey with SignPath - DB Browser for SQLite">
 
 
   <link href='/favicon.ico' rel='icon' type='image/x-icon'/>
@@ -65,7 +65,7 @@
     <span class="article-duration">2 min read</span>
     
 
-    <h1 class="article-title">Our journey with SignPath</h1>
+    <h1 class="article-title">Signing Windows executables - Our journey with SignPath</h1>
 
     
     <span class="article-date">2024-11-08</span>
diff --git a/docs/categories/db4s/index.html b/docs/categories/db4s/index.html
@@ -68,7 +68,7 @@
     <h2 class="archive-title">2024</h2>
     
     <article class="archive-item">
-      <a href="/blog/our-journey-with-signpath/" class="archive-item-link">Our journey with SignPath</a>
+      <a href="/blog/signing-windows-executables-our-journey-with-signpath/" class="archive-item-link">Signing Windows executables - Our journey with SignPath</a>
       <span class="archive-item-date">
         2024-11-08
       </span>
diff --git a/docs/categories/db4s/index.xml b/docs/categories/db4s/index.xml
@@ -8,11 +8,11 @@
     <language>en-us</language>
     <lastBuildDate>Fri, 08 Nov 2024 00:00:00 +0000</lastBuildDate><atom:link href="/categories/db4s/index.xml" rel="self" type="application/rss+xml" />
     <item>
-      <title>Our journey with SignPath</title>
-      <link>/blog/our-journey-with-signpath/</link>
+      <title>Signing Windows executables - Our journey with SignPath</title>
+      <link>/blog/signing-windows-executables-our-journey-with-signpath/</link>
       <pubDate>Fri, 08 Nov 2024 00:00:00 +0000</pubDate>
       
-      <guid>/blog/our-journey-with-signpath/</guid>
+      <guid>/blog/signing-windows-executables-our-journey-with-signpath/</guid>
       <description>Our Journey with SignPath: Code Signing for Windows Binaries When distributing software, code signing is essential to ensure our users can trust the software they download, especially on an operating system like Windows that displays security warnings for unsigned software.
 So for us, code signing is not just an option, but a necessity to validate software binaries, prevent tampering, and for the convenience of our users.
 A Little Background on This Journey It&amp;rsquo;s not difficult to code sign and notarize software binaries for Apple macOS.</description>
diff --git a/docs/index.html b/docs/index.html
@@ -121,7 +121,7 @@ <h2 id="windows-code-signing-policy">Windows Code-Signing Policy</h2>
     <h2 class="archive-title">2024</h2>
     
     <article class="archive-item">
-      <a href="/blog/our-journey-with-signpath/" class="archive-item-link">Our journey with SignPath</a>
+      <a href="/blog/signing-windows-executables-our-journey-with-signpath/" class="archive-item-link">Signing Windows executables - Our journey with SignPath</a>
       <span class="archive-item-date">
         2024-11-08
       </span>
diff --git a/docs/index.xml b/docs/index.xml
@@ -8,11 +8,11 @@
     <language>en-us</language>
     <lastBuildDate>Fri, 08 Nov 2024 00:00:00 +0000</lastBuildDate><atom:link href="/index.xml" rel="self" type="application/rss+xml" />
     <item>
-      <title>Our journey with SignPath</title>
-      <link>/blog/our-journey-with-signpath/</link>
+      <title>Signing Windows executables - Our journey with SignPath</title>
+      <link>/blog/signing-windows-executables-our-journey-with-signpath/</link>
       <pubDate>Fri, 08 Nov 2024 00:00:00 +0000</pubDate>
       
-      <guid>/blog/our-journey-with-signpath/</guid>
+      <guid>/blog/signing-windows-executables-our-journey-with-signpath/</guid>
       <description>Our Journey with SignPath: Code Signing for Windows Binaries When distributing software, code signing is essential to ensure our users can trust the software they download, especially on an operating system like Windows that displays security warnings for unsigned software.
 So for us, code signing is not just an option, but a necessity to validate software binaries, prevent tampering, and for the convenience of our users.
 A Little Background on This Journey It&amp;rsquo;s not difficult to code sign and notarize software binaries for Apple macOS.</description>
diff --git a/docs/sitemap.xml b/docs/sitemap.xml
@@ -14,7 +14,7 @@
     <loc>/categories/db4s/</loc>
     <lastmod>2024-11-08T00:00:00+00:00</lastmod>
   </url><url>
-    <loc>/blog/our-journey-with-signpath/</loc>
+    <loc>/blog/signing-windows-executables-our-journey-with-signpath/</loc>
     <lastmod>2024-11-08T00:00:00+00:00</lastmod>
   </url><url>
     <loc>/tags/signpath/</loc>
diff --git a/docs/tags/signpath/index.html b/docs/tags/signpath/index.html
@@ -68,7 +68,7 @@
     <h2 class="archive-title">2024</h2>
     
     <article class="archive-item">
-      <a href="/blog/our-journey-with-signpath/" class="archive-item-link">Our journey with SignPath</a>
+      <a href="/blog/signing-windows-executables-our-journey-with-signpath/" class="archive-item-link">Signing Windows executables - Our journey with SignPath</a>
       <span class="archive-item-date">
         2024-11-08
       </span>
diff --git a/docs/tags/signpath/index.xml b/docs/tags/signpath/index.xml
@@ -8,11 +8,11 @@
     <language>en-us</language>
     <lastBuildDate>Fri, 08 Nov 2024 00:00:00 +0000</lastBuildDate><atom:link href="/tags/signpath/index.xml" rel="self" type="application/rss+xml" />
     <item>
-      <title>Our journey with SignPath</title>
-      <link>/blog/our-journey-with-signpath/</link>
+      <title>Signing Windows executables - Our journey with SignPath</title>
+      <link>/blog/signing-windows-executables-our-journey-with-signpath/</link>
       <pubDate>Fri, 08 Nov 2024 00:00:00 +0000</pubDate>
       
-      <guid>/blog/our-journey-with-signpath/</guid>
+      <guid>/blog/signing-windows-executables-our-journey-with-signpath/</guid>
       <description>Our Journey with SignPath: Code Signing for Windows Binaries When distributing software, code signing is essential to ensure our users can trust the software they download, especially on an operating system like Windows that displays security warnings for unsigned software.
 So for us, code signing is not just an option, but a necessity to validate software binaries, prevent tampering, and for the convenience of our users.
 A Little Background on This Journey It&amp;rsquo;s not difficult to code sign and notarize software binaries for Apple macOS.</description>
diff --git a/docs/tags/windows/index.html b/docs/tags/windows/index.html
@@ -68,7 +68,7 @@
     <h2 class="archive-title">2024</h2>
     
     <article class="archive-item">
-      <a href="/blog/our-journey-with-signpath/" class="archive-item-link">Our journey with SignPath</a>
+      <a href="/blog/signing-windows-executables-our-journey-with-signpath/" class="archive-item-link">Signing Windows executables - Our journey with SignPath</a>
       <span class="archive-item-date">
         2024-11-08
       </span>
diff --git a/docs/tags/windows/index.xml b/docs/tags/windows/index.xml
@@ -8,11 +8,11 @@
     <language>en-us</language>
     <lastBuildDate>Fri, 08 Nov 2024 00:00:00 +0000</lastBuildDate><atom:link href="/tags/windows/index.xml" rel="self" type="application/rss+xml" />
     <item>
-      <title>Our journey with SignPath</title>
-      <link>/blog/our-journey-with-signpath/</link>
+      <title>Signing Windows executables - Our journey with SignPath</title>
+      <link>/blog/signing-windows-executables-our-journey-with-signpath/</link>
       <pubDate>Fri, 08 Nov 2024 00:00:00 +0000</pubDate>
       
-      <guid>/blog/our-journey-with-signpath/</guid>
+      <guid>/blog/signing-windows-executables-our-journey-with-signpath/</guid>
       <description>Our Journey with SignPath: Code Signing for Windows Binaries When distributing software, code signing is essential to ensure our users can trust the software they download, especially on an operating system like Windows that displays security warnings for unsigned software.
 So for us, code signing is not just an option, but a necessity to validate software binaries, prevent tampering, and for the convenience of our users.
 A Little Background on This Journey It&amp;rsquo;s not difficult to code sign and notarize software binaries for Apple macOS.</description>
