Budget: 1000 UAH Deadline: 1 day
Good time of day. Feel free to contact me, I will do it *on the go* - ifupdown+iproute2
Requirements:
- The bridge configuration must be persistent and activate on boot.
- The configuration should be based on iproute2 or network-manager/nmcli or another method, if it is not deprecated (for example, brctl is deprecated)
- The bridge must be configured under Debian Linux 9 (which is deprecated).
Regarding the bridge:
- it must connect two physical Ethernet ports
- it must be assigned two IP addresses from different networks
(for example, 192.168.111.0/26 and 192.168.111.64/26)
- STP must be disabled
- As a quick solution, the IP addresses can be hardcoded.
- In the second step, it would be good if we could parameterize the IP address easily (for example, using a configuration file).
Result:
- The result should be either a series of commands to execute manually (or in a script), or a set of configuration files (possibly), located in the /etc directory.
Budget: 1000 UAH Deadline: 1 day
Good time of day. Feel free to contact me, I will do it *on the go* - ifupdown+iproute2
Budget: 1500 UAH Deadline: 1 day
Hello.
I am ready to help with your issue.
For details - please contact me privately, I will be waiting for your feedback.
Who can help set up such a setup: I plan to deploy a server that will work in parallel with 4–5 different AI models for programming tasks. The key requirement is multi-user access: several developers will be able to use the server simultaneously, each in an isolated session with their own agents. Models Claude / GPT / Kimi k3
As part of enhancing the cybersecurity level of our infrastructure, we need to abandon the practice of storing "eternal" and static API keys, passwords, and integration tokens in the configuration files (.env, appsettings.json, config.yaml) of our microservices. Business Goal: Create a single secure storage point for confidential data (secrets) with a mechanism for their automatic updating (rotation) in external systems on a schedule. Our other services will request current tokens "on the fly" via API, which will minimize damage in case of compromise of any system component.Security Model and Encryption (Crypto Core) No secret should be stored in plaintext in the database. Upon application startup, a Master Key is passed to the environment variables. If the key is missing or has an invalid length, the service should fail at the initialization stage with a clear error in the logs. Each secret is encrypted before being written to the database using this Master Key. Upon request, it is decrypted in memory and returned in the response body.Audit Logging (Audit Trail) Any action with secrets (creation, reading by the service, successful or unsuccessful rotation) must be recorded in a separate log file audit.log (or a separate table in the database). Strict Taboo: It is strictly prohibited to record the actual values of secrets in the audit log (neither in plaintext nor in encrypted form).
We have a dedicated server on Hetzner with a website on Docker (+ Laravel framework) Contact with the developers has been lost Need to: - restore and change server access (probably SSH) - recommend a storage location and set up a full server backup with easy recovery, probably not on Hetzner for security - fix the logo that is not displaying for some reason (it's unclear why the file has become inaccessible) Important - there is no website backup, and there is no room for error. We will only consider experienced specialists.