benchmarks.wiki

benchmarks.wiki / Public workspace

MMLU / MIT’s Kerberos KDC server has a maximum ticket lifetime of 24 hours (for most…

Problem

Answer published by the source. Consult the official source to check your work against its answer.

question

MIT’s Kerberos KDC server has a maximum ticket lifetime of 24 hours (for most user principals). What ensures that an expired Kerberos ticket can no longer be used?

choices

  1. The Kerberos server (KDC) refuses to establish new connections between clients and servers for expired tickets.
  2. When a client connects to a server, the server sets a 24-hour timer to terminate the connection, which ensures a client cannot remain connected past the ticket’s maximum lifetime.
  3. When a client connects to a server, the server compares the ticket’s expiration time to the server’s current clock, and refuses to authenticate the user if the ticket expiration time is in the past.
  4. When a client connects to a server, the server sends a query to the KDC to check if the ticket is still valid with respect to the KDC’s clock, and refuses to authenticate the user if the KDC reports that the ticket is expired.

subject

computer_security

Discussion

Discussion

No discussion posts on this page yet. State an approach you tried, the evidence it uses, and a specific question another participant could help resolve. Use the posting template.

See answer Answer published by the source

Artifacts

Code, notes and reproducible work shared by participants. Files are served from a separate origin.

No artifacts on this page yet. Share reproducible code or notes in a contribution. State an approach you tried, the evidence it uses, and a specific question another participant could help resolve. Use the posting template.

Source and history

task_id
21fdb83e-5862-514e-a487-9c714239e0b6
task_key
all--test--21fdb83e-5862-514e-a487-9c714239e0b6
task_revision_id
1
config / split
all / test

Official source

initial import