You are not logged in.
Pages: 1
* AFAIK the OpenVPN service runs every config file in the /etc/openvpn/ directory. It is only capable of running config files from this directory. So in order to switch between different VPN's it is necessary to switch config files around. This is not the case on Debian. On Debian OpenVPN can be controlled per config file.
systemctl start openvpn #starts all config files systemctl start openvpn@name_of_config_file #starts name_of_config_file
I dont think this is a good example. I'm pretty sure that name_of_config_file must be also present in /etc/openvpn/. At least I would suggest this from https://salsa.debian.org/debian/openvpn … n@.service.
I consider your Debian example pretty equal to the following Devuan command:
openvpn --daemon --config /etc/openvpn/name_of_config_file.conf
Rootless VPN Management for Desktop users is most likely achieved by network-manager package. But network-manager is also available on Devuan - actually the same package as in Debian.
Nevertheless, please feel excited to extend WiCD. Its an alternative to network-manager and alternatives are always welcome.
Ok, session permissions seems to be OK. Im stumbling across
Jan 18 01:02:48 shook3r nm-openvpn[3642]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
and later
Jan 18 01:03:48 shook3r nm-openvpn[3642]: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
I think the permissions of /home/matteol/.local/share/networkmanagement/certificates/it.protonvpn.com.udp/tls_auth.key need to be 0600. (You can change that using chmod). Also it might be required to manually copy tls_auth.key to /home/matteol/.cert/. See
https://ask.fedoraproject.org/en/questi … pn-server/
If you have selinux installed, maybe this applies too. (But please check other things first)
https://unix.stackexchange.com/question … es-on-cert
On terminal it won't work as normal user because modifying network settings usually requires root permissions. By gui it should work indeed, since network-manger daemon itself runs with root permission and the gui should forward all requests through d-bus to the daemon. Can you please provide the exact error message or problem with KDE gui?
In the meanwhile, please check that elogind, libpolkit*elogind and polkit is installed. (Re-login if you had to install one of these) Then please run:
$ loginctl
should show a list of session (one probably). From that list get session number and run
$ loginctl show-session <session number here>
and post output of that command here.
If you had to install one of the packages above, please try again configuring the vpn through gui. (After re-login!)
As some of you maybe already noticed, there is ongoing work for creating an fully opensource and free mobile phone plattform:
https://puri.sm/products/librem-5/
While the vendor will provide a Debian based linux distribution "Pure Os" to run the phone, the opensource nature of the project will allow to use virtually any operating system with the phone.
The development kits for the phones are out now and there has already been some work to make Devuan images for these development kits.
Daniel Albrecht has created a shell script based image generator for Devuan, find it here:
https://gitlab.com/DanielAbrecht/librem5-image-builder
I can not tell much more about it
and I have made another one, based on the "ansible" tool here:
https://gitlab.com/amesser-group/librem … ge-builder
My image is a little different to original Puri SM image in the following points:
Devuan based
Kernel recompiled with much more filesystem and network filesystem options enabled
Using f2fs instead of ext4 for root partition (hopefully extends lifetime of eMMC)
The images can be readily used with the Librem 5 Development kits.
The Display is currently not working due to initialization issues. However a HDMI monitor can be connected instead.
Images bigger 4GB wont flash properly on the phone. (This took me some days to figure out) Not yet clear if this is an issue of the used u-boot version or NXP's software "mfgtools" required for flashing.
Network link might go down even if cable plugged after some uptime. Looks like a timing issue in ethernet driver of kernel
Bootup takes about two minutes, most of the time waiting for random number generator initialization
Purism has already spent some effort to build an gui interface for the phone. This software is available as .deb packages (and source of course). Some of these software packages need porting to Devuan. (mainly remove systemd dependencies)
Source code repos of Purism for Librem 5 https://source.puri.sm/Librem5
Any feedback is appreciated.
The (main) problem with building packages on different distributions is, that typically different distributions will have different versions of libraries. Depending on how stable the interface of such an library is, the executable might/will only work with particular versions of an library.
Therefore the dpkg builder usually grabs the version numbers of the libraries the package was build with and insert this version information into the built .deb files as requirement. So it can happen, that a source package can be build without problems on different distributions, but the resulting binary packages wont install or work on other distributions than they were built for.
These "oc" prefixed packages do not exist on Devuan, neither on Debian. Don't know how the owncloud package has been tested to work with Debian. I suggest "oc" stands for "owncloud" so I suggest these files are some OwnCloud internal packages.
I suggest you to rebuild the latest owncloud package by yourself from git repos. This is kinda back porting a package by yourself.
The workflow is something like this - roughly tested on devuan ascii:
$ sudo apt install git build-essential dpkg-dev devscripts
$ git clone https://salsa.debian.org/owncloud-team/owncloud-client.git
...
$ cd owncloud-client
$ git checkout debian/2.5.1.10973+dfsg-1
$ git checkout -b my_build
$ dch -l~mybuild # <- will pop up an editor, just save and close
$ sed -i 's/--with sphinxdoc//' debian/rules # <-- fix problem with doc build
$ dpkg-buildpackage -b # <- will most likely fail with missing packages (reported to terminal)
...
$ sudo apt install <missing packages>
...
$ dpkg-buildpackage -b # <- will build now, takes some time
...
$ ls ../*.deb # <- parent dir should now contain all required debs to install
Pages: 1