Thanks for your quick response Derrick...I will try it again under
1.2.10.
-Renata
>Date: Tue, 16 Sep 2003 14:05:00 -0400 (EDT)
>From: Derrick J Brashear <[EMAIL PROTECTED]>
>Subject: Re: [OpenAFS] Problems adding a new server encryption key.
>X-X-Sender: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED]
So Sam and others might want to look at this software mentioned on
port-darwin.
http://rescomp.stanford.edu/~akosut/macosx/kfm_aklog.tar.gz
kfm_aklog is a plug-in which goes into /Library/Kerberos\ Plug-ins/ and
is called by setting up kerberos login in /etc/authorization as per
http://docs.inf
Adam Done <[EMAIL PROTECTED]> writes:
> Why is it nesseccory to put some files into subdirectories would they
> still be subjected to AFS ACLs?
It's not that they have to be in subdirectories to be subject to ACLs,
since everything in AFS is subject to ACLs, but rather that AFS ACLs are
per-direc
Does anyone know what this means?
saturn> pts delete jomier
pts: I/O error writing dbase or log deleting jomier (id: 3672)
The user remains after the failed operation. We also get the
corresponding error when trying to add a user or change a password.
The log files seem fine and 'bos getlog'
Erik Arneson wrote:
On 16-Sep-2003, J Maynard Gelinas <[EMAIL PROTECTED]> wrote:
This may be slightly off-topic for the OpenAFS list, but the latest
OpenSSH-3.7p1 removes support for AFS, writing Kerberos 5 tickets to files
(in memory now), and Kerberos 4. Since an exploit for all previous Ope
On 16-Sep-2003, J Maynard Gelinas <[EMAIL PROTECTED]> wrote:
> This may be slightly off-topic for the OpenAFS list, but the latest
> OpenSSH-3.7p1 removes support for AFS, writing Kerberos 5 tickets to files
> (in memory now), and Kerberos 4. Since an exploit for all previous OpenSSH
> releases h
At 7:23 PM -0700 9/15/03, Adam Done wrote:
I can see good reasons to both arch. I gather openAFS is
simpler to manage than DFS but DFS has more advanced features.
Also I gather DFS is not supported on a wide rage of
server/client hardware.
RPI has used AFS for more than ten years. We were interes
I'll pick one place to reply, and punt the other. No code to be developed.
On Tue, 16 Sep 2003, Renata Maria Dart wrote:
> Lost contact with file server 134.79.17.xx in cell slac.stanford.edu (all
> multi-homed ip addresses down for the server)
>
> began appearing in our SYSLOG output. I wa
Thanks a bunch! This should tide me over until some official RPMS are
announced. --M
On Tue, 16 Sep 2003, Alf Wachsmann wrote:
> We are patching the last version (3.6.1p2) of OpenSSH that still supports
> AFS. The patch for this new bug is small enough to do this:
> http://www.freebsd.org/cg
On Tue, 16 Sep 2003, J Maynard Gelinas wrote:
> This may be slightly off-topic for the OpenAFS list, but the latest
> OpenSSH-3.7p1 removes support for AFS, writing Kerberos 5 tickets to files
> (in memory now), and Kerberos 4. Since an exploit for all previous OpenSSH
> releases has just been an
This may be slightly off-topic for the OpenAFS list, but the latest
OpenSSH-3.7p1 removes support for AFS, writing Kerberos 5 tickets to files
(in memory now), and Kerberos 4. Since an exploit for all previous OpenSSH
releases has just been announced, I'm somewhat confused about how to
handle th
Hi, yesterday we attempted to update our AFS server encryption
keys. We have done this procedure a dozen or so times under
Transarc AFS with minimal problems. Yesterday was our first time
trying it under OpenAFS and things did not proceed as expected.
All of our database (3) and fileservers (8)
Hi all -
I thought I'd share a little experience with using OpenAFS for my home
directory on MacOS X 10.2.6. I'm also subscribing to our Solaris NIS
server for password authentication.
In general, the configuration is *reasonably* reliable. However, it's
not quite ready for prime time, for the f
You almost certainly do mean utf-8.
If they really are being converted to '?' then something in the Windows
client wrongly believes that the server wants ascii or some other subset of
unicode.
Can you point me at one of these files?
Have you tried this with a later release of OpenAFS?
__
Yes, my users have had issues with OpenAFS on WinXP too:
1. The computer name is too long. Make sure the computer name is at most 10
alpha chars. Its a silly limitation, and OpenAFS should explicitly complain
about it.
2. AFS doesn't announce its netbios name. It should announce -AFS.
If it do
15 matches
Mail list logo
