Error in tightvnc viewer no security types supported server sent security types

Error in tightvnc viewer no security types supported raspberry

So I did an update today on my Pi 3 running Raspbian. Now when I try to connect to it using VNC from my PC, the VNC viewer goes «No matching security types». That’s with RealVNC. I get the same error when running vncviewer in Solaris 10. If I try TightVNC on the PC, I get «No security types supported». Oddly enough, the VNC Viewer app for Android works fine.

I tried restarting the Pi’s vncserver with «vncserver -Encryption AlwaysOff» but that didn’t help. There seems to be no shortage of questions about this error on the web, but no answers that helped. I searched the forum here and came up empty. Does anyone know what the problem is here?

Re: VNC viewer: «No matching security types»

For the benefit of anyone else with this problem, here’s the solution.

Using the Android VNC Viewer app, I was able to open a connection to the Pi. From there I opened the VNC server window. From there I went to the Options menu, set Authentication to «VNC password» and Encryption to «Prefer off». I then clicked OK and that was that. I can now log into the Pi using RealVNC and TightVNC from my PC’s again.

Re: VNC viewer: «No matching security types»

Languages using left-hand whitespace for syntax are ridiculous

DMs sent on https://twitter.com/DougieLawson or LinkedIn will be answered next month.
Fake doctors — are all on my foes list.

The use of crystal balls and mind reading is prohibited.

Re: VNC viewer: «No matching security types»

Re: VNC viewer: «No matching security types»

Re: VNC viewer: «No matching security types»

Re: VNC viewer: «No matching security types»

Re: VNC viewer: «No matching security types»

You can use following steps:
Step 1: If you have VNCServer already running just kill it. Use «vncserver -kill :windowNumber». You can find your window number in the raspberry pi terminal. Generally, you can use 1.

Step 2: Now you should start your VNCServer by the following command «vncserver -Encryption PreferOff -Authentication VncAuth». Hit Enter.

Step 3: This would also prompt you to provide the password just enter a simple one like «raspberry».

Step 4: Go to the VNC Viewer client on your client PC. Enter the IP address of your Raspberry Pi followed by the display number. Ex: «192.168.43.0:1» Click on Connect. Enter the specified password. And you are logged into your VNCServer.

Источник

Error in tightvnc viewer no security types supported raspberry

Brand new raspberry pi user.

Got my pi4 set up with VNC and I can access it perfectly fine via my PC, however for the life of me I can’t get the resolution fixed.

I’ve followed all youtube videos around forcing HDMI via config.txt, setting resolution in raspi-config but I can’t get it to boot up with any changes acted upon.

Any help would be greatly appreciated.

Re: VNC Resolution

What does your config.txt file look like?

Re: VNC Resolution

For some reason raspi-config now only changes the resolution of the initial boot screen and not the desktop.

I now have to use the GUI Screen Layout Editor to change the desktop resolution.
[Menu] —> [Preferences] —> [Screen Configuration]
Don’t forget to [Apply] after changing resolution.

Re: VNC Resolution

Re: VNC Resolution

I would recommend using the edid options, specifically hdmi_edid_file:
https://www.raspberrypi.org/documentati . t/video.md

This way you could be able to save the EDID information and keep the same resolution settings.

Re: VNC Resolution

I’m using tightvnc and I found that I could easily change the resolution when loading the server.
e.g.
tightvncserver :1 -geometry 1600×900

it can be loaded in your rc.local

Re: VNC Resolution

@lugee
I’m not sure I follow you. When I connect the Raspi to my TV, the resolution always is at 1920x1080x60, even when it’s plugged in after boot. However, when I want to configure the Raspi from my laptop (1366×768) or my PC (1920×1080) without being connected to the TV, I would like to do so via VNC and a resolution of 1280×720. Are you saying the edid file also influences the resolution of the virtual desktop?

@madoglee
I’m using Real VNC server that comes with Raspian (Buster) out of the box without any tweaks. When I connect with TightVNC viewer, I get this message:

—————————
Error in TightVNC Viewer: No security types supported. Server sent security types, but we do not support any of them.
—————————

which is why I have used RealVNC viewer instead. Dunno o

Re: VNC Resolution

If it’s a virtual desktop, then the EDID file won’t influence the resolution. A loaded EDID file will let the Raspberry Pi pretend that the same monitor/tv is always plugged into the Pi, even though that may not be the case. When I started my Pi without a monitor and without this file, RealVNC doesn’t work for me.

I’ve tested two different solutions, depending on which solution you prefer:

When VNC is mirroring a real screen, you can alter the resolution with the following command in the terminal within the VNC session:

Re: VNC Resolution

Thanks, my home dir looks like this though:

which is empty and

which is empty too.

Re: VNC Resolution

Re: VNC Resolution

Re: VNC Resolution

Thanks but since VNC starts flawlessly when connected to an HDMI port, I’m sure it’s no path issue. Still, I’ve entered the absolute path in rc.local and it makes no difference: the Raspi shows ‘cannot currently show the desktop’. After a reboot with the HDMI cable plugged in, I can connect to VNC from my Win PC immediately.

EDIT: Adding hdmi_force_hotplug=1 to /boot/config.txt did the trick. Headless will start in 1280×720 and when plugged in to a TV it will start with 1920×1080 as set via raspi-config.

Re: VNC Resolution

I’ve got one issue left though: say I boot up headlessly and get the 1024×768 resolution (instead of the 1280×720 I actually set in /etc/rc.local) when I connect with vncviewer. Now I want to change this to 1920×1080 cause I’m working from my PC with a FullHD monitor instead of my laptop. So in vncviewer I click ‘Raspberry icon > Preferences > Screen Configuration > Configure > Screens > HDMI-1 > Resolution’ where I can only select

1024×768
800×600
848×480
640×480.

Typing ‘xrandr -s 1920×1080’ yields ‘Size 1920×1080 not found in available modes’ and typing ‘vncserver -geometry 1920×1080’ opens a new instance on screen 2 which requires me to log in there. And when I start Chromium on screen 2 it actually starts on screen 1!

Any idea how to fix this?

Re: VNC Resolution

I’ve got one issue left though: say I boot up headlessly and get the 1024×768 resolution (instead of the 1280×720 I actually set in /etc/rc.local) when I connect with vncviewer. Now I want to change this to 1920×1080 cause I’m working from my PC with a FullHD monitor instead of my laptop. So in vncviewer I click ‘Raspberry icon > Preferences > Screen Configuration > Configure > Screens > HDMI-1 > Resolution’ where I can only select

1024×768
800×600
848×480
640×480.

Typing ‘xrandr -s 1920×1080’ yields ‘Size 1920×1080 not found in available modes’ and typing ‘vncserver -geometry 1920×1080’ opens a new instance on screen 2 which requires me to log in there. And when I start Chromium on screen 2 it actually starts on screen 1!

Источник

TigerVNC viewer: no matching security types

I’m trying to remote control the desktop of a Raspberry Pi (Raspbian Jessie) from a Samsung Chromebook (ARM Arch Linux).

The VNC server running on the Pi is RealVNC.

The VNC viewer on the Chromebook is TigerVNC

I’m getting the following error when I try to connect to the server:

As far as I understood by reading the man pages, vncviewer attempts by default every supported scheme:

Does RealVNC use some encryption scheme that is not supported by TigerVNC?

2 Answers 2

Using RealVNC

As user rodrunner suggested in the comments, one way to get the VNC connection going is by using RealVNC’s vncviewer .

Make sure to uninstall TigerVNC or any other VNC implementations before proceeding.

The package of RealVNC viewer is currently in AUR, you can install it via aura :

Assuming your Raspberry Pi’s host name is the default, connect to it with

You’ll be prompted for your Raspberry Pi’s login credentials:

Press OK and you should be connected:

Caveat

On their company blog, RealVNC published an article on May 28th, 2019 titled «The Dangers of Open Source VNC-based Software». The article claims that proprietary software is superior to open source software in terms of security, support, regulatory compliance, and user-friendliness.

In combination with TigerVNC’s incompatibilities with other VNC implementations, it seems to be an attempt at vendor-lock in, making me steer clear of TigerVNC.

The blog article used to be at https://discover.realvnc.com/blog/the-dangers-of-open-source-vnc-based-software , was since taken down, but a version from September 3rd, 2020 can still be accessed via this Wayback Machine entry.

Here’s the full blog article:

The Dangers of Open Source VNC-based Software

Author: Eden Jefford | 28 May 2019

Everybody loves a freebie, from a sample of chocolate at the mall to a promotional stress ball, but is it always a good idea? When it comes to sweets and sundries, we’re not going to stop you unless you’re taking them from a stranger in a van, but for software, there might be more risks than you think.

While the “stranger in the van of candy” scenario presents fairly obvious risks, using an open source program with no price tag can seem on paper much less dangerous. It does the job you need it for, doesn’t break your budget, and it has glowing reviews from people who greatly appreciate its most attractive feature: not costing any money – what could go wrong? We’ve put together a list of a few good reasons why open source VNC-based software can be a wolf in sheep’s clothing. Publicity of exploits

Open source at its core means that all the code behind the program is visible for anyone on the internet. This can work out great when bugs arise – lots of passionate eyes on the code means potential issues could be spotted quicker, and therefore patched quicker – but it can also pose a very real security risk for those using the program. While most users in the community will be purely focused on improving the software, some will be examining the code for ways to exploit and hack into any vulnerabilities.

Especially with remote access software, a well-placed hack can be devastating, and expose whole networks to the hacker without them needing to be anywhere near your computers in person. However, with closed source (also known as proprietary) software, the source code is not published outside of the organization with the rights to it.

This makes it far less vulnerable than open source, as not just anyone can scrutinize the code, therefore making it much more difficult to crack into. Think of it like trying to complete a 10,000-piece jigsaw in the dark – it’s still technically possible to do, but it’ll be a lot easier if the light is on!

Lack of support

While a community with a broad range of skills and expertise can be great for finding solutions to problems you’re encountering, it can also have its downsides. Every user on a support forum for open source software is a volunteer. They have no obligation to respond to queries, or to even check for new questions in the first place.

This means that you’re fully reliant on the goodwill of the internet to provide support, and when using the software is critical for your business, that can mean not only lost time, but lost revenue too.

With proprietary software, you can pick up the phone, send an email, or use a live chat knowing that a dedicated and highly trained person will get back to you as soon as possible, and do everything they can to help: in fact, helping you solve a problem is literally their job. Additionally, customer service agents are made accountable for the advice they provide – on a forum, an anonymous username can very easily give deliberately wrong or harmful ‘advice’ with no consequences.

Indemnity

Data breaches are unfortunately an ever present risk, and there seems to be a new one in the news every other day. Especially with recent data protection laws, such as the GDPR for those doing business in Europe, the repercussions for such leaks can also be catastrophic.

As open source software isn’t owned by anyone, and is offered under a General Public License (GPL), there isn’t a company to guarantee for its security (or lack thereof). If a data breach happens through that software, it’s all on the user, aka you or your business. You would be responsible for any legal or financial impact the leak causes, the fallout of which could be considerable depending on the size of the breach and the sensitivity of the data exposed.

Even if your company has professional indemnity insurance, if you are using software that is not secure and compliant with data protection regulations in your industry, your insurance can be rendered invalid due to willful negligence. Not to mention the reputational damage.

Compliance with industry governance

Compliance is a great concern for many industries, with many having very specific requirements in order to meet the necessary standard, be it HIPAA, PCI-DSS, GDPR, or any other regulatory laws. With records now being almost entirely digital, it is more important than ever for software to comply with industry governance, and not all software is going to fit the bill.

Open source software can be added to by anyone, with no thorough testing or vetting, and is not compliant with regulations by default. This not only negates the savings of using free software by requiring custom code (skillful coders aren’t cheap!) but can also leave you vulnerable through a lack of updates.

For instance, open source VNC-based software runs on the last publicly available release of the RFB (Remote Frame Buffer) protocol – v3.8, which came out in 2010: to put it into perspective, the current version of RFB is v6, and was released in early 2019.

Technology has moved at lightning speed over the last decade, and regular updates are vital to keeping software secure. Using a highly outdated version of any software can be dangerous when it comes to security, and fines for non-compliance with standards can be considerable. Can you afford to take that risk when you really don’t need to?

Low level of security

Brute force password attacks are still the easiest way hackers can gain access to your accounts and data, as many people use simple passwords that are very quick for an automated program to crack, especially with so many cracked passwords circulating on the internet.

Using longer and more complex passwords along with Multi-Factor Authentication (2FA/MFA) are the best ways to combat this vulnerability, but with open source VNC-based software, passwords have a hard limit of 8 characters, and there is no native 2FA/MFA. Open source VNC-based software does not encrypt any session data, but on proprietary software all sessions are now 128/256-bit AES encrypted. This is again due to the outdated version of the RFB protocol mentioned earlier, and is probably the most dangerous part of open source VNC-based software on this list.

Using proprietary remote access software, security tools are built in and updated regularly, as security is the biggest concern within the remote access industry. High levels of encryption, complex password capabilities, 2FA/MFA, and rich session permissions are now built in as standard with many paid remote access services, giving you and your company peace of mind you just can’t get with open source.

Not user friendly

Open source projects are primarily built and updated with only developers in mind, so the usability for people less technologically savvy can suffer considerably. From clunky and confusing user interfaces, to complicated installation and setup, they just aren’t designed to be used by the layman.

This can result not only in a poor experience for the user, but also in additional vulnerabilities. With a baffling UI, an inexperienced user could easily end up giving access to unauthorized people, getting stuck in strange glitches, and opening a portal to the underworld, all in a single session.

Open your eyes, not your source!

Consider the total cost of ownership (TCO) rather than the upfront cost – while free is appealing, it could easily end up costing much more than a paid service in the long run. Your business is worth the investment, and the freeware is not worth the possible risks.

Источник

Symptoms

While trying to access Mac Client via TightVNC in SCCM Console the error occurs:

Resolution

On the Mac do the following:

1. Open Sharing preferences if it isn’t already open (choose Apple menu > System Preferences, then click Sharing), then select the Remote Management checkbox.

2. Do one of the following:

   • Select “All users” to let all users on your network connect to your Mac using Apple Remote Desktop.

   • Select “Only these users,” click Add , then select the users who can share your Mac using Apple Remote Desktop.

3. Click Options, then select the tasks remote users are permitted to perform.

4. Click Computer Settings, then select options for your Mac. If people connect using a VNC viewer, you need to set a password.

If there were active VNC sessions on the Mac, you may need to restart it to apply the changes.

For more information, please refer to: OS X Yosemite: Allow access using Remote Desktop

Return to “Troubleshooting”

В предыдущем посте, я писал про доступ по SSH, пришло время «прикрутить»  удаленный доступ по VNC.

По умолчанию сервер VNC уже присутствует на борту. Нужно разрешить доступ к удаленному рабочему столу и поставить службу в автозапуск.

На компьютер под виндой ставим VNC клиента:

—TightVNC https://www.tightvnc.com/download.php 

—Ultra VNC

-Или еще какой-либо аналог

И пробуем подключиться по порту 5900 (по умолчанию порт именно такой). Вроде все просто, но подключения не происходит: «No security types supported. Server sent security types, but we do not support any of their » в этом случае:

1) $ sudo apt-get install dconf-editor
2) $ dconf-editor
org > gnome > desktop > applications > remote-access
3) снимаем флаг напротив «REQUIRE-ENCRYPTION»

Снова пробуем подключиться VNC клиентом:

Подключение установлено, но на этом медленном ноуте, мне не понравилась, как работает штатная оболочка (она «тупит» также, как и та винда, которая ранее была установлена здесь же).

В этом случае нам будет полезна легковесная модульная среда xfce: https://xfce.org/

«Прикручиваем» ее:

Sudo apt-get install xfce4-session xfce4-goodies

После перезагрузки ноут стал значительно шустрее… Пока устанавливалась новая оболочка, вместо штатного VNC сервера, решил установить проверенный временем на freebsd- x11vnc.

Для этого можно запустить скрипт: vnc-startup.sh

http://linuxway.ru/pervye-shagi/komanda-chmod-primery-ispolzovaniya/

Предварительно дав файлу права на запуск: chmod +х vnc-startup.sh (или добавить права через графический интерфейс) и запустить из командной строки следующий скрипт:

sudo apt-get install x11vnc -y

sudo x11vnc -storepasswd /etc/x11vnc.pass

cat > /lib/systemd/system/x11vnc.service << EOF
[Unit]
Description=Start x11vnc at startup.
After=multi-user.target

[Service]
Type=simple
ExecStart=/usr/bin/x11vnc -auth guess -forever -loop -noxdamage -repeat -rfbauth /etc/x11vnc.pass -rfbport 5900 -shared -permitfiletransfer

[Install]
WantedBy=multi-user.target
EOF

echo «Configure Services»
sudo systemctl enable x11vnc.service
sudo systemctl daemon-reload

sleep 5s
sudo shutdown -r now

После перезагрузки проверяем, что все успешно установилось и работает:

В целом все работает…

Пробуем подключиться уже к новому VNC серверу, подключение успешно, это же можно наблюдать и в командной строке

Далее устанавливаем необходимый нам TeamViewer

В итоге, получаем доступ по: SSH, VNC, TeamViewer.

После этого уже имеет смысл приступить к установке аналогов виндовых программ под Linux, но это тема уже следующего повествования…

Продолжение следует.

Всем хорошей работы!!!

31.10.2017 —

Posted by |
linux and unix servers