Adam Megacz <[EMAIL PROTECTED]> writes:
> Russ Allbery <[EMAIL PROTECTED]> writes:
>> ktadd changes the key.
> I am: dumbfounded.
> Dare I ask if there was a reason for this decision? Other than causing
> me grief, of course.
Keytabs are normally not supposed to be shared between multiple mach
I'm sure people will give me plenty of reasons why this is a bad idea,
but putting that aside...
Is there any way to make sure that the cache manager never waits for
more than (say) 5 seconds for a response? By which I mean that if the
server fails to respond after 5 seconds, assume it's never c
Russ Allbery <[EMAIL PROTECTED]> writes:
> ktadd changes the key.
I am: dumbfounded.
Dare I ask if there was a reason for this decision? Other than
causing me grief, of course.
- a
--
PGP/GPG: 5C9F F366 C9CF 2145 E770 B1B8 EFB1 462D A146 C380
_
Adam Megacz <[EMAIL PROTECTED]> writes:
> Wow, I just went through a really confusing experience. Please tell me
> if this is a correct understanding:
> 1. Exporting a key from the KDC into a keytab using "ktadd" causes
> the principal's "kvno" to be incremented.
It also causes the key s
Wow, I just went through a really confusing experience. Please tell
me if this is a correct understanding:
1. Exporting a key from the KDC into a keytab using "ktadd" causes
the principal's "kvno" to be incremented.
2. /etc/openafs/server/KeyFile contains such a key
3. The key in th
For a client/server combination each behind a firewall:
Why does the Linux client
timeout fairly rapidly requiring a client restart?
Why does the Windows client
loose the network connection which is restored after clicking on
/afs/cellname
Tedc
Can someone send a link to the NW Air Presentation from the 2005
workshop?
One of my clients is interested in using OpenAFS as a backup
system to distribute emergency paper based forms. (When there is an earthquake
or utility outage that damaged their data centers).
FAA acceptanc
Mike Bydalek wrote:
> Jeffrey Altman wrote:
>> In 1.4.1 the Server fully implements byte range locking. However,
>> the byte range locks are not backed by AFS locks.
>>
> This may sound like a silly question, but do the byte range locks need
> to be backed by AFS locks, or is having byte range
Jeffrey Altman wrote:
Mike Bydalek wrote:
Hi All,
I currently have OpenAFS 1.4.1-rc6 Windows clients using Kerberos
authentication. The problem I'm having is that we unfortunately use
Quickbooks. I know byte-range locking on Windows clients is still
somewhat up in the air, so I
Sorry..I'll learn eventually.
Authenticating with password.
#%PAM-1.0
auth required /lib/security/pam_securetty.so
auth sufficient/lib/security/pam_afs.krb.so.1 try_first_pass
ignore_root
auth required /lib/security/pam_stack.so service=system-auth
auth
Peter M. Metcalf wrote:
Please, tell me what I am missing? Been through all I can read about
pam.d but have not found what step I have skipped that causes the need
for "klog" after a successful "ssh" connection just to obtain a token.
We can't tell you what you're missing if you don't tell us w
Please, tell me what I am missing? Been through all I can read about pam.d
but have not found what step I have skipped that causes the need for "klog"
after a successful "ssh" connection just to obtain a token.
Pete
___
OpenAFS-info mailing list
Op
12 matches
Mail list logo
