search for: decode_base64

...ction_config (const char *key, const char *value) return -1; #endif } + else if (strcasecmp (value, "address") == 0) { + mode = MODE_ADDRESS; + } else { nbdkit_error ("unknown mode: '%s'", value); return -1; @@ -137,6 +144,74 @@ decode_base64 (const char *data, size_t len, struct handle *ret) #endif } +static int +handle_address (struct sockaddr *sa, socklen_t addrlen, + struct handle *ret) +{ + struct sockaddr_in *addr = (struct sockaddr_in *) sa; + struct sockaddr_in6 *addr6 = (struct sockaddr_in6 *) sa; + union...

...dout) File "/usr/lib/python2.7/base64.py", line 306, in decode s = binascii.a2b_base64(line) binascii.Error: Incorrect padding root at vdcsv1:~# echo "flhibllHV2tPVFMyIXIjcGpnWUE/cmV1Q3hjLm5BQUQycX5EdyR1NGh" | LANG=C perl -MMIME::Base64 -ne 'printf "%s\n",decode_base64($_)' ~XbnYGWkOTS2!r#pjgYA?reuCxc.nAAD2q~Dw$u4h so: a) 'base64' decode it, but bump an error b) openssl does nothing c) python bump an error d) perl decode it Seems a bit strange to me... -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famigl...

...lection_dump_plugin (void) +{ +#ifdef HAVE_BASE64 + printf ("reflection_base64=yes\n"); +#endif +} + +/* Per-connection handle. */ +struct handle { + void *data; /* Block device data. */ + size_t len; /* Length of data in bytes. */ +}; + +static int +decode_base64 (const char *data, size_t len, struct handle *ret) +{ +#ifdef HAVE_BASE64 + gnutls_datum_t in, out; + int err; + + /* For unclear reasons gnutls_base64_decode2 won't handle an empty + * string, even though base64("") == "". + * https://tools.ietf.org/html/rfc4648#sect...

This series is based on my blog posting here: https://rwmj.wordpress.com/2019/09/13/nbdkit-supports-exportnames/ It depends on the fix for realloc: https://www.redhat.com/archives/libguestfs/2019-September/thread.html#00103 This series adds a fun plugin, and also an semi-related feature I've long thought to be desirable. You can consider patches 1 & 4, and patches 2 & 3 as forming

...redentials sent are the same whether they're sent via a true pop3 client or via the command line. when sent via the command line, they're generated via perl -MMIME::Base64 -e 'print encode_base64("\0username\0password");'and i've verified they're correct via decode_base64 config stuff: # postconf -n biff = no command_directory = /usr/sbin config_directory = /etc/postfix content_filter = smtp-amavis:[127.0.0.1]:10024 daemon_directory = /usr/libexec/postfix debug_peer_level = 2 enable_server_options = yes header_checks = pcre:/etc/postfix/custom_header_checks html_d...