Testing 3
--
-BEGIN EMAIL SIGNATURE-
The Gospel for all Targeted Individuals (TIs):
[The New York Times] Microwave Weapons Are Prime Suspect in Ills of
U.S. Embassy Workers
Link:
https://www.nytimes.com/2018/09/01/science/sonic-attack-cuba-microwave.html
Many thanks for the pointers regarding this. We are successfully
running cross-realm tests in at least the perl environment. I do not
believe that python has a mechanism to allow the same but will
investigate further on that as time permits.
On 5/1/17 7:37 PM, Russ Allbery wrote:
> "David A. K
"David A. Kovacic" writes:
> Unfortunately we are not using kadmin and do not have the ability to set
> the "-r" flag in this case. We are trying to create test programs in
> perl and python that test the KDC functionality so that when we upgrade
> we can test development, test, and production s
27;: 43787566L, 'message': 'GSS-API (or Kerberos) error'}
On 5/1/17 3:17 PM, Tareq Alrashid wrote:
>
>
>> Begin forwarded message:
>>
>> *From: *Greg Hudson mailto:ghud...@mit.edu>>
>> *Subject: **Re: Testing 3 Kerberos realms from same server*
On 05/01/2017 04:10 PM, David A. Kovacic wrote:
> The perl programs use Authen::Krb5::Admin and the python program uses
> python-kadmin to try the tests - both of which use the Kerberos
> libraries to implement the "init with keytab" routine to produce an
> admin object with which we can manipulate
On 05/01/2017 11:04 AM, Tareq Alrashid wrote:
[...]
> Code written in Python simply loops through each of the 3 realms, kinit with
> the keytab performs a few kadmin operations and either passes or fails.
>
> The strange result is that only the realm name set by “default_realm =“, pass
> and al
Greetings,
On RHEL7 systems. We finally got around to setting up a separate development
and test realms.
We wanted to test normal/successful operations on all the realms specially
after new code deployment or new RHEL patches.
Testing all systems from same server which has a single keytab wit
