[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: Re: Arabic team coordinator
From: Abdalrahim Fakhouri <abdilra7eem () gmail ! com>
Date: 2012-01-01 22:44:30
Message-ID: CABS9rGt6GVcUxJEcUm0aONjsGqgewkXTaK9VpkotAWBhL3Chxg () mail ! gmail ! com
[Download RAW message or body]
On Sun, Jan 1, 2012 at 2:00 PM, <kde-i18n-doc-request@kde.org> wrote:
> Make sure the SSH key on your system exists and matches the one in KDE
> identity.
>
> First, run this command:
> ssh-keygen -lf ~/.ssh/id_*sa
>
> If that fails, you didn't set up SVN+SSH properly. Follow the
> instructions here to generate a key and configure SVN+SSH:
> http://techbase.kde.org/Contribute/Get_a_Contributor_Account#SSH
>
> Then, you can check it at identity.kde.org > Profile > Edit > Edit
> public ssh keys... If you do have a key, make sure the one there
> matches the output of the command you just ran. If it doesn't or you
> just generated a new one, upload the correct id_rsa.pub here. Then,
> make sure to click "Save" on that screen and then "OK" on the profile
> edit screen to save the changes, and then file a sysadmin request so
> the keys get changed on the server:
> https://bugs.kde.org/enter_sysadmin_request.cgi
>
> A sysadmin will let you know when your keys are fixed and then
> everything should work fine.
>
> I rechecked the fingerprint of that key, and it's good.
Everything else seems fine too!
> If your keys are set up properly, something strange might be going on
> with your connection/firewall/etc. Edit ~/.subversion/config,
> uncomment (remove the hash [#] marks from the beginning of) the "ssh =
> $SVN_SSH ssh -q" line in the "[tunnels]" section, and then remove the
> "-q" from the end. Save it, and try accessing KDE SVN+SSH again.
> That config file change will cause SVN to print some debugging
> information when trying to connect. If you can't make any sense of
> it, paste it in a reply here and maybe we can figure out what's going
> on.
>
> -T.C.
>
The line now looks like this:
ssh = $SVN_SSH ssh
Then, I went to the terminal and:
$ svn switch --username=fakhouri svn+ssh://
svn.kde.org/home/kde/trunk/l10n-kde4/ar/messages/kde-runtime
Bad owner or permissions on /home/myusername/.ssh/config
svn: To better debug SSH connection problems, remove the -q option from
'ssh' in the [tunnels] section of your Subversion configuration file.
svn: La connexion réseau a été fermée de façon inattendue
I checked the permissions in "/home/username/.ssh/", and they are:
-rw-rw-r--. config
-rw-------. id_rsa
-rw-r--r--. id_rsa.pub
----------------
A. Fakhouri
[Attachment #3 (text/html)]
<div dir="ltr"><br><br><div class="gmail_quote">On Sun, Jan 1, 2012 at 2:00 PM, \
<span dir="ltr"><<a href="mailto:kde-i18n-doc-request@kde.org" \
target="_blank">kde-i18n-doc-request@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
Make sure the SSH key on your system exists and matches the one in KDE identity.<br>
<br>
First, run this command:<br>
ssh-keygen -lf ~/.ssh/id_*sa<br>
<br>
If that fails, you didn't set up SVN+SSH properly. Follow the<br>
instructions here to generate a key and configure SVN+SSH:<br>
<a href="http://techbase.kde.org/Contribute/Get_a_Contributor_Account#SSH" \
target="_blank">http://techbase.kde.org/Contribute/Get_a_Contributor_Account#SSH</a><br>
<br>
Then, you can check it at <a href="http://identity.kde.org" \
target="_blank">identity.kde.org</a> > Profile > Edit > Edit<br> public ssh \
keys... If you do have a key, make sure the one there<br> matches the output of the \
command you just ran. If it doesn't or you<br> just generated a new one, upload \
the correct id_rsa.pub here. Then,<br> make sure to click "Save" on that \
screen and then "OK" on the profile<br> edit screen to save the changes, \
and then file a sysadmin request so<br> the keys get changed on the server:<br>
<a href="https://bugs.kde.org/enter_sysadmin_request.cgi" \
target="_blank">https://bugs.kde.org/enter_sysadmin_request.cgi</a><br> <br>
A sysadmin will let you know when your keys are fixed and then<br>
everything should work fine.<br>
<br></blockquote><div>I rechecked the fingerprint of that key, and it's \
good.<br>Everything else seems fine too!<br> <br></div><blockquote \
class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">
If your keys are set up properly, something strange might be going on<br>
with your connection/firewall/etc. Edit ~/.subversion/config,<br>
uncomment (remove the hash [#] marks from the beginning of) the "ssh =<br>
$SVN_SSH ssh -q" line in the "[tunnels]" section, and then remove \
the<br> "-q" from the end. Save it, and try accessing KDE SVN+SSH \
again.<br> That config file change will cause SVN to print some debugging<br>
information when trying to connect. If you can't make any sense of<br>
it, paste it in a reply here and maybe we can figure out what's going<br>
on.<br>
<br>
-T.C.<br></blockquote></div><br>The line now looks like this:<br>ssh = $SVN_SSH \
ssh<br><br>Then, I went to the terminal and:<br>$ svn switch --username=fakhouri \
svn+ssh://<a href="http://svn.kde.org/home/kde/trunk/l10n-kde4/ar/messages/kde-runtime">svn.kde.org/home/kde/trunk/l10n-kde4/ar/messages/kde-runtime</a><br>
Bad owner or permissions on /home/myusername/.ssh/config<br>svn: To better debug SSH \
connection problems, remove the -q option from 'ssh' in the [tunnels] section \
of your Subversion configuration file.<br>svn: La connexion réseau a été fermée \
de façon inattendue<br> <br>I checked the permissions in \
"/home/username/.ssh/", and they are:<br>-rw-rw-r--. \
config<br>-rw-------. id_rsa<br>-rw-r--r--. \
id_rsa.pub<br><br>----------------<br>A. Fakhouri<br> </div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic