<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Luke Hinds on Medium]]></title>
        <description><![CDATA[Stories by Luke Hinds on Medium]]></description>
        <link>https://medium.com/@lhinds?source=rss-3160f5b9f9f9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*97loEBs8HMUVMViIeYMgfw.jpeg</url>
            <title>Stories by Luke Hinds on Medium</title>
            <link>https://medium.com/@lhinds?source=rss-3160f5b9f9f9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:26:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lhinds/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Announcing SigstoreCon 2022!]]></title>
            <link>https://medium.com/sigstore/announcing-sigstorecon-2022-dad650d83802?source=rss-3160f5b9f9f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/dad650d83802</guid>
            <dc:creator><![CDATA[Luke Hinds]]></dc:creator>
            <pubDate>Tue, 02 Aug 2022 13:56:40 GMT</pubDate>
            <atom:updated>2022-08-02T13:56:40.097Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zPAnI2HUNtwOcsCJ" /></figure><p>We’re happy to announce the first-ever <a href="https://events.linuxfoundation.org/sigstorecon-north-america/">SigstoreCon</a> to help everyone accelerate how you secure the software supply chain. The one-day event will take place October 25, in Detroit Michigan, in co-location with <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/">KubeCon + CloudNativeCon North America</a>.</p><p>SigstoreCon is a vendor-neutral conference organized by the Sigstore community and focused on all things Sigstore.</p><h3>Why Participate?</h3><p>Sigstore is a standard for signing, verifying, and protecting software. Sigstore ensures that your software is all that it claims to be for developers and end users.</p><p>Building and distributing software that is secure throughout its entire lifecycle can be challenging, leaving many projects at risk or unprepared. Attacks and vulnerabilities can emerge at any step of the supply chain: from writing the software, to packaging and distributing to end users. Sigstore was developed to improve the integrity of the software supply chain, reducing the friction developers face in implementing security within their daily work. Open source communities and enterprise organizations are rapidly adopting Sigstore to support their security goals.</p><p><a href="https://www.sigstore.dev/">Learn more about Sigstore</a></p><h3>Call for Papers</h3><p>The call for papers is now open and will close on Friday, August 19.</p><p>SigstoreCon will be a vendor-neutral space dedicated to collaboration and learning, and is committed to a developer-first approach to software security.</p><p>Talks can be <a href="https://events.linuxfoundation.org/sigstorecon-north-america/program/cfp/">submitted on the event page</a>!</p><h3>Important Dates</h3><ul><li><strong>CFP Closes:</strong> Friday, August 19, 11:59 PM PST</li><li><strong>CFP Notifications: </strong>Monday, September 12, 2022</li><li><strong>Schedule Announcement: </strong>Tuesday, September 13, 2022</li><li><strong>Event Date: </strong>Tuesday, October 25</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dad650d83802" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sigstore/announcing-sigstorecon-2022-dad650d83802">Announcing SigstoreCon 2022!</a> was originally published in <a href="https://medium.com/sigstore">sigstore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[sigstore, blockchain vs transparency logs.]]></title>
            <link>https://medium.com/sigstore/sigstore-blockchain-vs-transparency-logs-d673ea41a9be?source=rss-3160f5b9f9f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/d673ea41a9be</guid>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[sigstore]]></category>
            <category><![CDATA[blockhain]]></category>
            <dc:creator><![CDATA[Luke Hinds]]></dc:creator>
            <pubDate>Mon, 30 May 2022 14:04:03 GMT</pubDate>
            <atom:updated>2022-05-30T14:04:03.409Z</atom:updated>
            <content:encoded><![CDATA[<p>Co-authored by Luke Hinds (Red Hat) and Prof Santiago Torres-Arias (Purdue University).</p><blockquote><strong>Disclaimer: </strong>The following is representative of the authors views, and not necessarily that of the sigstore community.</blockquote><p><strong><em>“Why did you chose to use a transparency log and not a blockchain?”</em></strong></p><p>We get this question often, so we figured it’s best to address this head on. It could be best summarised as <em>‘</em><strong><em>why would we use blockchain?</em></strong><em>’</em> as opposed to ‘<strong><em>why did we not use blockchain?</em></strong>’. The following points should illustrate how the first question is more apt.</p><h3>Tokens &amp; Fees</h3><p>The first issue is the need for a token and its related fees.</p><p>For a public blockchain a token of some sort is required to transact on the chain. A majority of the time these tokens are acquired as part of an initial ‘giveaway’, conversion of fiat money via some sort of exchange or via the use of compute power (in the case of proof-of-work).</p><p>With sigstore the key tenet of the service is that it is ‘<strong><em>free</em></strong>’ at point of use. We want everyone to be able to sign and get the same level of service, no matter how many resources you have at your disposal (both fiscal or computational). This is not possible when a token is involved. Typically fees are required and a general trend exists where the more popular the chain ecosystem becomes, the higher the token value inflates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*J3yo1b_0H_zvNXFa_y4Rww.png" /></figure><p>With a transparency log, no tokens / fees are required. It’s an API with a merkle tree as a backend. If you have an internet connection, you can sign artifacts and make records.</p><p><strong><em>“How about Hyperledger Fabric / R3 Corda? Those are token-less?”</em></strong>.<strong> </strong>True, but they have a private / “permissioned” mode of operation (there is often a need for additional access control layers, which often ends up negating the decentralised claim).</p><p>There are also considerations of factors such as a 51% attack. We do not want to have to be concerned about someone having majority ownership of a token / or consolidated hashing power.</p><h3>Private Key (Wallet) management</h3><p>A key area (excuse the pun) that sigstore was devised to address, is the lack of cryptographic signing adoption due to the pains of key management. The truth is the majority do not want to deal with the headache and cost of storing private keys securely. This is why cryptographic signing adoption is so low in open source communities (typically lower than 5%). With blockchain a key pair is required (a wallet). This is a problem for the following reasons:</p><ul><li>OSS contributors are often unfunded and not employed to develop open source. Quite often they could be from a developing nation or somehow disadvantaged financially (most students right?!). It is not fair to expect them to spend upwards of $100 on buying a hardware wallet.</li><li>Likewise we cannot expect users to store their wallet and passphrase in a cloud service.</li></ul><p>There are other alternatives using something like MetaMask, but we get into that a little later.</p><h3>Controversy</h3><p>This one is perhaps not fair, but alas it comes as a package with blockchain.</p><p>In sigstore, the more who adopt cryptographic signing, the better it is for all (a more secure supply chain). The truth is that blockchain makes for a controversial topic. Post to any forum about blockchain (save the ones catering to those holding crypto-currency) and you will find a very flammable mix of views. One group feels it is the answer to everything, the other feels it’s no more than a Ponzi scheme. Those in the middle are typically undecided and often drowned out.</p><p>We don’t have any of this concern with a transparency log. It’s a largely neutral technology.</p><h3>Production Ready</h3><p>Sigstore uses an existing implementation that has been put through its paces in production. We use the same backend as <a href="https://certificate.transparency.dev/howctworks/">certificate-transparency</a>.</p><p>Certificate transparency logs are queried millions of times a day by browsers to ensure a public transparent chain exists for all TLS certificates. The truth is we would have been in a ‘prototype’ stage for a lot longer if using blockchain, while we gained the confidence to have sigstore run in production. And of course, as said, we would have needed to address all of the above points too.</p><h3>Decentralisation</h3><p>One clear advantage a blockchain has is its distributed / decentralised architecture. However when we dig into the current developer landscape we often find its not decentralised. As mentioned under the Token heading, permissioned / token-less blockchains require gateways for access-control , canonicalization etc. dApps use centralised API access from providers such as <a href="https://infura.io/">Infura</a> or <a href="https://www.alchemy.com/">Alchemy</a> to interact with the blockchain.</p><p>MetaMask the most popular wallet implementation used by clients to communicate with Ethereum, also uses the Infura central API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*bCYTYLwL-mhOjpIfXZUF8A.png" /></figure><p>After the<a href="https://www.gemini.com/cryptopedia/the-dao-hack-makerdao"> DAO hack in ethereum</a>, a hard fork by developers created wide controversy about the other “angles” of centralisation that may exist: in this case, the fact that a series of developers can — and have — effectively thrown away the protocol-level decentralisation.</p><h3><strong>Would Sigstore Ever Use Blockchain?</strong></h3><p>It is possible! There is nothing forcing us to use one technology over the other. Instead, we are looking for properties that we can use today to help us secure the software ecosystem. While our assessment is that blockchains do not fit the bill (now), we wouldn’t discard a constantly-evolving and constantly-innovating field forever. Likewise, we are an open source community, which means we are always happy to hear proposals, weight them by their technical merit and the impact that they could have for everybody. If you feel that there are particular blockchains that could play with, we strongly encourage you to drop by the community meeting and show us how such a system would work — demos are very welcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d673ea41a9be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sigstore/sigstore-blockchain-vs-transparency-logs-d673ea41a9be">sigstore, blockchain vs transparency logs.</a> was originally published in <a href="https://medium.com/sigstore">sigstore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop calling it ‘cyber’.]]></title>
            <link>https://lhinds.medium.com/stop-calling-it-cyber-bc1b5fe648b6?source=rss-3160f5b9f9f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc1b5fe648b6</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Luke Hinds]]></dc:creator>
            <pubDate>Fri, 01 Apr 2022 20:23:44 GMT</pubDate>
            <atom:updated>2022-04-01T21:07:55.915Z</atom:updated>
            <content:encoded><![CDATA[<p>So this has been irking me for a while now.</p><p>Please stop saying you’re a ‘cyber expert’ and talking about the ‘cyber skills shortage’.</p><p>Once upon a time ‘cyber’ was an apt label for what was a smaller, niche area.</p><p>Security largely existed in a few unique realms, largely network defense and malware. Trust boundaries were far simpler, “Red and Green”. Everything outside is a threat and everything inside is trusted. The outside could ‘breach your perimeter’ and ‘infect you’ with evil cyber worms. Hackers sat hunched over laptops wearing a hoodie, typing cryptic hieroglyphs onto a green screened monitor, until they eventually cracked their way into some mega high security system. I don’t mean this to mock, in 20 years from now, the same sentiment will be apply to today techs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ngXUiR9zYmSIIRri" /><figcaption>typical stock go-to hacker image</figcaption></figure><p>However, the world has moved on since those times and a term such as ‘cyber’ should also be relegated with them. It’s not doing anyone any favours.</p><p>The ecosystem of security technologies is now a huge diverse industry in of itself, with many different technologies, with each requiring very specific skill sets. We now have so many verticals at play (and more coming).</p><ul><li>Vulnerability Research</li><li>Cryptography</li><li>Network Security</li><li>Cloud Security</li><li>Malware Analysis</li><li>Operating Systems Security</li><li>Trusted Computing</li><li>Confidential Computing</li><li>Secure coding</li><li>Penetration Testing / Red Team</li><li>DevSecOps</li><li>Identity and access.</li><li>…</li></ul><p>I could go on, but we will be here all day, especially considering each of the domains listed have their own sub topics.</p><p>Now look at that list and be honest with me.. how much deep expertise do you have in all of those? There are a few unicorns around that do, but I have met very few in my lifetime and I have been in this game for a good 20+ years now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*PraTmrVHn5L5Ay0D" /></figure><p>I think a good analogy to use here is ‘sports’. Not many refer to themselves as working in ‘sports’ or being a ‘sports expert’. I for example am a little too obsessed with running. I can talk all day and night about Vo2Max, Cadence, Training adaptations. Does this also make me an expert in Olympic Archery or Tae Kwon Do? No, of course not.</p><p>Or perhaps something a little closer to home. See how far a recruiter gets trying to hire ‘programmers’. Not very far (or at least without annoying a lot of engineers on linkedin), instead they narrow the search to a language or even a framework. Why does the same lack of scattergun not happen around ‘cyber’?</p><p>This is especially the case with ‘cyber skills shortage’. Everyone is on the hunt for ‘cyber experts’, where as a lot of the time the easier route to grow and acquire experts, is with those already familiar with existing common computing paradigms.</p><p>My gig is developing security software and when I look to bring people into a team, I often will not view the security part as essential. I need good engineers, they can learn the security part surprisingly quickly or at least enough to be useful.</p><p>When we use a blanket term of ‘cyber’ with it’s hollywood connotations of being a dark art and we are wizards. All we do then is cut off those folks who would be perfectly suited to transitioning to the roles we critically need to fill.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc1b5fe648b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[sigstore project update — March 2022]]></title>
            <link>https://medium.com/sigstore/sigstore-project-update-march-2022-bf34aa632388?source=rss-3160f5b9f9f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf34aa632388</guid>
            <dc:creator><![CDATA[Luke Hinds]]></dc:creator>
            <pubDate>Tue, 29 Mar 2022 14:53:20 GMT</pubDate>
            <atom:updated>2022-03-30T08:25:31.438Z</atom:updated>
            <content:encoded><![CDATA[<h3>sigstore project update — March 2022</h3><p>Another month and another whole batch of news to update you on.</p><p>For this months update we will be covering the coming GA status of sigstore, our presence at Kubecon EU 2022 and some of the awesome community adoption we have seen.</p><h3>sigstore GA</h3><p>Many engineers have been hard at work getting the sigstore public instance ready for GA. GA will mean we remove all experimental warnings and will have the service under 24 hour monitoring with an alerting system. A key part of the work, is having our transparency log be operationally ready to deal with any corruption events from compute failures or freak events such as a cosmic flip (for the curious, <a href="https://groups.google.com/a/chromium.org/g/ct-policy/c/PCkKU357M2Q/?pli=1">read me here</a>)</p><p>Many folks have been part of this working including Priya Wadhwa, Hayden Blauzvern, Lily Sturmann, Adolfo García, Carlos Panato.</p><p>We spoke with Priya and Lily about the activities.</p><p><em>“The Sigstore GA effort has been speeding along. Since January we’ve turned all Sigstore infrastructure, alerting and monitoring into code with Terraform, and are planning on open sourcing this code so that anyone can spin up Sigstore infrastructure easily. The team has been improving automation across the board by setting up managed project IAM permissions, a staging environment, and automating releases with Github Actions and ArgoCD. In the coming weeks, users can expect to see Fulcio 1.0 and Rekor 1.0! These are our next big milestones before Sigstore is ready to declare GA” </em>said Priya</p><p>On the transparency sharding work, Lily commented: “<em>The Sigstore team has completed some critical work around preparing Rekor, the transparency log, for sharding on the production server. Sharding breaks the transparency log into smaller sections and will allow Rekor to scale more easily and to support the rotation of signing keys. This functionality will be included in Sigstore’s GA. To prepare, users should make sure they are using at least v0.5.0 of the Rekor client, which will remain compatible with upcoming changes to the Rekor server.</em>”</p><h3>Community News</h3><p><strong>Maven central</strong> will integrate sigstore. Maven is a build tool from the Apache foundation for managing any Java-based project. The folks over at sonatype will be driving the effort to integrate sigstore signing into maven central, the main maven repository.</p><p>Jason Swank spoke about the implementation and their immediate plans “<em>We have every intent to adopt sigstore as part of the Maven Central platform. Additionally, Sonatype is in consultation with the Linux Foundation and OpenSSF to better understand the dimensions of our participation with their efforts to further support activities relevant to software supply chain security and observability</em>”.</p><p>For a more through overflow, check out <a href="https://central.sonatype.org/news/20220310_sigstore/">Jason’s announcement</a>.</p><p><strong>Harbor Project</strong></p><p>The <a href="https://github.com/goharbor/harbor/releases/tag/v2.5.0-rc2">harbor project</a> now officially supports cosign image signing and verification system. Harbor is widely used in on-prem, air-gapped envs, so this is huge for users migrating content into and out of those environments</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MFCANAPYs4N9Wu2xW8R2QA.png" /></figure><h3>KubeCon EU</h3><p>Following on from the success of KubeCon NA 2021 we will once again have a booth at the <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/">EU event in Valencia</a>. Should you be in attendance, please do come and meet the community at the sigstore booth. Stay in touch for more updates on sigstore @ KubeCon EU.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf34aa632388" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sigstore/sigstore-project-update-march-2022-bf34aa632388">sigstore project update — March 2022</a> was originally published in <a href="https://medium.com/sigstore">sigstore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[sigstore project update — January 2022]]></title>
            <link>https://medium.com/sigstore/sigstore-project-update-january-2022-d5772467a8e3?source=rss-3160f5b9f9f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5772467a8e3</guid>
            <dc:creator><![CDATA[Luke Hinds]]></dc:creator>
            <pubDate>Thu, 03 Feb 2022 21:29:24 GMT</pubDate>
            <atom:updated>2022-02-03T21:29:24.267Z</atom:updated>
            <content:encoded><![CDATA[<h3>sigstore project update — January 2022</h3><p>A new year and a new update blog on project sigstore! Lots of exciting events have happened (with a lot more on the horizon) to get the new year off to a great start.</p><h3>Community</h3><p>As has been the trend, the community is continuing to grow with no sign of levelling off.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*loWcpOmkW_O1B-Y5nW-xBg.png" /></figure><p>The same trajectory is also seen for commits</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mDH6HsmAwb4TNWDPJqzhTA.png" /></figure><h3>RubyGems</h3><p>The good folks at <a href="https://github.com/Shopify">shopify open source</a> have submitted an RFC to introduce <a href="https://blog.sigstore.dev/sigstore-ruby-ce3591838fe8">sigtore signing to the rubygems</a> community. Check out the <a href="https://github.com/rubygems/rfcs">RFC</a> for lots of interesting discussion on how the implementation will work.</p><h3>Cosign</h3><p>Three days ago, cosign shipped <a href="https://github.com/sigstore/cosign/releases/tag/v1.5.1">1.5.1</a> which introduces some bug fixes and some doc fixes!</p><h3>Rekor</h3><p>Rekor, the system that underpins the trust and transparency of the entire sigstore eco-system edges towards it’s 1.0 release. This will introduce a sharding API, that is required for project sigstore’s public service to go GA (more on that below)!</p><h3>GA Status</h3><p>sigstore is now getting close to being operationally GA. Work is underway to review our readiness for this important milestone. To date we have captured and signed over 1.2 million software supply chain artifacts, but this is likely to be a tiny amount of the fraction the volume we expect to see from sigstore. Therefore it’s important that we have a stable code base and a platform that can be monitored for anomalies and outages. Lots of work is happening in the community to foster that position.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5772467a8e3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sigstore/sigstore-project-update-january-2022-d5772467a8e3">sigstore project update — January 2022</a> was originally published in <a href="https://medium.com/sigstore">sigstore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sigstore project update — October 2021]]></title>
            <link>https://medium.com/sigstore/sigstore-project-update-october-2021-c8ef2e88f333?source=rss-3160f5b9f9f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8ef2e88f333</guid>
            <dc:creator><![CDATA[Luke Hinds]]></dc:creator>
            <pubDate>Tue, 07 Dec 2021 14:16:07 GMT</pubDate>
            <atom:updated>2021-12-07T15:24:56.340Z</atom:updated>
            <content:encoded><![CDATA[<h3>Sigstore project update — November 2021</h3><p>Welcome sigstore folks, its the start of a new month and so time to update you all about our progress for October!</p><h3>OpenSSF</h3><p>First off, we have sigstore joining the OpenSSF. You can read more about this in the <a href="https://blog.sigstore.dev/sigstore-the-openssf-315d09f135f2">existing post we made</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/0*YLYDOAx2FGIng4at.jpeg" /></figure><h3>Initial Funding</h3><p>We were also happy to announce a round of funding we got from our kind benefactors. This will give us some revenue for a Developer Relations Engineer and a highly important security audit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yQlOkuKPvi9VltqL8N5pvA.png" /><figcaption>Friends of sigstore who contributed an initial funding round</figcaption></figure><h3>Community Metrics</h3><p>The community is continuing to grow as is our rekor log entries (almost reaching 1 million!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rAHI21_ixJdNBCFk0Tpx1A.png" /></figure><h3>Project News</h3><h4>cosign 1.4</h4><p>cosign 1.4 shipped today!</p><p>One of the main features is that it now resides upon a TUF (the update framework) root.</p><p>Experimental mode is now removed for cosign Keyless.</p><p>For more details, check out the <a href="https://github.com/sigstore/cosign/releases/tag/v1.4.0">release notes</a></p><p>Also new in, is that sigtore / cosign functionality is now available as GitHub Actions starter workflow, read more in <a href="https://github.blog/2021-12-06-safeguard-container-signing-capability-actions/">GitHub’s blog post</a>.</p><h4>rekor</h4><p>rekor 1.0 is now on the verge of completion with the sharding patch in review. Once this lands, we consider rekor as production grade.</p><h4>fulcio</h4><p>Another sigstore project on the verge of a 1.0 release, now that the GCP CA API has been ported to v1.</p><h4>sget</h4><p>sget is edging towards its first list and recently work landed to cryptographically verify the root policy.</p><p>See you at the end of the year and happy holidays!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8ef2e88f333" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sigstore/sigstore-project-update-october-2021-c8ef2e88f333">Sigstore project update — October 2021</a> was originally published in <a href="https://medium.com/sigstore">sigstore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[sigstore & the OpenSSF]]></title>
            <link>https://medium.com/sigstore/sigstore-the-openssf-315d09f135f2?source=rss-3160f5b9f9f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/315d09f135f2</guid>
            <dc:creator><![CDATA[Luke Hinds]]></dc:creator>
            <pubDate>Tue, 16 Nov 2021 19:33:32 GMT</pubDate>
            <atom:updated>2021-11-16T19:36:06.326Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*nPBuy0gfQrlfI81_fasZ6Q.jpeg" /></figure><p>A quick post based on the recent news of sigstore joining the <a href="https://openssf.org/">OpenSSF</a> and what this means.</p><p>For those of you not already in the know, the Open Source Security Foundation (OpenSSF) is a Linux Foundation project committed to collaboration with existing communities to advance open source security for all. The OpenSSF consists of what are termed <a href="https://github.com/ossf">working groups</a>, who tackle topics such as supply chain security, vulnerability reporting, security best practises and more (one working group you may well have heard of is <a href="https://slsa.dev/">SLSA</a>).</p><p>sigstore will now become a project under the OpenSSF. This makes sense on several levels:</p><ol><li>We both have alignment around our overall vision (securing the Open Source supply chain).</li><li>TheOpenSSF has a funding allocation to help projects such as sigstore.</li></ol><p>Point 2 is of particular relevance to sigstore, as sigstore will run as a public good, non-profit service. This means costs will be incurred such as daily running costs for hardware, cloud computing and staff to ensure the service remains updated and available.</p><p>For the sigstore community itself, this will mean no change. The same set of project maintainers remain in place, as do our code repositories and slack channel, website etc. If you’re a member of the sigstore community, you will not notice any change to your daily interaction and work flow.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=315d09f135f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sigstore/sigstore-the-openssf-315d09f135f2">sigstore &amp; the OpenSSF</a> was originally published in <a href="https://medium.com/sigstore">sigstore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sigstore project update — September 2021]]></title>
            <link>https://medium.com/sigstore/sigstore-project-update-september-2021-799162b5a686?source=rss-3160f5b9f9f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/799162b5a686</guid>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[sigstore]]></category>
            <dc:creator><![CDATA[Luke Hinds]]></dc:creator>
            <pubDate>Fri, 01 Oct 2021 18:01:22 GMT</pubDate>
            <atom:updated>2021-10-01T18:48:10.024Z</atom:updated>
            <content:encoded><![CDATA[<h3>Sigstore project update — September 2021</h3><p>Well another month has passed and as per usual in the sigstore world, a lot has happened!</p><p>Since our last update in August we have<strong> over double the amount of contributors</strong> working on sigstore! There has been a leap from 46 to 98! wow!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/1*ylUfuaXazXG3ZlzU5J-CSw.png" /><figcaption>contributors</figcaption></figure><h3>KubeCon NA 20201</h3><p>sigstore will be at <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/">KubeCon North America </a>with it’s own booth, so if you’re in person at the event, come and say hi! We will be at booth number S86</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*ZfSOLBJi_3nwpTXiX79rHA.png" /><figcaption>sigstores booth</figcaption></figure><p>There will be swag available in the form of a stickers and security keys. However there is small caveat that you try out sigstore with one of our community members, so come on over at get your stuff signed!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/554/0*o0iY6mQZ9bhyzoGR" /><figcaption>sigstore swag</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cvD9kHIt9Fiw3I0X" /><figcaption>Extra special swag at sigstore.</figcaption></figure><h3>Sigstore talk.</h3><p>On Wednesday October 13 11:55am — 12:30pm. Dan Lorenc and Bob Callaway will be performing a talk on sigstore ‘How we started, where we are, and where we are headed’.</p><h3>Project Updates</h3><h3><strong>Rekor</strong></h3><p>Our transparency log is edging close to a 1.0 release now, while we just fine tune the API for our approach to sharding.</p><p>sharding is required if ever a corruption occurs, this allows us to freeze the former log and create a new one, with no loss of data or service.</p><p>Once sharding is landed, we cut 1.0 and rekor is then considered production grade.</p><h3>cosign</h3><p>cosign is developing fast. Work is being carried out to refactor the CLI over to <a href="https://github.com/spf13/cobra">cobra</a> and we recently included github’s OIDC into cosign (more on the OIDC change under fulcio), along with support for GCP environments without workload identity.</p><p>cosign is now at <a href="https://github.com/sigstore/cosign/releases/tag/v1.2.1">version v1.2.1</a></p><h3>fulcio</h3><p>GitHub recently released its own OpenID connect functionality, which enables sigstore to provide an even more seamless keyless signing experience.</p><p>With fulcio keyless signing it is required that a developer be present to perform the OpenID connect grant. Sigstore clients open a browser to our oauth2 server, which then prompts the user to ‘login’ with a provider account (Google, Github, Microsoft etc). This grant then allows us to obtain the email addresss of the user and place it into a sigstore X509 signing certificate.</p><p>Now the above works great for what we term an ‘attended signing’, but what about ‘unattended’, e.g. a headless machine with no human present to interact with the browser to allow the grant.</p><p>With Github OIDC now, we can provide an unattended experience to signing artefacts (such as a container image) within a github action. The great factor here, is that GitHub have added sigstore as an OIDC Audience (idToken Field).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lTYGOcpmA7H4w_njphIpYA.png" /></figure><p>Keep an eye out for an entry on this blog on how to get set up for unattended sigstore signing!</p><h3>Community</h3><p>As always, the slack channel is counting to grow, we are now at 646 members</p><p>The <a href="https://github.com/sigstore/community#community-meetings">community meetings</a> are also seeing lots of new faces, do come along if you have any interest in sigstore.</p><h3>Talks</h3><p>There have been a few talks recently.</p><p><a href="https://www.youtube.com/watch?v=JXcqX5ozuvc">Luke Hinds spoke at #romhack in Rome Italy about sigstore.</a></p><p><a href="https://www.youtube.com/watch?v=JhqQ_6Z1SCA">Dan Lorenc Chatted with commiting to cloud native</a></p><p><a href="https://www.youtube.com/watch?v=TGC1zT_BNBM&amp;t=341s">Luke Hinds, technically speaking with Chris Wright</a></p><p><a href="https://www.youtube.com/watch?v=cjY26RRHpo8">Andrew Block discusses the sigstore helm plugin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=799162b5a686" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sigstore/sigstore-project-update-september-2021-799162b5a686">Sigstore project update — September 2021</a> was originally published in <a href="https://medium.com/sigstore">sigstore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sigstore Project Update — August 2021]]></title>
            <link>https://medium.com/sigstore/sigstore-project-update-august-2021-1fad6d12b8dc?source=rss-3160f5b9f9f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fad6d12b8dc</guid>
            <dc:creator><![CDATA[Luke Hinds]]></dc:creator>
            <pubDate>Tue, 31 Aug 2021 08:16:18 GMT</pubDate>
            <atom:updated>2021-08-31T11:43:48.946Z</atom:updated>
            <content:encoded><![CDATA[<h3>Sigstore Project Update — August 2021</h3><p>Welcome to our project update for August.</p><p>As always the community is continuing to expand. We are now close to 600 members in our <a href="https://join.slack.com/t/sigstore/shared_invite/zt-mhs55zh0-XmY3bcfWn4XEyMqUUutbUQ">slack workspace</a>. We now have <a href="https://insights.lfx.linuxfoundation.org/projects/sigstore/dashboard">46 contributors</a> and are growing each day.</p><p>The month of August saw 254 commits and 526k lines of code were changed!</p><p>Lots of exciting things are happening, read more for our project updates and our presence at KubeCon, NA.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/547/0*31GOseoZ8EIUENqv" /></figure><h3>cosign</h3><p>Cosign hit 1.0 and adoption is coming on great. It seems almost daily that we spot someone new using cosign.</p><ul><li>go-releaser now has the <a href="https://carlosbecker.com/posts/goreleaser-cosign/">ability to sign</a> using cosign</li><li>flagger, a delivery kubernetes operator is now <a href="https://twitter.com/stefanprodan/status/1430491008752623617">signing its images</a> using cosign</li><li>Kubernetes is <a href="https://github.com/kubernetes/release/issues/2227">seeking to expand</a> its signing efforts using cosign and sigstore</li></ul><p>There is some exciting work happening around TUF integration with a Fulcio root. See here for a more <a href="https://dlorenc.medium.com/using-the-update-framework-in-sigstore-dc393cfe6b52?source=user_profile---------2----------------------------">detailed update</a>, and expect to see this start landing next month!</p><h3>fulcio</h3><p>Fulcio continues on its path to maturity. A first release is in the planning stage and will come shortly after rekor 1.0 (since rekor is a dependency of fulcio). We’re also working to directly integrate fulcio IDs with The Update Framework, which should be <a href="https://github.com/theupdateframework/go-tuf/pull/141">landing soon</a>.</p><h3>rekor</h3><p>Rekor will soon be reaching it’s 1.0 release which means we consider it ready for production! We are currently working on a sharding approach and considering its relevant API design.</p><h3>New Website!</h3><p>sigstore has a cool new website, check it out <a href="https://sigstore.dev/">https://sigstore.dev</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CPhP_JkoAozRcVnqTjqWQA.png" /></figure><p>We also have a new docs system under development!</p><h3>Other Projects</h3><p>The Helm Plugin is almost ready to <a href="https://github.com/sigstore/sigstore-helm-operator/pull/2">publish</a></p><p><a href="https://github.com/sigstore/k8s-manifest-sigstore">k8s-manifest-sigstore</a> is developing at a fast space and will bring many protections to the kubernetes space with its ability to leverage admission controller based signing and validation of workloads.</p><p>We now have <a href="https://github.com/sigstore/homebrew-tap">homebrew taps</a> for cosign and rekor-cli!</p><h3>Events and talks!</h3><p>Sigstore will be at KubeCon, NA, 2021 where we will have a booth! Come and say hi and let’s chat signing all the things! Community members will be present and there to help you get set up using sigstore and there will be swag!</p><p>There will also be lots of talks. Project co-founders Dan Lorenc and Luke Hinds will be providing a <a href="https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/program/schedule/">history of sigstore and what’s next</a></p><h3>Supply Chain Security Con</h3><p>The Continuous Delivery Foundation is hosting a colocated event with KubeCon North America called Supply Chain Security Con, and Sigstore is featured in a number of talks. Check out the full agenda <a href="https://events.linuxfoundation.org/supplychainsecuritycon-north-america/">here</a>.</p><p><a href="https://www.heavybit.com/library/podcasts/the-kubelist-podcast/ep-20-sigstore-with-dan-lorenc-of-google/?utm_campaign=coschedule&amp;utm_source=twitter&amp;utm_medium=heavybit&amp;utm_content=Ep.%20%2320,%20Sigstore%20with%20Dan%20Lorenc%20of%20Google">Kubelist Podcast</a></p><p><a href="https://www.youtube.com/watch?v=JhFr5_PQS_Y">OSS Supply Chain Security Deep Dive with Dan Lorenc</a></p><p><a href="https://www.twitch.tv/videos/1127122758">Luke Hinds OpenShift Commons — sigstore</a></p><h3>Getting Involved!</h3><p>As always, we truly welcome contributors and users to our community. We take pride in being friendly to new folks and fostering a welcome and safe environment. Being a large open source project, there is always lots to do and it’s not always complex coding tasks, helping with documentation, general testing or just telling others about sigstore are all valued contributions. Come and join our <a href="https://join.slack.com/t/sigstore/shared_invite/zt-mhs55zh0-XmY3bcfWn4XEyMqUUutbUQ">slack workspace</a> and say hello!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fad6d12b8dc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sigstore/sigstore-project-update-august-2021-1fad6d12b8dc">Sigstore Project Update — August 2021</a> was originally published in <a href="https://medium.com/sigstore">sigstore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sigstore Project Update — May 2021]]></title>
            <link>https://medium.com/sigstore/sigstore-project-update-may-2021-ad8df9ac8dc5?source=rss-3160f5b9f9f9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad8df9ac8dc5</guid>
            <dc:creator><![CDATA[Luke Hinds]]></dc:creator>
            <pubDate>Wed, 19 May 2021 10:52:32 GMT</pubDate>
            <atom:updated>2021-05-19T11:09:42.281Z</atom:updated>
            <content:encoded><![CDATA[<h3>Sigstore Project Update — May 2021</h3><p>Welcome to our project update for May. We have a lot to update you on. As you can tell by now, things move quickly in sigstore, so let’s get into this!</p><p>The community is continuing to expand. We are now close to 400 members in our <a href="https://join.slack.com/t/sigstore/shared_invite/zt-mhs55zh0-XmY3bcfWn4XEyMqUUutbUQ">slack workspace</a>. We now have <a href="https://insights.lfx.linuxfoundation.org/projects/sigstore/dashboard">40 contributors</a> and are growing each day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/0*VT5l9KET4BZZNYkO" /></figure><h3>cosign</h3><p>Cosign is blazing ahead with lots of new features. It now has support for Hashicorp <a href="https://github.com/sigstore/cosign/blob/3eaf8268804501cd7db747247bf3f0bd608466ab/KMS.md#hashicorp-vault">vault KMS</a>. <a href="https://github.com/sigstore/cosign/pull/285">Offline verification</a> of Rekor signatures (great for air gaped instances). Windows binaries can now also be signed! All these features were shipped in cosign release <a href="https://github.com/sigstore/cosign/releases/tag/v0.4.0">v0.4.0</a></p><h3>fulcio</h3><p>Fulcio continues on its path to maturity. We recently refactored out the test client code and added the ability for fuclio to now sign <a href="https://github.com/sigstore/fulcio/commit/240a054e2829c8de75b0d34573953310a9af31bb">RSA certificates</a> (alongside ecdsa).</p><h3>rekor</h3><p>Rekor is close to release 0.2.0 which will include <a href="https://github.com/sigstore/rekor/pull/293">RFC 3161 timestamp</a> responses. We are seeing continued interest in rekor, as it is so well suited to SBOM validation and storage, especially with its ability to allow customized schemas.</p><h3>New Projects</h3><p>We recently bootstrapped a <a href="https://github.com/sigstore/helm-sigstore">helm sigstore</a> plugin, to allow signing and verification of helm charts.</p><p>The <a href="https://github.com/sigstore/ruby-sigstore">rubygems plugin</a> is reaching completion, it is now possible to sign gems using keyless OpenID backed functionality , at present the verification part work is underway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dPQGNk7SF-hRDmaQ" /></figure><p>The <a href="https://github.com/sigstore/sigstore-maven-plugin">maven plugin</a> is now complete and we are in discussion with the community on how they can best leverage sigstore for JAR signing.</p><p><strong>Sget</strong> it really cool prototype put together by Dan Lorenc for signing and verification of curl | bash style operations by leveraging OCI registries. We plan to launch this as its own project, as the internet is awash with folks piping scripts off the internet or downloading artefacts with no trust guarantees.</p><h3>signing party</h3><p>The last preparations are occurring for the sigstore signing party. This will bootstrap the trust root of sigstore utilising <a href="https://theupdateframework.io/">TUF</a> (The Update Framework). TUF is based on a key hierarchy.</p><p>Five community members (from Red Hat, Google and academia (Purdue University/ NYU)) will generate five hardware protected keys as TUF root ROLES and target ROLES. These five keys will be utilized to sign the root keys used to establish sigstore’s root of trust for rekor, fulcio CA and the CTFE log. It will also sign all timestamps generated within sigstore’s ecosystem.</p><p>Using TUF also provides us with <a href="https://theupdateframework.github.io/papers/survivable-key-compromise-ccs2010.pdf?raw=true">survivable key compromise</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/60/0*XH7x12uAZsAhY9vb" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ue4em9OYaGQ8jsqD.png" /></figure><p>As we are a community who believe in <strong>openness</strong> and <strong>transparency</strong>, the signing will happen in the open. The signing event will be broadcast live by CNCF <a href="https://cloudnative.tv/">cloudnative.tv</a> on the 18th of June. The signatures and public keys will all be recorded into a git repository (sigstore/root-signing), we then encourage everyone to <strong>fork this repository</strong> for accountability!</p><h3>Release Manager</h3><p>Sigstore now has a release manager! <a href="https://github.com/cpanato">Carlos Tadeu Panato Jr </a>will be bringing his experience as a <a href="https://github.com/kubernetes/release">kubernetes release manager</a> to sigstore and will help to coordinate milestones and releases within sigstore’s projects.</p><h3>Getting Involved!</h3><p>As always, we truly welcome contributors and users to our community. We take pride in being friendly to new folks and fostering a welcome and safe environment. Being a large open source project, there is always lots to do and it’s not always complex coding tasks, helping with documentation, general testing or just telling others about sigstore are all valued contributions. Come and join our <a href="https://join.slack.com/t/sigstore/shared_invite/zt-mhs55zh0-XmY3bcfWn4XEyMqUUutbUQ">slack workspace</a> and say hello!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad8df9ac8dc5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sigstore/sigstore-project-update-may-2021-ad8df9ac8dc5">Sigstore Project Update — May 2021</a> was originally published in <a href="https://medium.com/sigstore">sigstore</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>