Searched refs:BASE64 (Results 1 – 9 of 9) sorted by relevance
8 postmap: warning: table hash:file_test_map.db: key entry-4: malformed BASE64 value: postmap-entry-413 postmap: warning: table hash:file_test_map.db: key entry-4: malformed BASE64 value: postmap-entry-4
152 %token ADDR4 ADDR6 ADDRANY SLASH NUMBER BASE64156 %type <chr> ADDR4 ADDR6 BASE64220 | TAG_PUB BASE64
71 return BASE64;
129 base64-distinguishedName = BASE64-UTF8-STRING137 base64-rdn = BASE64-UTF8-STRING153 ":" FILL (BASE64-STRING) /260 BASE64-UTF8-STRING = BASE64-STRING264 BASE64-CHAR = %x2B / %x2F / %x30-39 / %x3D / %x41-5A /269 BASE64-STRING = [*(BASE64-CHAR)]362 defined in BASE64-CHAR, and are ignored. LDIF does not permit
28 # GRR: handle BASE64
178 signature = BASE64( D^M( authorization ))366 server-signature = BASE64( DIGEST( raw-server-signature ) )369 encoded-challenge = BASE64( raw-challenge )
284 BASE64, enumerator1048 dearmour->state = BASE64; in base64()1206 case BASE64: in armoured_data_reader()
271 Authentication (as described in RFC2068) uses BASE64 for a similar
9630 *) Fix BASE64 decode (EVP_DecodeUpdate) for data with CR/LF ended lines:9634 BASE64-decoding BIO. Bug fund and patch submitted by Pavel Tsekov