Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestions of archive hosting (SSH access with two accounts: one main RW account with sub RO account?) #100

Open
tlaurion opened this issue Jun 21, 2022 · 4 comments
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Milestone

Comments

@tlaurion
Copy link
Contributor

tlaurion commented Jun 21, 2022

Unfortunately, rsync.net cannot offer either tar, python or sync into accounts ssh environments.

Sad because they offered enough customization to offer a main RW account and then RO sub-account.
Not hard to implement with proper rights on folders, but I have not heard of anyone else providing such feature with so cheap data plan (unlimited bandwidth, payment on stored data amount).

Suggestions of other providers providing subaccounts and python3, sync, rm, mv, mkdir, cat, tar, mountpoint available commands from ssh terminal?

@tasket
Copy link
Owner

tasket commented Jun 22, 2022

The rsync.net plan does seem pretty unique... maybe someone reading this will know of an alternative?

@tasket tasket added help wanted Extra attention is needed question Further information is requested labels Jun 22, 2022
@tlaurion tlaurion changed the title Suggestions of achive hosting (SSH access with two accounts: one main RW account with sub RO account?) Suggestions of archive hosting (SSH access with two accounts: one main RW account with sub RO account?) Aug 3, 2022
@tlaurion
Copy link
Contributor Author

tlaurion commented Aug 3, 2022

@tasket even if rsync.net is unique, it is not fit for wyng.

They won't offer Python and other host tools currently required by wyng.

But their offer of RW main account with RO sub account is required for "lvm deployment as a service".

Otherwise, without host providing write protection mechanisms, backups stored are also writeable (and destroyable) by users having access to the remote archives.

So two use cases here

  • RW accounts for users encrypting their backups for their sole purposes (still require hosts recommendation)
  • RW with RO sub accounts for images providers

@tlaurion
Copy link
Contributor Author

veeble.org, 5$ USD a month, 2gb ram, 20GB ssd and 100TB bandwidth.

They of course have more space/bandwidth/memory options available if needed and DNS name as well for later more serious PoC.

Was able to duplicate rsync.net subaccount setup based on basic user rights management, and created main rw user account with a ro subaccount(in subdir) used to specify what OEM image type is there (q41_insurgo here as example) where ssh authorized_keys is simply put somewhere else per sshd_config override on user match:

Match User q41_insurgo
        AuthorizedKeysFile /etc/ssh/authorized_keys-%u

So safe state restoration as a service is totally feasible on cheap storage friendly VPS services.

@tlaurion
Copy link
Contributor Author

Interesting list of providers for users wanting to store on the cloud with 0.4 encrypted backups
https://forum.qubes-os.org/t/known-good-vps-providers/7026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants