网站的安全性建设,网站建设系统设计报告,网站怎么找开发公司吗,wordpress配置文件背景#xff1a;因为某些原因需要从本地mac连接远程linxu桌面查看一些内容#xff0c;必须使用桌面查看#xff0c;所以ssh无法满足#xff0c;所以决定安装vnc客户端。
问题#xff1a;
在mac上通过 brew install tiger-vnc命令安装, 但是报错如下#xff1a; D…背景因为某些原因需要从本地mac连接远程linxu桌面查看一些内容必须使用桌面查看所以ssh无法满足所以决定安装vnc客户端。
问题
在mac上通过 brew install tiger-vnc命令安装, 但是报错如下 Downloading https://raw.githubusercontent.com/Homebrew/homebrew-core/555c288aed70eaa4fa9dcf3bd37a1fbca3f69a00/Formula/lib/libpng.rb
Already downloaded: /Users/xxxx/Library/Caches/Homebrew/downloads/e334b6d4753af38f07dcbd30e22cd79df1d2b2c61cd4ac212c64559271884d04--libpng.rbDownloading https://downloads.sourceforge.net/project/libpng/libpng16/1.6.44/libpng-1.6.44.tar.xz
################################################################################################################################################################################ 100.0%curl: (35) error:06FFF089:digital envelope routines:CRYPTO_internal:bad key lengthTrying a mirror...Downloading https://sourceforge.mirrorservice.org/l/li/libpng/libpng16/1.6.44/libpng-1.6.44.tar.xz
curl: (6) Could not resolve host: sourceforge.mirrorservice.org
Warning: Problem : timeout. Will retry in 1 seconds. 3 retries left.
curl: (6) Could not resolve host: sourceforge.mirrorservice.org
Warning: Problem : timeout. Will retry in 2 seconds. 2 retries left.
curl: (6) Could not resolve host: sourceforge.mirrorservice.org
Warning: Problem : timeout. Will retry in 4 seconds. 1 retries left.
curl: (6) Could not resolve host: sourceforge.mirrorservice.orgError: tiger-vnc: Failed to download resource libpng尝试的解决办法
在stackoverflow有类似的curl: (35) error:06FFF089:digital envelope routines:CRYPTO_internal:bad key length 但是根据该方法无法解决我的问题。 linkhttps://stackoverflow.com/questions/69734654/fixing-git-https-error-bad-key-length-on-macos-12 该link给的方法是export CURL_SSL_BACKEND“secure-transport”
再次尝试修改brew缓存目录内容将下载的libpng-1.6.44.tar.xz直接放入到cache目录通过brew --cache 获取cache目录信息依然报相同的错误。
最终解决办法
升级mac os版本 我的版本是12.1 直接升级到了12.7.6 问题解决
为什么选择升级os因为stackoverflow的帖子写的该问题时有一段描述macOS 12.3 was officially released on march 13th, 2022 and the issue reported on this question has been fixed. Personally I have removed the workaround I had deployed and I suggest others do the same to keep up with the new versions.
而我的mac版本是12.1所以最后决定升级当时12.x系列中可用的版本是12.7.6 就升级到12.7.6
