File: condor_check_password.rst

package info (click to toggle)
condor 23.9.6%2Bdfsg-2.1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 60,012 kB
  • sloc: cpp: 528,272; perl: 87,066; python: 42,650; ansic: 29,558; sh: 11,271; javascript: 3,479; ada: 2,319; java: 619; makefile: 615; xml: 613; awk: 268; yacc: 78; fortran: 54; csh: 24
file content (58 lines) | stat: -rw-r--r-- 2,025 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
*condor_check_password*
=======================

Examine HTCondor key files, looking for keys that prior version of HTCondor
will not fully read.

:index:`condor_check_password<single: condor_check_password; HTCondor commands>`
:index:`condor_check_password command`

Synopsis
--------

**condor_check_password** <**-h** | **-\-help**>

**condor_check_password** [**-\-truncate**] [*key*]

Description
-----------

Versions of HTCondor before 8.9.12 contained contained a bug in the code
used to read the pool password (hence the name of the tool): in some
cases the read would be truncated before end of the file.  Because the
same code is used to read IDTOKENS signing keys, this bug affects the
IDTOKENS authorization method, as well.

There was no backwards-compatible fix: versions 8.9.12 and later may
read the same file differently than earlier versions, meaning that
tokens issued before 8.9.12 may not be recognized by later versions.

This tool detects key files which will not be fully read by earlier versions
of HTCondor.  IDTOKENS generated by such a key will not be accepted by
later versions (which read the whole key file).  If you choose to
truncate these files on disk, later version of HTCondor will read only
the same bits as earlier versions, allowing them to accept tokens
issued by earlier versions, at the cost of weakening your pool's
resistance to brute-force attacks.

By default, this tool checks all the key files that will be
found by the current HTCondor configuration; you may specify a
specific *key* or *key*\ s to check, instead.

Options
-------

    **-h**, **-\-help**
        Print a usage reminder.

    **-\-truncate**
        When a potentially insecure key is encountered, truncate it to
        match the behavior prior to version 8.9.12.

Exit Status
-----------

Exits with code 0 if there were no signing keys to check or if all of
the checked keys were OK.  Exits with code 1 if at least one checked
key was not OK.  Exits non-zero if a problem was encountered
along the way.