savannah-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Savannah-hackers] address@hidden: Re: Strangeness in quail-input-st


From: Loic Dachary
Subject: Re: [Savannah-hackers] address@hidden: Re: Strangeness in quail-input-string-to-events]
Date: Wed, 9 Jan 2002 00:34:52 +0100

Dave Love writes:
 > 
 > I mean in information about savannah.

        I see. The page http://savannah.gnu.org/cvs/?group_id=40
does not propose pserver access, this is true. But it also says:

# Compatibility
#
# If your project (emacs) was using subversions.gnu.org before Savannah
# was installed, you should know that Savannah does not impose any
# action nor does it break anything in your habits. Please refer to the
# generic mail providing all the information you may need on this
# subject.

        Maybe you are refering to another page ? If so could you please
give me the URL so that I can fix it ? 

 >  > I tried to help you setup ssh some months ago, for the url
 >  > and w3 projects. It turned out not to work for you for some reason (I
 >  > could search the archives if this is important to you). 
 > 
 > I couldn't find instructions.  It appeared there should have been a
 > link from where I was referred, but there wasn't.  I asked for more
 > info and never heard back. 

        I attached the complete thread to the end of this mail. My answer,
dated December 10 says:

# > but `Account Maintenance' isn't linked and I couldn't find what it's
# > referring to.
#
#       It is now linked to https://savannah.gnu.org/account/editsshkeys.php

        Since I did not hear from you after this mail, I assumed this 
patch was satisfactory. Apparently the mail never reached you and I'm
sorry about that.

 > I used it extensively for gcc maintenance, but since then things have
 > changed, particularly with networking here.

        Oh, you mean the pserver port is open but the ssh port is not ? 
If it is so we can easily fix this by providing ssh protocol on the 2401
port. Please let me know if that would be a solution for you.

 > I'm sure something that I read said I must use ssh (1).  (Sorry I
 > don't remember where, if you want to correct it.)  I have tried
 > Kerberos access in the past without success through our firewalling,
 > despite being able to telnet to gnu.  (FYI Heimdal in Debian is
 > problematic at present -- it won't let me authenticate against
 > GNU.ORG.  I had an exchange with Debian people about that before
 > Christmas, which I must resume.)

        Alternatively, you could use the Debian GNU/Linux krb5
package, unless it's problematic for some reason. It works perfectly
well with gnu.org machines. I'm no kerberos expert, though, and if
you're using kerberos for purposes other than connecting to the
gnu.org machines I could not guide you into a heimdal -> krb5
migration.

 >  > This implies that your CVS is compiled with kerberos 5 support and
 >  > gssapi support and that you have a gnu.org kerberos account.
 > 
 > Can't you offer kerberized rsh too (not that it would help me)?

        You mean in replacement of ssh ? That is probably doable although
I've never tried. It would require to maintain a .k5login file for each
user automatically. I'd rather explore easier solutions before trying this,
if it's ok with you. 

        Since it's easy for us to bind ssh on any port convenient to
you, I guess ssh is still the best solution.

        Here is the URL that will allow you to reset your password.
Please use it ASAP, it will expire shortly. That will unlock your account
while we try to figure out how you can receive mail from address@hidden

https://savannah.gnu.org/account/lostlogin.php?confirm_hash=362201253a481af8970707df6d1b3bbb
    

        Cheers,

Attachment: d
Description: thread

-- 
Loic   Dachary         http://www.dachary.org/  address@hidden
12 bd  Magenta         http://www.senga.org/      address@hidden
75010    Paris         T: 33 1 42 45 07 97          address@hidden
        GPG Public Key: http://www.dachary.org/loic/gpg.txt

reply via email to

[Prev in Thread] Current Thread [Next in Thread]