Commit Graph
6 Commits
Author SHA1 Message Date
Ian Littman c8e3a3b208 Clean up "here" link anchors in articles (#29755) 2025-06-09 09:48:27 -04:00
Noah Talerman aa16261959 Fleet attestation: cleanup (#26487) 2025-02-20 13:37:52 -05:00
Noah Talerman f9dc049679 GitHub (SLSA) attestation guide (#26222)
- Add instructions for verifying Fleet, fleetd, and fleetctl
2025-02-14 13:01:39 -05:00
Noah Talerman ad883ee1d1 Guide: update Fleet software attestation (#26098)
- 4.63.0 is shipped
- Use "fleetd" language to be consistent with docs and product
2025-02-05 15:50:22 -05:00
Scott Gress fa65eb7b55 Update Software Attestation guide (#26000)
For #25334 

Implementing changes suggested by @zayhanlon 

> @sharon-fdm or @sgress454 in the style of our current articles, i
think its okay to cut the fluff 'At Fleet, we understand the importance
of having a secure software supply chain. Our core value of 🟣
[Openness](https://fleetdm.com/handbook/company#openness) extends to
ensuring that our users can verify the provenance and authenticity of
any Fleet software they install. With that in mind,' and start with "As
of version 4.63.0 Fleet has added"

Done

> fleetctl we don't capitalize correct?

Updated references to `fleet`, `fleetctl` and `osqueryd` to be
lowercased and use code styling, to be consistent with usage in other
articles.

> I think orbit we also dont capitalize

It's pretty inconsistent but it looks like we mostly do capitalize it,
which makes sense to me as it's not a command you run (as opposed to
`fleet`, `fleetctl` or `osqueryd`). I left it for now but can change to
`orbit` if that's the official style guide policy.
2025-02-04 08:54:02 -06:00
Scott GressandDrew Baker bb5ec47ec0 Add SLSA guide (#25423)
This PR adds an article about the software attestations Fleet now adds
to release artifacts.

---------

Co-authored-by: Drew Baker <89049099+Drew-P-drawers@users.noreply.github.com>
2025-01-17 09:38:37 -06:00