Skip to main content

Release 0.7 of rport


🚀 New features:

  • Copy files from the server to clients with full control over the writable folders on the client. Read more
  • Scheduling of scripts with a central server-side scheduler for individual clients and groups. Read more
  • Client-side tunnel allow-deny rules. On the client configuration, you can define exactly where a tunnel is allowed to connect. See new options.
  • Tunnels can now be accessed on a different hostname than the API or UI achieving more flexibility when running behind a reverse proxy or Cloudflare. See new options.
  • Purging disconnected clients can be turned off now. You can keep them in your inventory forever. See new options.
  • You can specify which interface to use for tunnel connections on the RPort client. Useful if the remote machine has multiple network cards. See new options.

🔩 Improvements:

  • API listener accepts now TLS 1.3 only. The support for weak encryption has been discontinued.
  • Proper 404 handling on the static web server, no more HTTP status code 200 on “file not found”.
  • The Systemd service always injects ambient capabilities to bind privileged ports.
  • Emails and push messages with the two-factor token now include the user-agent and the remote IP address of the requester to better identify login attempts.
  • Migrated to a more secure JWT implementation. Read more
  • SQLite Write-Ahead Logging (WAL) is enabled by default for all databases to improve concurrent operations.


Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi