Re: [Savannah-users] SSH key change seems ineffectual

[Steve White]

Hi,

I found it.

Something went wrong when I pasted the RSA key into the field -- the
beggining and end looked the same as my key,
but in between something got pasted twice.

Sorry for the trouble.

On Fri, Apr 6, 2018 at 10:57 PM, Steve White <stevan.wh...@gmail.com> wrote:
> Hi Bob,
>
> I am trying to do commits from a new machine.  I added its SSH public
> RSA key on the Savannah web page (for GNU FreeFont project), but for
> hours, neither SVN nor CVS works for me.  Both are asking for a
> password.
>
> Have i forgotten something?  Or do key changes have to be authorized
> by somebody?
>
> Thanks!

Re: [Savannah-users] SSH key change seems ineffectual

[Steve White]

Hi,  I guess it's OK to send the results of your second test.
Something clearly goes haywire with the RSA offering, but I don't know why.
I've used this system to ssh to other machines locally and remotely --
this is the first problem I've seen.

ssh -v stevan_wh...@cvs.savannah.gnu.org hostname
OpenSSH_7.2p2 Ubuntu-4ubuntu2.4, OpenSSL 1.0.2g  1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to cvs.savannah.gnu.org [208.118.235.201] port 22.
debug1: Connection established.
debug1: identity file /home/swhite/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/swhite/.ssh/id_rsa-cert type -1
debug1: identity file /home/swhite/.ssh/id_dsa type 2
debug1: key_load_public: No such file or directory
debug1: identity file /home/swhite/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/swhite/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/swhite/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/swhite/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/swhite/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4
debug1: Remote protocol version 2.0, remote software version
OpenSSH_6.6.1p1 Trisquel_GNU/linux_7.0-1
debug1: match: OpenSSH_6.6.1p1 Trisquel_GNU/linux_7.0-1 pat
OpenSSH_6.6.1* compat 0x0400
debug1: Authenticating to cvs.savannah.gnu.org:22 as 'Stevan_White'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha...@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC:
 compression: none
debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC:
 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256
SHA256:qRLLJ4w/GAeiDyYnbx4yWJbZXwGiYYxgNty7lAfUyuM
debug1: Host 'cvs.savannah.gnu.org' is known and matches the ECDSA host key.
debug1: Found key in /home/swhite/.ssh/known_hosts:9
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS received
debug1: Skipping ssh-dss key /home/swhite/.ssh/id_dsa - not in
PubkeyAcceptedKeyTypes
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/swhite/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/swhite/.ssh/id_ecdsa
debug1: Trying private key: /home/swhite/.ssh/id_ed25519
debug1: Next authentication method: password



On Sat, Apr 7, 2018 at 12:57 AM, Bob Proulx  wrote:
> Hi Steve,
>
>> I am trying to do commits from a new machine.  I added its SSH public
>> RSA key on the Savannah web page (for GNU FreeFont project), but for
>> hours, neither SVN nor CVS works for me.  Both are asking for a
>> password.
>
> Looking in the logs doesn't show anything obvious.  Seems like it
> should be working.  I looked quickly at your ssh keys in the database
> and they looked okay.  Since you say you are working from a new
> machine then I suspect something there.  Perhaps permissions.  Usually
> permissions must not be group writable anywhere up the directory tree
> for example so be sure to check permissions.
>
>> Have i forgotten something?  Or do key changes have to be authorized
>> by somebody?
>
> Things should be working.  Try this as a simple test.
>
>   $ ssh stevan_wh...@cvs.savannah.gnu.org hostname
>
> You should see:
>
>   You tried to execute: hostname
>   Sorry, you are not allowed to execute that command.
>
> That means things are working.  But you might be seeing something
> else.  If so and the reason isn't obvious then try:
>
>   ssh -v stevan_wh...@cvs.savannah.gnu.org hostname
>
> You should see something like (this is from me):
>
>   debug1: Next authentication method: publickey
>   debug1: Offering public key: RSA 
> SHA256:ny9SZmnnLpUeTcmzt+pVpoxdH39AntZ+8Cb33tmCLzQ /home/rwp/.ssh/id_rsa
>   debug1: Server accepts key: pkalg ssh-rsa blen 279
>
> If you don't then something is wrong with the public key offer.
> Either permissions or something.
>
> Bob
>

