lebt in Zürich, ist System Engineer MCP bei A-Enterprise GmbH. Mitglied des UNBLOG Network. Author und Blogger zu den Themen, Linux und Open Source. Tutorials für Windows, VMware, Synology, Fortinet.
Regjump takes a registry path and makes Regedit open to that path
Registry editor (regedit.exe) is known not to be particularly comfortable, but the Registy Jump utility offers simplification. Microsoft has made hardly any changes to the now old-fashioned windows tool in recent years.
In addition to the search function, the Registry Editor does not offer a direct way to jump to a specific key in a path, which is especially annoying if you have to hail through a particularly long registry key.
However, the Regjump utility jump to a specified registry path. Microsoft offers from the Sysinternals collection a free tool called Regjump, which can be downloaded here.
Regjump Path
The small command line applet takes a registry path and opens Regedit for that path. It accepts root keys in the standard form such as: HKEY_LOCAL_MACHINE and in short form with HKLM.
Particularly helpful is to paste a key path from the clipboard with the option -c (Copy path from clipboard).
Regjump takes the registry path and opens Regedit to the path
Conclusion
Most Windows users have dealt with the Windows Registry at some point. Endless possibilities are available to the Windows administrator to adapt the Windows system to the needs by making certain changes in the Windows registry. Unfortunately, the registry editor (regedit.exe) is not particularly user-friendly and unfortunately Microsoft has hardly changed anything in the somewhat dusty editor in recent years.
Firefox Sync Server running self-hosted, for bookmarks available synchronously on any device, including the timeline, tabs, add-ons, settings, and credentials, which can be matched on request.
The Mozilla-hosted Firefox account server can be easily used in combination with a self-hosted synchronization server and storage. Authentication and encryption protocols are designed so that the account server does not know the user’s plaintext password and therefore cannot access the stored synchronization data.
This tutorial shows how to install Firefox Sync Server (Sync 1.5 server) on Apache and Ubuntu 16.04.4 LTS. The Ubuntu server, here sync.server.net as an example, is accessible via the Apache 2.4 web server on the Internet.
Firefox Sync Server Installation
Prerequisite for Sync 1.5 servers is Python 2.7 and Python Virtualenv, python-dev, make, git, as well as the C and C++ compiler. To ensure this, the following pacts will be made available:
The Firefox Sync Server is configured using the ini file to pass different runtime settings. The syncserver .ini file serves as a starting point.
Most settings can be applied before the sync server runs, the URL that can be reached for clients must be adapted to the sync server. For productive use, we open the syncserver .ini file and edit the public_url:
$ vi /opt/syncserver/syncserver.ini
[syncserver]
public_url = https://sync.server.net/
Change the public_url from localhost:5000 to our sync.server.net. In another section, the configuration is set up on the HTTPS protocol.
Then adjust the sqluri for our data beacon:
sqluri = sqlite:////opt/syncserver/syncserver.db
A secret key with the random generator is generated from a terminal, running the following line:
$ head -c 20 /dev/urandom | sha1sum
60bev0b7bd2f56dxea3794fb97f03c824e70e21d
Enter this key generated in the syncserver.ini file:
secret = 60bev0b7bd2f56dxea3794fb97f03c824e70e21d
Assign enough rights to the database:
chmod 660 /opt/syncserver/syncserver.db
Create automatic start in systemd for Firefox Sync:
Now the Let’s Encrypt certificate can be created, certbot makes it easy for us, the SSL configuration required for our virtual host is created automatically.
$ certbot --apache -d sync.server.net
Under /etc/apache2/sites-enabled is now the symlink of this to file sync.server.net-le-ssl.conf shows, this is stored under/etc/apache2/sites-available.
$ ls /etc/apache2/sites-enabled/sync.server.net-le-ssl.conf
/etc/apache2/sites-enabled/sync.server.net-le-ssl.conf
In the file sync.server.net-le-ssl.conf, the WSGI configuration still needs to be added, we edit sync.server.net-le-ssl.conf, which then shows the following content:
In order for Firefox to be able to synchronize via its own sync server, the URL must be changed, for this purpose you enter about:config in the address bar and confirm with the enter key.
After confirming the warning, enter identity.sync.tokenserver.uri into the search box.
Double-clicking changes the value to your own sync server https://sync.server.net/token/1.0/sync/1.5
Finally, the Mozilla account is created via the following URL:
https://accounts.firefox.com
The account itself is located on the Mozilla server, the data is stored on the own sync server.
It is important that the synchronization was made only after the entry to the own sync server in Firefox. If bookmarks and data are on the sync server with Mozilla, the data can be deleted, with the following command lines:
Note that the Let’s Encrypt certbot for validation, the Firefox Sync Server must be reachable via port 80, for the firewall included in Ubuntu in the default, the command is as follows:
$ sudo ufw allow http
When you call the Firefox Sync Server URL, or https://sync.server.net in the browser, the following output should appear:
$ curl -k https://sync.server.ent
it works!
If the Apache web server does not start, the syntax of the configuration can be validated:
$ apache2ctl configtest
Syntax OK
After all accounts have been created, access to other users can be blocked in the syncserver .ini file:
$ allow_new_users = false
The Firefox Sync protocol contains the debug information in case of errors and can be queried with the following command in the browser line.