[00:28:14] --- kaj has become available [03:20:12] --- Russ has left: Replaced by new connection [03:20:12] --- Russ has become available [03:56:31] --- Russ has left: Replaced by new connection [03:56:31] --- Russ has become available [06:01:27] --- jaltman has left: Replaced by new connection [06:01:28] --- jaltman has become available [06:52:17] --- JSund has become available [07:00:12] --- deason has become available [07:50:04] --- Kevin Sumner has left [07:50:08] --- Kevin Sumner has become available [08:10:59] --- jaltman has left: Disconnected [08:11:06] --- jaltman has become available [08:12:16] --- Russ has left: Replaced by new connection [08:12:16] --- Russ has become available [08:18:18] --- reuteras has left [08:58:32] --- Russ has left: Replaced by new connection [08:58:32] --- Russ has become available [09:20:58] --- matt has become available [09:28:56] --- kaj has left [10:33:16] --- kaj has become available [10:54:03] --- Russ has left: Disconnected [10:55:07] --- kaj has left [10:56:28] --- Russ has become available [12:41:13] --- Simon Wilkinson has left [12:42:49] --- jaltman has left: Disconnected [12:53:58] Anybody want to give me a hint about how to go about converting a Krb5 ticket to AFS token in perl, similar to aklog? (And, before it gets recommended, we've considered `system('aklog')` :) [12:58:03] After digging through some Google, I've found this post from Russ back in '08: http://www.openafs.org/pipermail/openafs-info/2008-July/029583.html Have things changed considerably wrt AFS.pm? [13:00:54] Do you actually have an AFS ticket, or just a TGT? In the latter case, you are probably best off running aklog, which contains fairly complicated logic for selecting the correct service principal name. [13:01:28] Oh, and I see that's what Russ said, too. [13:06:17] We have a TGT, but getting an AFS ticket shouldn't be difficult. [13:07:02] It also sounds like this might be the similar answer for our C code. (1) Get krb5 tgt in a 'correct' manner (2) run aklog. [13:08:20] > getting an AFS ticket shouldn't be difficult. No, but deciding what SPN to use is complicated, and you don't want to duplicate that code if you're writing something for the general case. If it's something site-specific, then you know the right SPN and can just get a ticket for that and pass it in. [13:09:59] See the src/aklog/aklog_main.c for how to construct the arguments to ktc_SetToken. It's fairly straightforward, once you have a ticket. [13:10:19] Thanks, I'll check it out. [13:57:45] --- jaltman has become available [15:44:47] --- deason has left [15:49:07] --- deason has become available [16:10:36] --- pod has left [17:11:37] --- JSund has left [17:15:21] --- JSund has become available [17:36:24] --- Russ has left: Disconnected [17:57:27] --- Russ has become available [18:28:34] --- matt has left [18:45:39] --- JSund has left [19:52:49] --- jaltman has left: Disconnected [20:08:16] --- jaltman has become available [20:56:26] --- Born Fool has become available [21:59:30] --- Born Fool has left [22:05:32] --- reuteras has become available [22:24:08] --- andersk has left [22:24:32] --- andersk has become available [22:33:29] --- deason has left [22:34:20] --- Russ has left: Disconnected [23:56:23] --- kaj has become available