search

GaloisInc / BESSPIN-FETT-Portal

The web-based portal used by FETT Researchers to manage Target instances.
Apache License 2.0
0 stars 0 forks source link

LEARN: SRI/Cambridge Description #296

Closed jrtc27 closed 4 years ago

jrtc27 commented 4 years ago

Currently the description for our environment is:

Cambridge/SRI

  • CPU: Bluespec CHERI-RISC-V
    • OS:
    • Applications:
    • Web Server (nginx v.1.13.12)
    • Database (sqlite v.3.22.0)
    • SSH Daemon (OpenSSH 7.3)
    • Voting registration application
    • Additional applications modified to incorporate CHERI protections
    • Researcher-provided and compiled vulnerable applications
  • Security researchers are given access to an unprivileged shell to interact with custom applications
  • FAQ forthcoming if required based on contest activity

Issues are as follows:

  1. We're the only CPU to not say P1/P2 in the name; incorporating CHERI is nice, but perhaps we should be saying something like "Bluespec P2 w/ CHERI extension" (or, like UMich with Morpheus, put CHERI in our team name instead)

  2. OS should state FreeBSD or CheriBSD (currently LAUNCH says FreeBSD so perhaps we should pick that, or update LAUNCH accordingly if we decide on CheriBSD)

  3. We want researchers to have the option of a root shell (and believe that all will probably want it for operational convenience)

  4. (minor) Are we Cambridge/SRI or SRI/Cambridge... to DARPA we're the latter, but at Cambridge we like to think we're the former so perhaps it's currently correct :) also LAUNCH goes for the third option of "SRI-Cambridge"

rwatson commented 4 years ago

Probably “CheriBSD (CHERI-extended FreeBSD)” or similar is the way to go on OS name, to ensure they understand that it isn’t vanilla FreeBSD, but are also aware that it is essentially FreeBSD. This may help them google better for one or both.

As SRI is the prime contractor, I suggest “SRI/Cambridge” is the best choice in this context, and will be consistent with what DARPA is saying.

Bluespec is arguably the company name, whereas BSV is the language. Probably BSV should be used in the same situations that Chisel might be. (This is a distinction often lost in conversation, but Bluespec (the company) tries to be very clear on it.)

jrtc27 commented 4 years ago

They seem to have given up then based on what their README says for the open-source bsc:

Compiler, simulator, and tools for the Bluespec Hardware Description Language. Bluespec is a single language for hardware designs that comes in two syntactic flavors, which are interchangeable:

  • Bluespec SystemVerilog (BSV)
  • Bluespec Haskell (BH, or "Bluespec Classic")

Bluespec is a high-level hardware description language. ...

mattlebeau-galois commented 4 years ago

@kurthopfer @brian-fivetalent - Incorporated updates noted here into google doc with all LEARN content. https://docs.google.com/document/d/1XmkHB16E56JiyuA6fsVvNk2qxmcXWQjqaTXaPJUH_EM/edit#

mattlebeau-galois commented 4 years ago

Implemented. Closing #296