鸡毛蒜皮

A great python to save keepass WSL user in windows If you are a keepass user, chances are that you are also a keeagent user, chances are that you are also a WSL user. You want all your passwords and ssh keys managed by keepass , and automatically served by the great keeagent plugin. As with putty, mobaxterm, git bash, win10 bundled OpenSSH all works well with trivial additional setup. You will expect the real OpenSSH inside your WSL environment to work as well. msysgit2unix-socket.py Get the tool and setup it in your WSL, and then you get it. Try ssh-add -l or ssh to any of your usual ssh target after restart your WSL terminal. https://gist.github.com/kevinvalk/3ccd5b360fd568862b4a397a9df9ed26

ssh-dss key not in PubkeyAcceptedKeyTypes 忙里偷闲鼓捣自建基于 Jekyll 的blog，发现无论如何都不能在心爱的linux里面通过ssh clone新创建的 git repository。 提示如下： Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. 遂坠入无限ssh检查中无法自拔： ssh-add -l 显示 ssh-keyagent 内容无碍 ssh-keygen -l -f 显示各个key的finger print 看不出错误 进入windows通过 git bash clone 失败，遂发现 windows 中 plink 太久未用，已经生锈。不认识 github 的 host key。用 putty github.com 弹出的新host key 对话框确认了事。 windows下终于clone成功。 再次尝试将 windows 下的ppk导出为openssh格式，遂发现几年前曾经有一份导出的 key 躺在那里…… 各种折腾之后拷贝的key诺到了linux中，以为万事大吉，结果，结果，结果虽然 diff -u 显示新来的 key 是新的，但是 ssh-keygen -l -f 说他们两个是一样的…… 无奈出下下策 ssh -vvvv git@github.com ，一阵垃圾滚屏过后终于发现 debug1: Skipping ssh-dss key /home/fktpp/.ssh/fktpp.openssh - not in PubkeyAcceptedKeyTypes Google 说 (keyword: Skipping ssh-dss key not in PubkeyAcceptedKeyTypes) stackexchange: ssh keeps skipping my pubkey and asking for a password The new openssh version (7.0+) deprecat...