base64 in url allways safe ?

[wbsurfver]

I am using the two functions below to encode part of a url. I had seen
that someone said base64 can sometimes add newlines in the encoding,
but had little luck finding reference to that using google, but I want
to make sure I am safe.
my url looks like this:
http://my.local/index.php/widget/fil...2F0ZWRfbmV3cy9

// functions to code url segments ...
function base64_url_enco de($input) {
return strtr(base64_en code($input), '+/=', '-_.');
}

function base64_url_deco de($input) {
return base64_decode(s trtr($input, '-_.', '+/='));
}

[Jerry Stuckle]

wb*******@yahoo .com wrote:

I am using the two functions below to encode part of a url. I had seen
that someone said base64 can sometimes add newlines in the encoding,
but had little luck finding reference to that using google, but I want
to make sure I am safe.
my url looks like this:
http://my.local/index.php/widget/fil...2F0ZWRfbmV3cy9

// functions to code url segments ...
function base64_url_enco de($input) {
return strtr(base64_en code($input), '+/=', '-_.');
}

function base64_url_deco de($input) {
return base64_decode(s trtr($input, '-_.', '+/='));
}

I haven't seen any base64 implementations which use a newline character
- and I doubt there are any (it's not a printable character).

But rather then use strstr, just urlencode the results from
base64_encode() .

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[C. (http://symcbean.blogspot.com/)]

On Jun 6, 3:34 am, Jerry Stuckle <jstuck...@attg lobal.netwrote:

wbsurf...@yahoo .com wrote:

I am using the two functions below to encode part of a url. I had seen
that someone said base64 can sometimes add newlines in the encoding,
but had little luck finding reference to that using google, but I want
to make sure I am safe.

my url looks like this:
http://my.local/index.php/widget/fil.../aHR0cDovL21lZ...

// functions to code url segments ...
function base64_url_enco de($input) {
return strtr(base64_en code($input), '+/=', '-_.');
}

function base64_url_deco de($input) {
return base64_decode(s trtr($input, '-_.', '+/='));
}

I haven't seen any base64 implementations which use a newline character
- and I doubt there are any (it's not a printable character).

But rather then use strstr, just urlencode the results from
base64_encode() .

uuencode does it (presumably because it was written when line-oriented
terminals were the common way of interacting with data) and MIME does
it (because SMTP is line oriented). But AFAIK the php implementation
doesn't.

It's a handy way to move data around because:
$enc=str_replac e('=','', base64_encode($ data)); // the trailing '=='
is not required
urlencode($enc) === mysql_real_esca pe($enc) === htmlentities($e nc)
=== addslashes($enc ) === stripslashes($e nc) === $enc

C.

[Jerry Stuckle]

C. (http://symcbean.blogspot.com/) wrote:

On Jun 6, 3:34 am, Jerry Stuckle <jstuck...@attg lobal.netwrote:

>wbsurf...@yaho o.com wrote:

>>I am using the two functions below to encode part of a url. I had seen
that someone said base64 can sometimes add newlines in the encoding,
but had little luck finding reference to that using google, but I want
to make sure I am safe.
my url looks like this:
http://my.local/index.php/widget/fil.../aHR0cDovL21lZ...
// functions to code url segments ...
function base64_url_enco de($input) {
return strtr(base64_en code($input), '+/=', '-_.');
}
function base64_url_deco de($input) {
return base64_decode(s trtr($input, '-_.', '+/='));
}

I haven't seen any base64 implementations which use a newline character
- and I doubt there are any (it's not a printable character).

But rather then use strstr, just urlencode the results from
base64_encode( ).

uuencode does it (presumably because it was written when line-oriented
terminals were the common way of interacting with data) and MIME does
it (because SMTP is line oriented). But AFAIK the php implementation
doesn't.

It's a handy way to move data around because:
$enc=str_replac e('=','', base64_encode($ data)); // the trailing '=='
is not required
urlencode($enc) === mysql_real_esca pe($enc) === htmlentities($e nc)
=== addslashes($enc ) === stripslashes($e nc) === $enc

C.

Yes, that's a different way to do it. I've always used base64_encode,
mostly out of habit.

--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===

[GuangXiN]

Jerry Stuckle wrote:

C. (http://symcbean.blogspot.com/) wrote:

>On Jun 6, 3:34 am, Jerry Stuckle <jstuck...@attg lobal.netwrote:

>>wbsurf...@yah oo.com wrote:
I am using the two functions below to encode part of a url. I had seen
that someone said base64 can sometimes add newlines in the encoding,
but had little luck finding reference to that using google, but I want
to make sure I am safe.
my url looks like this:
http://my.local/index.php/widget/fil.../aHR0cDovL21lZ...

// functions to code url segments ...
function base64_url_enco de($input) {
return strtr(base64_en code($input), '+/=', '-_.');
}
function base64_url_deco de($input) {
return base64_decode(s trtr($input, '-_.', '+/='));
}
I haven't seen any base64 implementations which use a newline character
- and I doubt there are any (it's not a printable character).

But rather then use strstr, just urlencode the results from
base64_encode ().

uuencode does it (presumably because it was written when line-oriented
terminals were the common way of interacting with data) and MIME does
it (because SMTP is line oriented). But AFAIK the php implementation
doesn't.

It's a handy way to move data around because:
$enc=str_replac e('=','', base64_encode($ data)); // the trailing '=='
is not required
urlencode($enc) === mysql_real_esca pe($enc) === htmlentities($e nc)
=== addslashes($enc ) === stripslashes($e nc) === $enc

C.

Yes, that's a different way to do it. I've always used base64_encode,
mostly out of habit.

the base64_encode function will never add any newline to result string,
but in the description of RFC 2045, base64ed string should be splited by
\r\n every 76 characters.

[Jerry Stuckle]

GuangXiN wrote:

Jerry Stuckle wrote:

>C. (http://symcbean.blogspot.com/) wrote:

>>On Jun 6, 3:34 am, Jerry Stuckle <jstuck...@attg lobal.netwrote:
wbsurf...@ya hoo.com wrote:
I am using the two functions below to encode part of a url. I had seen
that someone said base64 can sometimes add newlines in the encoding,
but had little luck finding reference to that using google, but I want
to make sure I am safe.
my url looks like this:
http://my.local/index.php/widget/fil.../aHR0cDovL21lZ...
>
// functions to code url segments ...
function base64_url_enco de($input) {
return strtr(base64_en code($input), '+/=', '-_.');
}
function base64_url_deco de($input) {
return base64_decode(s trtr($input, '-_.', '+/='));
}
I haven't seen any base64 implementations which use a newline character
- and I doubt there are any (it's not a printable character).

But rather then use strstr, just urlencode the results from
base64_encod e().
uuencode does it (presumably because it was written when line-oriented
terminals were the common way of interacting with data) and MIME does
it (because SMTP is line oriented). But AFAIK the php implementation
doesn't.

It's a handy way to move data around because:
$enc=str_replac e('=','', base64_encode($ data)); // the trailing '=='
is not required
urlencode($enc) === mysql_real_esca pe($enc) === htmlentities($e nc)
=== addslashes($enc ) === stripslashes($e nc) === $enc

C.

Yes, that's a different way to do it. I've always used base64_encode,
mostly out of habit.

the base64_encode function will never add any newline to result string,
but in the description of RFC 2045, base64ed string should be splited by
\r\n every 76 characters.

This RFC is discussing how to use bas64 encoding in email - which has
absolutely nothing to do with the topic at hand.
--
=============== ===
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
js*******@attgl obal.net
=============== ===