search for: base64_encod

...orig/authenticate.c Sun Jan 26 20:37:54 2003 +++ rsync-2.5.6/authenticate.c Tue May 13 13:18:50 2003 @@ -24,7 +24,7 @@ encode a buffer using base64 - simple and slow algorithm. null terminates the result. ***************************************************************************/ -static void base64_encode(char *buf, int len, char *out) +void base64_encode(char *buf, int len, char *out) { char *b64 = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/"; int bit_offset, byte_offset, idx, i; diff -u rsync-2.5.6.orig/socket.c rsync-2.5.6/socket.c --- rsync-2.5.6.orig/socket...

...02-01-24 03:33:45.000000000 +0100 +++ rsync-2.5.5/authenticate.c 2002-04-04 12:32:58.000000000 +0200 @@ -24,7 +24,7 @@ encode a buffer using base64 - simple and slow algorithm. null terminates the result. ***************************************************************************/ -static void base64_encode(char *buf, int len, char *out) +void base64_encode(char *buf, int len, char *out) { char *b64 = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/"; int bit_offset, byte_offset, idx, i; diff -u rsync-2.5.5.orig/socket.c rsync-2.5.5/socket.c --- rsync-2.5.5.orig/socket...

...*salt) { unsigned char snonce[SCRAM_SERVER_NONCE_LEN+1]; string_t *str; @@ -84,12 +63,9 @@ snonce[sizeof(snonce)-1] = '\0'; request->snonce = p_strndup(request->pool, snonce, sizeof(snonce)); - random_fill(request->salt, sizeof(request->salt)); - - str = t_str_new(MAX_BASE64_ENCODED_SIZE(sizeof(request->salt))); - str_printfa(str, "r=%s%s,s=", request->cnonce, request->snonce); - base64_encode(request->salt, sizeof(request->salt), str); - str_printfa(str, ",i=%d", SCRAM_ITERATE_COUNT); + str = t_str_new(sizeof(snonce)); + str_printfa(str, &...

.... When using M$ Outlook (2000 and 2003) and Outlook Express 6, authentification always fails. Turning on the Dovecot auth debug on reveals the reason: Dovecot SASL expects, in accordance with the standards, the following format of the SMTP AUTH command (using the PLAIN auth mechanism): AUTH PLAIN base64_encode("username\0username\0password") whereas the M$ clients send as the second argument only base64_encode("username\0password"), which naturally leads to authentification failure. Postfix apparently does not play any role in this game, as it simply passes the received command argu...

...$iv = substr( $password ^ $enc_text, 0, 512 ); while ( $i < $n ) { $block = substr( $plain_text, $i, 16 ) ^ pack( ''H*'', md5 ( $iv ) ); $enc_text .= $block; $iv = substr( $block . $iv, 0, 512 ) ^ $password; $i += 16; } return base64_encode( $enc_text ); } function md5_decrypt( $enc_text, $password, $iv_len = 16 ) { $enc_text = base64_decode( $enc_text ); $n = strlen( $enc_text ); $i = $iv_len; $plain_text = ''''; $iv = substr( $password ^ substr( $enc_text, 0, $iv_len ), 0, 512 ); while (...

...my explain me, how to use client auth socket to authenticate against dovecot-auth unix socket. As fas as I understood login must be sent in form "user\0\user\0password" as base64 encoded string. pp code (I'm using socket used by postfix auth): -------------------- <?php $authstr = base64_encode('test at virtual.net\0test at virtual.net\0test'); $fp = fsockopen("unix:///var/spool/postfix/private/auth",0, $errno, $errstr, 30); if (!$fp) { echo "$errstr ($errno)<br />\n"; } else { $out = "$authstr\r\n"; fwrite($fp, $out); while (!f...

Hello, I would like to change samba4 AD user's password using php. Here's my code: function UpdateLdapPassword($username, $newpassword) { global $ds; global $rdn; $entry["clearTextPassword"][0]=base64_encode(iconv('UTF-8','UTF-16LE',$newpassword)); $bReturn= ldap_modify ($ds, $rdn, $entry); Debug ("msg:'".ldap_error($ds)."'<br><br>"); return $bReturn; } The logs display something like this:...

Is it possible to rsync through a firewall that requires HTTP basic authentication? The RSYNC_PROXY variable seems to correctly direct the request to go through the HTTP proxy server on the firewall, but there's no way to specify a username/password combo. The error message reported by rsync is "bad response from proxy - HTTP/1.1 401 Authentication required", which is not

Dear all, Hi. This is imacat from Taiwan. I'm new to this list. I was migrating from Qpopper to Dovecot. (Qpopper copies the mailbox when POP3 logged in, which causes quota problem.) Generally Dovecot is nice. However, I have a few questions: 1. I have a few virtual users, and I'm not using IMAP. Do I still have to give them a writable home directory? I mean, they

Hi, Let's say I do: Set(data=xxx,yyy) Gosub(my-sub,s,1(${data})) My subroutine will only receive "xxx" for ARG1. How can I pass a literal with a comma to a single argument in a subroutine? (The point is: when calling the subroutine I do not know if the variable has a comma or not.) Thanks, Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I made a patch against branch-1.0 for SHA256 password hashing support for Dovecot. Courier Authlib supports this hashing scheme and in order to migrate from Courier to Dovecot, I've added SHA256 support to Dovecot. The attached patch is based on BSD licensed code from Olivier Gay (http://www.ouah.org/ogay/sha2/). Changes made by me in Olivier's sha2{.h,.c} code: - Prototype for

...ar *users = lp_auth_users(module); char challenge[16]; --- 202,208 ---- otherwise return username */ ! char *auth_server(int f_in, int f_out, int module, char *addr, char *leader) { char *users = lp_auth_users(module); char challenge[16]; *************** *** 221,229 **** base64_encode(challenge, 16, b64_challenge); ! io_printf(fd,"%s%s\n", leader, b64_challenge); ! if (!read_line(fd, line, sizeof(line)-1)) { return NULL; } --- 221,229 ---- base64_encode(challenge, 16, b64_challenge); ! io_printf(f_out,"%s%s\n", leader, b64_challe...

...al/ to the start of my PATH, reinstalled RCurl, and still the same erro message comes up. So, what does it mean that the output of nm is different on our systems and is it important? Thanks, Mark mkimpel-m90 ~/bin/curl-7.18.1: nm /home/mkimpel/R_HOME/site-library-2.7.0/RCurl/libs/RCurl.so | grep base64_encode U Curl_base64_encode 0000000000003910 T R_base64_encode mkimpel-m90 ~/bin/curl-7.18.1: nm /home/mkimpel/R_HOME/site-library-2.7.0/RCurl/libs/RCurl.so | grep Curl_base64_encode U Curl_base64_encode mkimpel-m90 ~/bin/curl-7.18.1: nm /home/mkimpel/R_HOME/site-library...

...al/ to the start of my PATH, reinstalled RCurl, and still the same erro message comes up. So, what does it mean that the output of nm is different on our systems and is it important? Thanks, Mark mkimpel-m90 ~/bin/curl-7.18.1: nm /home/mkimpel/R_HOME/site-library-2.7.0/RCurl/libs/RCurl.so | grep base64_encode U Curl_base64_encode 0000000000003910 T R_base64_encode mkimpel-m90 ~/bin/curl-7.18.1: nm /home/mkimpel/R_HOME/site-library-2.7.0/RCurl/libs/RCurl.so | grep Curl_base64_encode U Curl_base64_encode mkimpel-m90 ~/bin/curl-7.18.1: nm /home/mkimpel/R_HOME/site-library...

I hacked some command line options into imaptest. I dont think I broke it.. Place into dovecot-source root as usual and compile with: gcc imaptest.c -o imaptest -Wall -W -I. -Isrc/lib -DHAVE_CONFIG_H src/lib/liblib.a As per Timo's instructions. # imaptest -h imaptest [USER at IP:PORTNO] [pass=PASSWORD] [mbox=MBOX] [clients=CC] [msgs=NMSG] [use_authenticate] [PORTNO] USER = template for

...E *output_file = NULL; + + #define BASE64_LENGTH(len) (4 * (((len) + 2) / 3)) + + /* Encode the string S of length LENGTH to base64 format and place it + to STORE. STORE will be 0-terminated, and must point to a writable + buffer of at least 1+BASE64_LENGTH(length) bytes. */ + static void base64_encode (const gchar *s, gchar *store, gint length) + { + /* Conversion table. */ + static gchar tbl[64] = { + 'A','B','C','D','E','F','G','H', + 'I','J','K','L','M','N','O','...