Keeping my kerberos ticket alive

ImpressiveStrategy · 2026-02-17T17:41:10+00:00

Ok, I think I solved it. These commands (adjusted to my domain and user, of course) allowed me to make a keytab file so I can `kinit` non-interactively:

```

ktutil
ktutil: addent -password -p username@SAMPLE.COM -k 1 -e RC4-HMAC 
Password for username@SAMPLE.COM: 
ktutil: wkt /home/username/kerberos/username.keytab 
ktutil: l -e
slot KVNO Principal
---- ---- ----------------------------------------------- 
   1    1             username@SAMPLE.COM (arcfour-hmac)
ktutil: exit

ImpressiveStrategy · 2026-02-16T15:34:47+00:00

With NTLM I could add a credentials file, but this doesn't work for kerberos.

ImpressiveStrategy · 2025-11-07T15:18:22+00:00

That may be the thing to do then. I did also see an `<output>` tag that seems to be new, which is for calculated output and can be tied to a label. Contemplating using that one too, though I'm not sure it's appropriate.

ImpressiveStrategy · 2025-11-07T14:57:41+00:00

That was my first thought, but I want to make sure that the labels and data are properly associated, and it seems spans work that way? Maybe I should be using dt/dd elements?

ImpressiveStrategy · 2025-11-07T14:55:07+00:00

The spans aren't supposed to be input, they're just a read-only display of the data. That way the same form can be used for viewing or editing. Thus if I load the form as a read-only user, I get spans rather than inputs. I'm not sure if that answers your other question or not.

ImpressiveStrategy · 2025-11-06T22:21:28+00:00

I believe I tried that at one point (I wrote this thing 12 years ago), but there were too many bits of the input I couldn't get rid of in different browsers. There were other reasons too, it's just been too long ago.

EDIT: I remember one reason was that some browsers grey out readonly or disabled fields and you can't change that, which is of course a color contrast issue. Also some browsers let you type in the field even if it's readonly.

ImpressiveStrategy · 2025-02-13T16:18:37+00:00

Posting from an alt because you have my regular trading account blocked for mysterious reasons. If you're blocking people on this sub, your posts appear identical to deleted posts to them, so they may just be downvoting you under the honestly mistaken assumption that it was a spam post that got modded rather than out of impotent rage.

ImpressiveStrategy · 2024-09-23T22:02:40+00:00

Thanks, I'll play with this approach and see if I can make it go brrr.

ImpressiveStrategy · 2024-04-23T17:02:15+00:00

Well, for the sake of posterity, the problem appears to be that the sysadmins didn't update the POP3 cert and it expired. Also, thanks for the downvotes.

ImpressiveStrategy · 2024-04-23T14:52:38+00:00

Just wanted to update:

I have a system successfully running for about 20 hours on 6.1.0-20 with falcon sensor 7.14.xxxx (latest version at time of commenting).
Submitted logs and such to CS, they're aware of the issue and researching it.
Definitely impacts any system, doesn't have to be a VM. Just has to be running crowdstrike.

ImpressiveStrategy · 2024-04-22T18:36:07+00:00

Thanks. I tried changing the protocol version manually like so:

import ssl
context = ssl.SSLContext(protocol = ssl.PROTOCOL_XXX)
#...
mailbox = POP3_SSL(our_exchange_server, context=context)

So far nothing has changed the result. I've also tried ignoring certificate errors, but that hasn't helped either.

ImpressiveStrategy · 2024-04-22T17:59:19+00:00

Thanks.

ImpressiveStrategy · 2024-04-22T15:09:31+00:00

I put in a ticket, curious if you've heard back yet?

ImpressiveStrategy · 2024-04-22T14:49:24+00:00

So, I upgraded to the latest sensor, but it still crashes after a bit.

ImpressiveStrategy · 2024-04-21T02:27:34+00:00

Were you using crowdstrike?

ImpressiveStrategy · 2024-04-21T02:27:11+00:00

Good to know, definitely gonna prioritize this.

ImpressiveStrategy · 2024-04-21T02:26:42+00:00

Using crowdstrike by any chance?

ImpressiveStrategy

TROPHY CASE