[Savannah-users] SSH key change seems ineffectual

[Steve White]

Hi Bob,

I am trying to do commits from a new machine.  I added its SSH public
RSA key on the Savannah web page (for GNU FreeFont project), but for
hours, neither SVN nor CVS works for me.  Both are asking for a
password.

Have i forgotten something?  Or do key changes have to be authorized
by somebody?

Thanks!

Re: [Savannah-users] SVN commit problems

[Steve White]

Thanks, Bob!

On Thu, Nov 30, 2017 at 4:40 AM, Bob Proulx  wrote:
> Hi Steve,
>
>> This time the commit worked.
>
> Then I am sure this is a problem with the nfs lockd.  Rotating the
> file out of the way causes the problem to follow the original file and
> the new file works fine.  I have chased this problem before elsewhere
> and am sure that if we were to double blind this by rotating the saved
> off file back that the lock problem would return again.  This is a bug
> that has been around for a while.
>
> Interestingly enough the system was rebooted very recently for the
> lastest security kernel upgrade.  Which I just mention because it
> isn't a case of the system having been up for ages.  It was rebooted
> just two days ago.
>
>> Shall I still experiment with the test project?
>
> Not necessary now.  Since it is working for your project.  But if it
> had failed there then the test-project would have been a good
> comparison.
>
> I think things will be fine from here forward.  But if you encounter
> the problem again please let us know and we will work the problem
> again.
>
> Bob

Re: [Savannah-users] SVN commit problems

[Steve White]

Hi,

This time the commit worked.

Shall I still experiment with the test project?

On Thu, Nov 30, 2017 at 1:10 AM, Bob Proulx <b...@proulx.com> wrote:
> Hi Steve,
>
> Steve White wrote:
>> OK I tried it again.  Still not working -- it has hung:
>>
>> $ svn commit
>> Sending...
>> Transmitting file data ...done
>> Committing transaction...
>
> And that also shows a process stuck on it on the server side.
>
> root@vcs0:~# lsof | grep txn-current-lock
> svnserve  20468   Stevan_White4u  REG   0,24 
> 07003445 /net/vcs/srv/svn/freefont/db/txn-current-lock (vcs:/)
>
>> And nothing for several minuts.  Previously I killed the process and
>> tried again later -- this is when I saw the issue with the lock on the
>> server.
>> I have been committing the same way pretty regularly recently and this
>> thing just started happening yesterday.
>> And I saw it happen on a different system, when I committed something
>> from there.
>
> Sometimes the root cause is not immediately clear.  I tested to our
> test-project and I could commit okay.  I have a suspicion and tried
> something.  Please try it again now.
>
> (I hate to say before I know but I have seen the nfs lockd get into an
> odd state on individual files before.  This is tied to the inode and
> so tracks the physical file and not the name.  Therefore I rotated
> that file out of the way and a copy into place.  This doesn't
> eliminate the problem but side-steps it.  If it is one of those times
> again then the problem will follow the file and all will appear okay
> now.  And if not then it is something completely different.  Just a
> diagnose step.)
>
>> I'll leave it like this for a while so you can look at it.
>
> I killed that process on the server side.
>
>> What else can I look at?
>
> I added you to the test-project.  Please check that out and make some
> random change to test-file1.txt or create a new file or whatever and
> then commit that back in.  Did that work?  Do that twice or three
> times.  Does that work?  It's a test project to test svn functionality
> on Savannah so please keep it clean but the changes aren't important
> otherwise.  Any diddle and commit should test the flow.
>
>   svn co svn+ssh://stevan_wh...@svn.savannah.nongnu.org/test-project
>
> Bob

Re: [Savannah-users] SVN commit problems

[Steve White]

Hi Bob,

OK I tried it again.  Still not working -- it has hung:

$ svn commit
Sending...
Transmitting file data ...done
Committing transaction...


And nothing for several minuts.  Previously I killed the process and
tried again later -- this is when I saw the issue with the lock on the
server.
I have been committing the same way pretty regularly recently and this
thing just started happening yesterday.
And I saw it happen on a different system, when I committed something
from there.

I'll leave it like this for a while so you can look at it.

What else can I look at?  There's only one SVN process running:
$ ps -aef |grep svn
swhite   19355  3728  0 00:13 pts/000:00:01 svn commit
swhite   19363 19355  0 00:13 pts/000:00:00 ssh -q -o
ControlMaster=no -- stevan_wh...@svn.savannah.gnu.org svnserve -t

Thanks!


On Wed, Nov 29, 2017 at 10:46 PM, Bob Proulx <b...@proulx.com> wrote:
> Hello Steve,
>
> Steve White wrote:
>> Hi,  since yesterday I've been getting errors on svn commit:
>>
>> Sending  ... 
>> Transmitting file data ...done
>> Committing transaction...
>> svn: E37: Commit failed (details follow):
>> svn: E37: Can't get exclusive lock on file
>> '/srv/svn/freefont/db/txn-current-lock': No locks available
>> ...
>
> There appears to be a process of yours still running attached to that file.
>
>> It doesn't happen every time, but for some hours now I've been unable
>> to commit anything.
>
> It seems that there are two processes hanging around attached to that
> file.  I can only guess that some networking glitches between your
> client and the server has left some processes unclosed.  They should
> timeout eventually but the timeout is long to accomodate people
> working on slow connections.
>
>> This appears to be a server issue.  Please have a look at it.
>
> I have killed off the two processes I saw of yours that were attached
> to that file.  That should release the locks for it and you should be
> able to get a new semaphore lock now.  But there is nothing that would
> prevent this from happening again.  If it happened once then it could
> happen again.  Please let us know if it does and we can deal with it
> again then.
>
> Bob

Re: [Savannah-users] incorrect link on your webpage

[Steve White]

Hi Linda!

Fixed it.

This is the result of trying to maintain a site by hand with straight
HTML.  I should find a better way.

Don't hesitate to point out any other problems!  But...it would be
better to write to me directly, or to one of the FreeFont lists
https://savannah.gnu.org/mail/?group=freefont
or submit a bug report at
  https://savannah.gnu.org/bugs/?group=freefont

Thanks!


On Sat, Nov 19, 2011 at 4:48 PM, Linda Evans lindaev...@btinternet.com wrote:
 When I am on this page -

 http://www.gnu.org/s/freefont/ranges/

 and I click on the left side menu word SOURCES

 I am taken to (the same page) -

 http://www.gnu.org/s/freefont/ranges/index.html

  - - - - - - - - - - - - - - - - - - - -

 If I am on any other page of the GNU FreeFont site
 and I click on SOURCES
 then I am taken to -

 http://www.gnu.org/s/freefont/sources/

  - - - - - - - - - - - - - - - - - - - -

 regards,

 Linda

[Savannah-users] removing spam comments from news items

[Steve White]

Hi,

I just noticed, people have been making junk replies on the FreeFont
News items for some time.

Look, for example, at the end of
https://savannah.gnu.org/forum/forum.php?forum_id=6518

I can't figure out how to delete them or hide them, or how to
not-publish them or whatever I'm supposed to do. I want these things
gone.
--
The User Docs: In-Depth Guide, under News, says:

From the Administration-News menu, you will be able to set news
notification. However, news management (approval/deletion) is done
through the Public-News menu. The News management link will only be
visible if you are logged in as the project administrator. Before
being published, news must be approved first by project admin.

I don't know what this means.

There's Edit Public Info under Main... but no...
OK maybe it means, to log out and look at it as a non-admin user, but... no...
--
The Cookbook topic Fighting spam

 
https://savannah.gnu.org/cookbook/?func=detailitemcomingfrom=1405item_id=140

says at the time when logged-in male user sees content that in his
belief system is spam, he is able to flag it as spam.

Well I'm logged in, and I'm male, and I am seeing it, and I truly do
believe with all my heart that it is spam. Yet...

This document goes into some detail about policies and algorithms, but
doesn't say what the heck a male such as I must do to flag something
as spam. It gives me assurance as to my ability, but no instruction.
Is this a test of some kind?

Just how is this flagging accomplished by the user?

TIA!

Re: [Savannah-users] removing spam comments from news items

[Steve White]

Muchas gracias, Karl!