0

I have a TigerVNC 1.8.0-1 session running on my Linux machine for over 2 years. I've created several tabs and windows running all over the desktop. Needless to say, I do not wish to terminate this session.

Work environment is changing the connectivity to my VNC server. I tested their new connectivity and had multiple failures and Auth failures reaching my VNC session. All the IPs from their connection endpoints are now blacklisted in the running VNC session. I found this when looking at the VNC session log file. After working with the networks team, I was able to get their new connectivity to work with a new VNC session. So, I know that new sessions now are able to connect.

Question is: how can I "fix" the existing running session to whitelist IPs or remove the blacklist? I hate to tear down this session. The session has BlacklistTimeout=5 and BlacklistThreshold=10 (standard defaults). These variables are not modifiable during the running session.

Improve this question
2
  • Oh! That version of TigerVNC is 8 years old! hm, unlikely it can do these changes at runtime. Two observations: Commented Nov 28 at 11:43
  • 1. I sympathize! I hate tearing down my workplace. 2. But I do also know that I need to at some points. It might be much easier to structurizedly note down what you had open, and recreate that, than to solve the TigerVNC issue, though. You're using this probably on a RedHat 7 derivate (I guess, because I recognize the ancient version!); your whole system is end-of-support, most likely. If you don't start planning for how to recreate your "comfortable" session, the system will at some point schedule downtime for you. Commented Nov 28 at 11:47

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.