aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorrhatto <rhatto>2005-08-08 02:21:50 +0000
committerrhatto <rhatto>2005-08-08 02:21:50 +0000
commit62cc6406658baae7884f32f82a2021d265439dee (patch)
treed8c5eb8adef9db7190cdfa0f0681d218eed1cd70
parent105e4b25cfb073b1d70ee2790c3bcf45678fd339 (diff)
downloadfirma-62cc6406658baae7884f32f82a2021d265439dee.tar.gz
firma-62cc6406658baae7884f32f82a2021d265439dee.tar.bz2
minor changes
-rwxr-xr-xGUIDELINES105
-rwxr-xr-xREADME3
-rwxr-xr-xfirma2
3 files changed, 108 insertions, 2 deletions
diff --git a/GUIDELINES b/GUIDELINES
new file mode 100755
index 0000000..8028132
--- /dev/null
+++ b/GUIDELINES
@@ -0,0 +1,105 @@
+Pequena politica de desenvolvimento pro firma
+---------------------------------------------
+
+Intuito: ajudar no controle do desenvolvimento para
+ que o codigo nao estufe de lixo e que se mantenha seguro.
+
+Apos qualquer adicao no firma, efetue o seguinte procedimento
+-------------------------------------------------------------
+
+ - Coloque as novas variaveis criadas na lista de variaveis
+ - Coloque as novas funcoes criadas na lista de funcoes
+ - Coloque os novos arrays na variavei USED_ARRAYS
+ - Se estiver usando um comando unix, verifique se o mesmo jah estah listado
+ na lista de programas, caso contrario adicione-o
+
+Uso de variaveis
+----------------
+
+ - Variaves globais: uppercase
+ - Variaves locais a uma funcao ou rotina: lowercase, devem ser zeradas depois do uso
+ - Cuidado com a inicializacao, zerar tudo quando nao mais necessario
+
+Listagem
+--------
+
+- funcoes utilizadas:
+
+ usage
+ version
+ check_config
+ get_gpg_stderr
+ get_subscribers_list
+ get_message
+ get_gpg_message
+ get_message_headers
+ message_list
+ message_list_error
+ message_list_return
+ process_message
+ newlist
+ gpg_args
+ list_admin
+ choose_uid
+
+- variaveis utilizadas:
+
+ - via arquivo de configuracao
+
+ MAIL
+ MAIL_ARGS
+ GPG
+ LISTNAME
+ LISTADMIN
+ GPGDIR
+ PASSWD
+
+ - direto no script
+
+ FIRMA_LIST_PATH
+ VERSION
+ LINES
+ FROM
+ FROMADD
+ DATE
+ SUBJECT
+ EMAIl (mudar para lowercase?)
+
+ CONFIG
+ CONFIG_PATH
+ CONFIG_FILE
+
+ DESCRIPTION
+
+ GPGFLAGS
+ GPGCOMMAND
+ GPGLIST
+ GPGDECRYPT
+ GPGENCRYPT
+
+ KEYID
+
+ - variaveis auxiliares: x, n, signal
+
+ - arrays
+
+ ver USED_ARRAYS
+ ADMINCOMMANDS
+
+- Comandos Unix:
+
+ $MAIL
+ $GPG
+
+ echo
+ cat
+ grep
+ wc
+ tr
+ cut
+ sed
+ mkdir
+ touch
+ chmod
+ basename
+ expect
diff --git a/README b/README
index 89fdf8d..85c7d35 100755
--- a/README
+++ b/README
@@ -41,7 +41,8 @@ Everyone has the private key X The server has the private key
When using a encrypted mailing list software, one must choose between
keeping the private key in the server or send it to each of the
subscribers. We'll not consider the case where every subscribers encrypt
- the message to all recipients cause...
+ the message to all recipients cause this has none automation in the
+ process we are looking for.
For the second option we have the NAH6 Mailman patch,
http://mail.python.org/pipermail/mailman-coders/2003-June/000506.html
diff --git a/firma b/firma
index 6488a68..ec0fc9d 100755
--- a/firma
+++ b/firma
@@ -47,7 +47,7 @@ function check_config {
exit 1
elif [ ! -d $GPGDIR -o ! -f $GPGDIR/pubring.gpg -o ! -f $GPGDIR/secring.gpg ]; then
echo "$CONFIG_FILE: GPG home directory ($GPGDIR) or the GPG keyrings could not be found."
- exit 1
+ exit 1
elif [ -z "$(cat $CONFIG | grep -o ^PASSWD=\'[^\']*\'$)" -o \
-z "$(echo -n $PASSWD)" -o \
"$(echo -n $PASSWD | wc -m)" -lt "25" -o \