bvnc

Browse for VNC servers

$ bvnc

$ bvnc --ssh

$ bvnc --shell

$ bvnc --domain [domain]

bvnc [options] host[::port | :display]
bvnc [options] connection-string

host
    The hostname or IP address of the VNC server to connect to.

:display
    The display number of the VNC server (e.g., :1 for port 5901). Defaults to :0 if not specified.

::port
    The specific TCP port number to connect to (e.g., ::5901). Overrides the display number if both are present.

-password file | prompt
    Specifies the password for authentication. It can be read from a file or prompted interactively.

-fullscreen
    Starts the VNC client in fullscreen mode.

-geometry WxH[+X+Y]
    Sets the initial window geometry (widthxheight and optional position) for the client window.

-viewonly
    Connects in view-only mode, disabling keyboard and mouse input to the remote server.

-share
    Allows other VNC clients to connect to the same display session (if supported by the server).

-encodings encoding-list
    Specifies the preferred VNC encodings to use, in order of preference (e.g., 'tight,hextile,zrle').

-compresslevel 0-9
    Sets the compression level for the VNC connection (0 for no compression, 9 for maximum).

-quality 0-9
    Sets the image quality level for lossy encodings (e.g., Tight or JPEG).

-via gateway
    Connects to the VNC server via an SSH tunnel through a specified gateway host.

The command bvnc is not a standard or commonly recognized command in most Linux distributions. It is highly likely that this name refers to a specific, niche, or custom script, or possibly a misspelling of other common VNC client commands like vncviewer, xtightvncviewer, vinagre, or remmina.

Assuming bvnc were a functional VNC client, its purpose would be to establish a connection to a remote VNC (Virtual Network Computing) server. VNC is a graphical desktop sharing system that allows users to remotely control another computer's desktop. A VNC client (like a hypothetical bvnc) receives the remote desktop's screen updates and sends local keyboard and mouse events back to the server, effectively allowing remote interaction with the graphical interface. Such a client would typically require the hostname or IP address of the VNC server and, optionally, a port number or display number, along with a password for authentication.

The primary caveat is that bvnc is not a standard Linux command. Users looking for VNC client functionality should instead use well-established commands like vncviewer (from various VNC packages like TightVNC, TigerVNC, RealVNC), xtightvncviewer, or graphical clients like vinagre or remmina.

If a custom script or application named bvnc exists on a specific system, its behavior, options, and security implications would depend entirely on its implementation. Standard VNC connections are often unencrypted, making them vulnerable to eavesdropping unless secured via an SSH tunnel or VPN. Always ensure connections are encrypted for sensitive data.

If bvnc was intended as a VNC client, you can install one using your distribution's package manager. For Debian/Ubuntu, try sudo apt install tigervnc-viewer or apt install xtightvncviewer. For Fedora/RHEL, use sudo dnf install tigervnc. Graphical clients like vinagre or remmina are often available through desktop environment menus or direct installation.

vncviewer(1), xtightvncviewer(1), vinagre(1), remmina(1), ssvnc(1), vncserver(1)