Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

/earth: file system full.


devel / comp.protocols.kerberos / Re: Creating a principal using the kadmin C API

SubjectAuthor
o Re: Creating a principal using the kadmin C APIGreg Hudson

1
Re: Creating a principal using the kadmin C API

<mailman.38.1649392542.8148.kerberos@mit.edu>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=233&group=comp.protocols.kerberos#233

  copy link   Newsgroups: comp.protocols.kerberos
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!tncsrv06.tnetconsulting.net!.POSTED.mailman.mit.edu!not-for-mail
From: ghudson@mit.edu (Greg Hudson)
Newsgroups: comp.protocols.kerberos
Subject: Re: Creating a principal using the kadmin C API
Date: Fri, 8 Apr 2022 00:35:29 -0400
Organization: TNet Consulting
Lines: 17
Message-ID: <mailman.38.1649392542.8148.kerberos@mit.edu>
References: <CAD-Ua_ifa=vo4PEzy3kx-5FB3J+hhN_2BTuS7O=E+hfudRbV4Q@mail.gmail.com>
<733bbe58-7c13-8abc-f0e6-3cbe979540ed@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Injection-Info: tncsrv06.tnetconsulting.net; posting-host="mailman.mit.edu:18.7.21.50";
logging-data="19316"; mail-complaints-to="newsmaster@tnetconsulting.net"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Thunderbird/91.5.0
To: Lars Francke <lars.francke@gmail.com>, <kerberos@mit.edu>
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
b=A7DnByemzXBLocIXk6YxZcaTr11pWegyWs7gb70BL+hos8O1aOCDEhPz5Y5aZ8nApOLfcsDqcuKyvJiUEPqexFyhw0MA+oQOv1wZqJ563T5uW/FweaX3anUuZp3AjD2w7QwBOa2IqtgHNddOY0nic1lzndH+9MzNimj7zfHyJ3i0mZztq8mtd7vxOW1RxS5eKw/w1tq7LPNFBEzD/R7hrPaBA8qipseGOqkmcMOA5NG2Ap3NBDf8/EkdEgVr+FssGbSB7PTOzbO5Sh/0gUtntICIDEIZLP4ZhHab70GZ/R7Wbv4k0bMdTdG7iCNiDcvmZ2wqhz+jLBC/t+amwAMKxQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
s=arcselector9901;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1;
bh=alqlmPxhb0Zb6PBlDGVUckrsTObKOEkgA+H7woK6P0Q=;
b=X/ftm4EszkcpAoOr6XAXNH3SshmOEDTT+zardoE39JSrSCjDFFdiywFcESlbnd7pniTKDcFy+CLim4KA/qZIZTVRHjpf5I8ZHLaUh8CUVt4iJ8F8N04gwjctiOMga55HuOtIsgH9ocRRQ9Mv77A//D7cdN68ecmsVq0crocvRmbCjiWn2FduIV6DvKB1OGR/3jA7l7wiiKY5vyc89bHhqLHkxUH+htIE6ZMj14TRNLfCEuHypnuYMsvBWaUOyNoSLb2gZasrJAL+6cp9XNiB0ZBhhGV3GtiHQT6h0iSDoEVQBMpVASROW5dK0IyI+AtoknTOKS1A5tvfd18jy6inlA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is
18.9.28.11) smtp.rcpttodomain=mit.edu smtp.mailfrom=mit.edu; dmarc=pass
(p=none sp=none pct=100) action=none header.from=mit.edu; dkim=none (message
not signed); arc=none (0)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=selector2;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=alqlmPxhb0Zb6PBlDGVUckrsTObKOEkgA+H7woK6P0Q=;
b=GFJPXO6iKl2i7pdav8QmwZnX0RztlIc1JPKnNZ5dNqaL4E5Ko3UPdJ2Q71aRdX3sBEvKMEdlz7uFaK64lBq6N89y2YuhBpyHivaeQ/FpUpnlaREs72dGm8yeUIDs9CLIe6H57Y54Y3DHaCcH5px0LkGELl1uzGxW+sqiYQQhGNI=
Authentication-Results: spf=pass (sender IP is 18.9.28.11)
smtp.mailfrom=mit.edu; dkim=none (message not signed)
header.d=none;dmarc=pass action=none header.from=mit.edu;
Received-SPF: Pass (protection.outlook.com: domain of mit.edu designates
18.9.28.11 as permitted sender) receiver=protection.outlook.com;
client-ip=18.9.28.11; helo=outgoing.mit.edu;
Content-Language: en-US
In-Reply-To: <CAD-Ua_ifa=vo4PEzy3kx-5FB3J+hhN_2BTuS7O=E+hfudRbV4Q@mail.gmail.com>
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 64afd9ba-0ecf-4acf-bc36-935f6235ba8b:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: a1edc35e-bacc-4688-0ef0-08da19193895
X-MS-TrafficTypeDiagnostic: CO1PR01MB7388:EE_
X-LD-Processed: 64afd9ba-0ecf-4acf-bc36-935f6235ba8b,ExtAddr
X-MS-Exchange-AtpMessageProperties: SA
X-Microsoft-Antispam-PRVS: <CO1PR01MB7388EC182F78FC209EBA8C2CBCE99@CO1PR01MB7388.prod.exchangelabs.com>
X-MS-Exchange-SenderADCheck: 1
X-MS-Exchange-AntiSpam-Relay: 0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: TqobKffsn52RzwGuuJHbJHidG6L5qRraaj45uAyTOPoO9eu+SgfvTNlOV2danBYW1KIQ+BqYSnyLfJ4tlG5POHsiCEy/l5nIqAzBduqUq3nuMFOS7emoPxemVmhLgFb6zbfOdfPdDXxTlVhAkj2NYo3BKgw5FjmAfCZ/a2vwoXdSCgtMX1mmModjgBVZeB82cl5PlWATVTutKKntKvqiz6azAJ+9Q5pmGLJLKcHLndJvZGHMv5VtSY9J708i57DSxGiBBFEj5P4IOSg5KTy872448OKUayPVtcWqVNd16CPGBwXa8PRGa4/jkaYAHMAVacFP/I338Pyco6wioxRzFYLeqX2NSzFtBMYX+KY2HgcGEB7W6bGuWV6Kqm1pMIiucial9y0/33Mbv9Htv2cI7as8aOU3czrSz2l+o/iqLYqM5XTZgEog8jNdW39ftFmZI7XSDaPn3KN7WEG5DGctXuuC1x5tBHYfNcNzXGoC7dMotObHOrmByhds1S81M8F9B61KetexYehb0z+ID+fZ3UEhdN0gGTGgTdsfgFp1yFnE5MLNNSez5z9Oh4yDbcEGZhzWjbBDWHI/pQt5Sroyf2iLH1PDwAbgtkKmB93IRaQZje5l8HDjNKiADJHxBFCP9/cLLh18VU9EzW1BLaYAU/RFHgZsk1/7aZX09ikZjOVeLpefwM7aBnisLSd/Seu+xGlYfoOtgMStGtgJlo7yDA==
X-Forefront-Antispam-Report: CIP:18.9.28.11; CTRY:US; LANG:en; SCL:1; SRV:;
IPV:CAL; SFV:NSPM; H:outgoing.mit.edu; PTR:outgoing-auth-1.mit.edu; CAT:NONE;
SFS:(13230001)(4636009)(356005)(26005)(2616005)(956004)(2906002)(31686004)(7696005)(4744005)(36756003)(53546011)(426003)(5660300002)(336012)(83380400001)(75432002)(68406010)(8676002)(70586007)(31696002)(86362001)(786003)(316002)(508600001)(6706004)(6636002)(43740500002);
DIR:OUT; SFP:1102;
X-Auto-Response-Suppress: DR, OOF, AutoReply
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 08 Apr 2022 04:35:33.7547 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: a1edc35e-bacc-4688-0ef0-08da19193895
X-MS-Exchange-CrossTenant-Id: 64afd9ba-0ecf-4acf-bc36-935f6235ba8b
X-MS-Exchange-CrossTenant-AuthSource: DM6NAM11FT003.eop-nam11.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1PR01MB7388
X-OriginatorOrg: mit.edu
X-BeenThere: kerberos@mit.edu
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: The Kerberos Authentication System Mailing List <kerberos.mit.edu>
List-Unsubscribe: <https://mailman.mit.edu/mailman/options/kerberos>,
<mailto:kerberos-request@mit.edu?subject=unsubscribe>
List-Archive: <http://mailman.mit.edu/pipermail/kerberos/>
List-Post: <mailto:kerberos@mit.edu>
List-Help: <mailto:kerberos-request@mit.edu?subject=help>
List-Subscribe: <https://mailman.mit.edu/mailman/listinfo/kerberos>,
<mailto:kerberos-request@mit.edu?subject=subscribe>
X-Mailman-Original-Message-ID: <733bbe58-7c13-8abc-f0e6-3cbe979540ed@mit.edu>
X-Mailman-Original-References: <CAD-Ua_ifa=vo4PEzy3kx-5FB3J+hhN_2BTuS7O=E+hfudRbV4Q@mail.gmail.com>
 by: Greg Hudson - Fri, 8 Apr 2022 04:35 UTC

On 4/7/22 16:19, Lars Francke wrote:
> We tried to use kadm5_create_principal_3 and kadm5_randkey_principal_3 but
> we seem to be running into an issue. Ideally we'd like to call this
> function with a handle (+ context) with an in-memory krb5.conf but that
> does not seem to work so we create the files and refer to them in the
> profile but kadmin still seems to load (is this related to the
> "alt_profile"?) a file from a default location which means it'll use the
> wrong connection details.

krb5_init_context_profile() lets you supply a profile object. If this
is created with profile_init_path(), the application should be able to
strictly control which file is used.

It is possible to create an in-memory profile with
profile_init_vtable(). Perhaps it would be nicer if one could create an
empty in-memory profile object and populate it with
profile_add_relation(), but that is not currently implemented.


devel / comp.protocols.kerberos / Re: Creating a principal using the kadmin C API

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor