File: en%40boldquot.gmo

package info (click to toggle)
gss 1.0.3-1
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 8,228 kB
  • ctags: 2,436
  • sloc: sh: 13,069; ansic: 11,900; python: 2,873; perl: 623; makefile: 172; sed: 16
file content (99 lines) | stat: -rw-r--r-- 9,947 bytes parent folder | download | duplicates (4) 
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
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
 
Kte`alH	4
(!J,d0*.K#h&*=
$Q
#v

 
(
()GIe;;@'h Q	
&+49`"m3C&w*9'/+-['& '4)T~),)"Hkw!,1)*1m7)4(D,^0*.E#b&*=
$K#p ((#AI_;;@! b  z  Q 
!	!
 !+.!9Z!"!!m!3="&q"*"9"'"/%#-U#'#2# ##'$:$)Z$$$)$$$,$5$%"Z%}%%!%,%1%)&<&C&)=,<89"&F:- 2%7'AJ0!G
I3+E.?>KBHC;(
D4@$/6#*51	   MSB                                                                 LSB
   +-----------------+-----------------+---------------------------------+
   |  Calling Error  |  Routine Error  |       Supplementary Info        |
   |   -a, --accept-sec-context[=MECH]
                    Accept a security context as server.
                    If MECH is not specified, no credentials
                    will be acquired.  Use "*" to use library
                    default mechanism.
  -i, --init-sec-context=MECH
                    Initialize a security context as client.
                    MECH is the SASL name of mechanism, use -l
                    to list supported mechanisms.
  -n, --server-name=SERVICE@HOSTNAME
                    For -i and -a, set the name of the remote host.
                    For example, "imap@mail.example.com".
  -h, --help        Print help and exit.
  -V, --version     Print version and exit.
  -l, --list-mechanisms
                    List information about supported mechanisms
                    in a human readable format.
  -m, --major=LONG  Describe a `major status' error code value.
  -q, --quiet       Silent operation (default=off).
A credential was invalidA later token has already been processedA parameter was malformedA required input parameter could not be readA required output parameter could not be writtenA supplied name was of an unsupported typeA token had an invalid MICA token was invalidAn expected per-message token was not receivedAn invalid name was suppliedAn invalid status code was suppliedAn unsupported mechanism was requestedAttempt to use incomplete security contextAuthenticator has no subkeyBuffer is the wrong sizeCommand line interface to GSS, used to explain error codes.

Context is already fully establishedCouldn't allocate gss_buffer_t dataCredential cache has no TGTCredential usage type is unknownGSS-API major status code %ld (0x%lx).

Incorrect channel bindings were suppliedInvalid field length in tokenKerberos V5 GSS-API mechanismMandatory arguments to long options are mandatory for short options too.
Masked calling error %ld (0x%lx) shifted into %ld (0x%lx):
Masked routine error %ld (0x%lx) shifted into %ld (0x%lx):
Masked supplementary info %ld (0x%lx) shifted into %ld (0x%lx):
Message context invalidNo @ in SERVICE-NAME name stringNo context has been establishedNo credentials were supplied, or the credentials were unavailable or inaccessibleNo errorNo error
No krb5 errorNo principal in keytab matches desired namePrincipal in credential cache does not match desired nameSTRING-UID-NAME contains nondigitsThe context has expiredThe gss_init_sec_context() or gss_accept_sec_context() function must be called again to complete its functionThe operation is forbidden by local security policyThe operation or option is unavailableThe provided name was not a mechanism nameThe quality-of-protection requested could not be providedThe referenced credentials have expiredThe requested credential element already existsThe token was a duplicate of an earlier tokenThe token's validity period has expiredTry `%s --help' for more information.
UID does not resolve to usernameUnknown krb5 errorUnknown quality of protection specifiedUnknown signature type in tokenUnspecified error in underlying mechanismUsage: %s OPTIONS...
Validation erroraccepting security context failed (%d/%d)base64 failbase64 input too longcould not acquire server credentials (%d/%d)could not import server name "%s" (%d/%d)displaying status code failed (%d)end of filegetlineindicating mechanisms failed (%d)initializing security context failed (%d/%d)inquiring information about mechanism failed (%d)inquiring mechanism for SASL name (%d/%d)malloc|
   +-----------------+-----------------+---------------------------------+
Bit 31            24  23            16  15                             0

Project-Id-Version: gss 1.0.3
Report-Msgid-Bugs-To: bug-gss@gnu.org
POT-Creation-Date: 2014-10-09 15:37+0200
PO-Revision-Date: 2014-10-09 15:37+0200
Last-Translator: Automatically generated
Language-Team: none
Language: en@boldquot
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=2; plural=(n != 1);
   MSB                                                                 LSB
   +-----------------+-----------------+---------------------------------+
   |  Calling Error  |  Routine Error  |       Supplementary Info        |
   |   -a, --accept-sec-context[=MECH]
                    Accept a security context as server.
                    If MECH is not specified, no credentials
                    will be acquired.  Use “*” to use library
                    default mechanism.
  -i, --init-sec-context=MECH
                    Initialize a security context as client.
                    MECH is the SASL name of mechanism, use -l
                    to list supported mechanisms.
  -n, --server-name=SERVICE@HOSTNAME
                    For -i and -a, set the name of the remote host.
                    For example, “imap@mail.example.com”.
  -h, --help        Print help and exit.
  -V, --version     Print version and exit.
  -l, --list-mechanisms
                    List information about supported mechanisms
                    in a human readable format.
  -m, --major=LONG  Describe a ‘major status’ error code value.
  -q, --quiet       Silent operation (default=off).
A credential was invalidA later token has already been processedA parameter was malformedA required input parameter could not be readA required output parameter could not be writtenA supplied name was of an unsupported typeA token had an invalid MICA token was invalidAn expected per-message token was not receivedAn invalid name was suppliedAn invalid status code was suppliedAn unsupported mechanism was requestedAttempt to use incomplete security contextAuthenticator has no subkeyBuffer is the wrong sizeCommand line interface to GSS, used to explain error codes.

Context is already fully establishedCouldn't allocate gss_buffer_t dataCredential cache has no TGTCredential usage type is unknownGSS-API major status code %ld (0x%lx).

Incorrect channel bindings were suppliedInvalid field length in tokenKerberos V5 GSS-API mechanismMandatory arguments to long options are mandatory for short options too.
Masked calling error %ld (0x%lx) shifted into %ld (0x%lx):
Masked routine error %ld (0x%lx) shifted into %ld (0x%lx):
Masked supplementary info %ld (0x%lx) shifted into %ld (0x%lx):
Message context invalidNo @ in SERVICE-NAME name stringNo context has been establishedNo credentials were supplied, or the credentials were unavailable or inaccessibleNo errorNo error
No krb5 errorNo principal in keytab matches desired namePrincipal in credential cache does not match desired nameSTRING-UID-NAME contains nondigitsThe context has expiredThe gss_init_sec_context() or gss_accept_sec_context() function must be called again to complete its functionThe operation is forbidden by local security policyThe operation or option is unavailableThe provided name was not a mechanism nameThe quality-of-protection requested could not be providedThe referenced credentials have expiredThe requested credential element already existsThe token was a duplicate of an earlier tokenThe token's validity period has expiredTry ‘%s --help’ for more information.
UID does not resolve to usernameUnknown krb5 errorUnknown quality of protection specifiedUnknown signature type in tokenUnspecified error in underlying mechanismUsage: %s OPTIONS...
Validation erroraccepting security context failed (%d/%d)base64 failbase64 input too longcould not acquire server credentials (%d/%d)could not import server name “%s” (%d/%d)displaying status code failed (%d)end of filegetlineindicating mechanisms failed (%d)initializing security context failed (%d/%d)inquiring information about mechanism failed (%d)inquiring mechanism for SASL name (%d/%d)malloc|
   +-----------------+-----------------+---------------------------------+
Bit 31            24  23            16  15                             0