Cryptosat
WebsiteBlogSatellite Tracking
  • Cryptosat
    • 🛰️Satellite tracking
    • 📄SpaceTEE paper
    • Contribution to the Ethereum KZG Ceremony
      • Cryptosat KZG Operation Tracker
      • Crypto2 contribution output
      • Contribution verification
  • Cryptosim
    • Cryptosim
    • Asynchronous API
    • Use-case examples
    • Open-source contribution
  • 🗳️Private Voting
    • Private Voting on Snapshot X
    • Private Voting Contract
    • Browser Side Encryption
  • 🎲random-beacon
    • Verifiable Random Beacon
    • Using the random beacon on-chain
  • API documentation
    • Message Signing
    • Authentication
    • Randomness API
      • Tutorial
      • API reference
    • Queue API
      • API reference
        • Queue
          • Request
          • Requests
    • Public randomness SAPI
      • About
      • API reference
        • Public randomness
          • Result
    • FROST API
      • About
      • API reference
        • Frost
          • Partial sign
          • Private key
      • Specification
    • Satellite Public Keys
  • ⏳Time-based Primitives
    • ⌚Time-based primitives and delay-encryption
    • ⚛️Using Delay Encryption for Atomic Swaps
  • Flastsat Environment
    • Overview
    • Access and Control
    • Crypto Engine Specs
    • Power API
Powered by GitBook
On this page
  • Access
  • Connect to Environment
  • Control
  • The Local Machine
  1. Flastsat Environment

Access and Control

Access

Connect to Environment

The Flatsat can be accessed using SSH. Please email contact@cryptosat.io for more details.

Control

The Local Machine

The local machine is a Debian based machine connected to the internet and to the Flatsat. This machine facilitates access to all the Crypto Engines.

Individual Crypto Engine Control

From the local machine terminal, you can use SSH to directly connect to a Crypto Engine. The following command will connect to the Crypto Engine 2 via SSH.

ssh ce2

sftp can be used to transfer files. Other common utilities are installed on the local computer as well.

Here is an example how to upload a file using sftp:

sftp -i .ssh/id_rsa -P [port] user@server_ip

Crypto Engine Orchestration

Ansible is installed on the local machine. The ~/ansible/ directory contains the inventory and configuration files to quickly run playbooks and commands across all the Crypto Engines.

For example, this command will run hostname on all Crypto Engines:

~/ansible $ ansible crypto_engines -a "hostname"

This command will run hostname just on Crypto Engine 0 (ce0)

~/ansible $ ansible ce0 -a "hostname"

The playbook copy.yml can be used to upload files to all Crypto Engines

~/ansible $ ansible-playbook copy.yml -e "src=~/test3"

The target targets parameter can be used to specify a subset of hosts. The dest can be used to specify a remote path and name.

~/ansible $ ansible-playbook copy.yml -e "targets=ce2,ce3 src=~/test3"

PreviousOverviewNextCrypto Engine Specs

Last updated 1 year ago

Please refer to the Ansible for more information. The Cryptosat team will be happy to assist you in creating Ansible playbooks.

documentation