SyncOS Introduction

SyncOS is developed based on Secure-K OS and Debian Stretch release.

SyncOS is a live USB OS. It is distributed as syncos-liveusb-yyyymmdd.iso image file. Customer can use third party USB burning tool to burn this iso image file into a USB drive.

We suggest you to use Rufus for burning SyncOS iso image to bootable live USB, as it's proved to be a reliable and capable tool. SyncOffice have a main tab page - USB Utility Page embed a customized Rufus tool for your SyncOS operations.

som-usb-rufus-tab

SyncOS Drive File Strcture

After SyncOS live USB is created, its drive under Windows is shown as follow.

syncos-drive-icon-in-windows

Go into fully built SyncOS drive. It shows its root directory as follow.

syncos-drive-root-directory

In its root directory, it contains:

  • /boot folder, the Grub Multiboot boot loader files are there.
  • /casper folder, this is where OS file system files stored. Its main file is filesystem.squashfs. Different from other ordinary live USB, Its filesystem.squashfs is encrypted. You cannot decipher and unzip it easily. This can prevent some extent of hacking possibilities.
  • App_Container_disk.img, this is a GB size disk block image file for LXC guest container. It has 5600MB and 12600MB two versions, for 8GB and 16GB USB drives respectively. It should be manually copied here using any copy means. If you don't need that LXC guest container for playing own application, there is no need to copy it into this SyncOS USB drive.
  • User_Home_disk.img, this is a 300MB disk block image file for persistence storage, mainly for user home folder contents, such as user credentials and profiles. It can also be manually copied here using any copy means. It's an essential file. Without it, SyncOS cannot login after boot up. This 300MB image file needs to be backed up routinely. In some rare cases, it could be corrupted if lacks of enough resources.
  • userid__SyncOS.crt.tes, this is the encrypted certificate which SyncOS will use for auditing when booting up.
  • rclone.conf.tes, this is the encrypted Rclone cloud credential file, which SyncOS will use to connect to the corporate cloud.
  • Other files, autorun.ico, autorun.inf, boot.catalog and md5sum.txt are for auto boot and CRC integrity check.

SyncOS Bootup

To boot up SyncOS live USB, normally you need to change PC's boot sequence. Some PC provide one-time boot sequence selection, some provide BIOS/UEFI option to change statically prefer USB boot in front of hard-disk boot.

The following screenshot is from a Dell PC, which has F12 button that can trigger an one time boot sequence selection at start of PC boot up.

f12-boot-selection-gui1

After PC start boot SyncOS, it shows a loading progress bar and a dynamic splash logo as follow.

syncos-bootup-splash

After boot up OK, it shows login GUI as follow. SyncOS always uses an unprivileged user "teleon" as login user. User teleon's default password is as200712. Once a local certificate is applied, the certificate can define a new password and it will be updated when it boot up.

syncos-login-gui1b

syncos-login-gui2b

After successful login using Linux user password assigned to the associated certificate, the SyncOS desktop shows up as follows.

syncos-desktop-gui-1