Streisand: The whole scripts needs update

Created on 18 Nov 2020  路  5Comments  路  Source: StreisandEffect/streisand

I've tried several time to install the Streisand but every time has a problem like outdated gpg key, deprecation warnings, not found errors of requirements for shadowsocks, and so on.

Expected behavior:

I expect to get installed Streisand without lots of problems

Actual Behavior:

As I said there are lots of problems,

Steps to Reproduce:

  1. start the script on an existing Ubuntu 16 with default options.

[ ### Ansible Information

  • Ansible version: 2.8.4
  • Ansible system: Linux
  • Host OS: Ubuntu
  • Host OS version: 20.04
  • Python interpreter: python3
  • Python version: 3.8.5

Streisand Information

  • Streisand Git revision: af5eb7dac157a2416ea64cba96cf32f7f505d9ff
  • Streisand Git clone has untracked changes: yes
  • Genesis role: existing-server
  • Custom SSH key: False

Enabled Roles

  • Shadowsocks enabled: True
  • Wireguard enabled: False
  • OpenVPN enabled: True
  • stunnel enabled: True
  • Tor enabled: False
  • Openconnect enabled: True
  • TinyProxy enabled: True
  • SSH forward user enabled: True
  • Configured number of VPN clients: 3 ]

examples of problems:

TASK [openvpn : One or more of the VPN clients could not be mirrored. Please file a bug report on GitHub so that the version number, checksum, or download location can be updated. Setup will now continue.] *

TASK [shadowsocks : One or more of the VPN clients could not be mirrored. Please file a bug report on GitHub so that the version number, checksum, or download location can be updated. Setup will now continue.] *

streisand_shadowsocks_enabled or streisand_ssh_forward_enabled or streisand_stunnel_enabled or streisand_tor_enabled
as a bare variable, this behaviour will go away and you might need to add |bool to the expression in the future.
Also see CONDITIONAL_BARE_VARS configuration toggle.. This feature will be removed in version 2.12. Deprecation
warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

Most helpful comment

Well, I second that. It is true that many sections are out of date and the activity on the project is very low to non-existent. Also, the platform of choice Ubuntu 16 is getting old, it will be end of line in 2021. Beyond that date, the whole install will start becoming unsecure due to lack of support. Looks like the developers got tired and moved on to better, greater things. If that is the case, this is very sad since the need for a good trustworthy vpn has never been higher. I can help a bit but I do not have the skill set to make a major upgrade by myself.

All 5 comments

Well, I second that. It is true that many sections are out of date and the activity on the project is very low to non-existent. Also, the platform of choice Ubuntu 16 is getting old, it will be end of line in 2021. Beyond that date, the whole install will start becoming unsecure due to lack of support. Looks like the developers got tired and moved on to better, greater things. If that is the case, this is very sad since the need for a good trustworthy vpn has never been higher. I can help a bit but I do not have the skill set to make a major upgrade by myself.

@woefull At first I tried Ubuntu 18.04 but when the script failed, I downgrade it to a have chance of working in the lower version

Now, I am curious. Did you tweak the existing scripts by hand to rebase on Ubuntu 18.04 or are you going through the tasks manually. What do you think is the best approach, if something makes sense I might try an Ubuntu LTS 20.x just for fun.

Hello everyone,
I tried to get a new server created from an Ubuntu 20.04LTS builder to an Ubuntu 20.04LTS target on digitalocean.
To try that, the only thing needed is to change the defaults in the genesis-digitalocean role to refer to the new public image name.
I did and I gave it a try... I got a nice warning that the install would probably fail since the target server was not 16.04 but continued anyway.
Well, I was a bit disappointed but not surprised when it failed and I was even less surprised at the first task that failed. The infamous GPG thing.
The precise task that failed was: wait for the gpg agent and dirmngr control sockets...
Now, if not for the time out, I would have waited forever, it failed at that point.
If anyone has a clue as how to upgrade the script to handle the right version of GPG for a newer distro, I would be willing to try it. I dont think there is a really good version of GPG but perhaps there is one that would work just enough.

Also, the droplet got created and updated just fine on digitalocean... so that portion still works well.
That's if for now.
Have fun everyone.

Woefull

Was this page helpful?
0 / 5 - 0 ratings