Using uuencode for passwords isn't any more secure than plain text (maybe slightly: non-developers or too lazy to figure out what you used). mcrypt or even md5 is much more secure.
convert_uuencode
(PHP 5)
convert_uuencode — Codifica, mediante uuencode, una cadena
Descripción
string convert_uuencode
( string
$data
)convert_uuencode() codifica una cadena usando el algoritmo uuencode.
Uuencode traduce todas las cadenas (incluyendo las binarias) a secuencias de caracteres imprimibles, haciéndolas seguras para transmisiones de red. Los datos codificados de esta forma son aproximadamente 35% más largos que el original.
Parámetros
-
data -
Los datos a ser codificados.
Valores devueltos
Devuelve los datos codificados mediante uuencode.
Ejemplos
Ejemplo #1 Ejemplo de convert_uuencode()
<?php
$some_string = "prueba\ntexto texto\r\n";
echo convert_uuencode($some_string);
?>
Ver también
- convert_uudecode() - Descodifica una cadena codificada mediante uuencode
- base64_encode() - Codifica datos con MIME base64
abc518 at gmail dot com ¶
4 years ago
zash at zash dot se ¶
4 years ago
note that using base64 or uuencode to store data in a database is pretty useless. if you properly escape your data and use a binary field (BLOB etc) there is no problem.
allali at labri dot fr ¶
5 years ago
if you want to use convert_uuencode with command uudecode you must insert a line "begin %s %s\n" at the beginning and "end\n" at the end:
<?php
echo "begin 644 hello.txt\n";
echo convert_uuencode("hello");
echo "end\n";
?>
the first arg. after begin is the mode (destination file rights), the second is the destination file name.
Then you can do a wget followed by a uudecode.
JA.
root at mantoru dot de ¶
5 years ago
@Craig's note: base64_encode() is better suited for that. In fact, it produces smaller output and operates slightly faster. I did a little benchmark -- here are my findings:
File: JPG, 631614 bytes
== Base64 ==
execution time: 0.0039639472961426 secs
output length: 842152
== UUencode ==
execution time: 0.004105806350708 secs
output length: 870226
tmaschler at NOSPAM dot ditf-denkendorf dot de ¶
6 years ago
Note to the tip of Craig at frostycoolslug dot com:
If you are using fulltext functionality on columns with uuencoded texts, collations will not work. You might prefer to pass the text escaped to the database engine.
nmmm at nmmm dot nu ¶
7 years ago
uuencode is recognisable as email attachment in Ms Outlook, but in Outlook Express (at least in older versions) - is not.
This is shell script, but it may give you an idea how you can send attachments using uuencode:
cat file.bin | uuencode file.bin | mail someone@domain.com -s "file.bin"
uuencode mail attachments from other point of wiev are deprecated. However I use such technic for years now and it work well.
aidan at php dot net ¶
7 years ago
This functionality is now implemented in the PEAR package PHP_Compat.
More information about using this function without upgrading your version of PHP can be found on the below link:
http://pear.php.net/package/PHP_Compat
Craig at frostycoolslug dot com ¶
8 years ago
This function can be useful if you wish to store files in a MySQL database, it will save any problems with obscure binary data breaking the queries.
just remember to convery-uudecode before you try to use the data again.
(A common example of something that uses this system, would be email attachments)
