Skip to content

openSeaChest VS SeaChest

Jump to bottom
Tyler Erickson edited this page Sep 6, 2024 · 3 revisions

OpenSeaChest vs SeaChest, what's the difference?

For the most part openSeaChest and SeaChest are almost identical, however there are a few differences.

openSeaChest supports all standardized behavior and approved Seagate vendor unique behavior.

As of September 4, 2024 SeaChest has the following features that are not found in openSeaChest:

  • TCG Revert and RevertSP
    • Need to remove some Seagate unique IP and behavior from library code before it can be open sourced.
    • More of a time constraint than anything else with all of the projects we have a backlog on.
  • --tcgInfo in SeaChest_Security
    • Same reasons as revert and revertSP.
  • Firmware Updates via a config file (--fwdlConfig)
    • Support for .cfs files will not be made available in open source. This file format has been retired.
    • Modern JSON format may receive partial support in openSeaChest in the future.
  • Official Support from Seagate's support center
    • This applies specifically to SeaChest_Lite
    • All openSeaChest support will be found on Github through this Wiki, Docs, --help options, Github Issues, and Github Discussions

If an option is available in both SeaChest and openSeaChest, feel free to file it on the openSeaChest project, the code is probably exactly the same!

For SeaChest unique options, please use the Toolbin Issue tracker.

For any security issues for any Seagate software or hardware, please disclose them here: Seagate Vulnerability Disclosure

Clone this wiki locally