Topic: seems broken now
I just upgraded and now I can't sign anything. It fails with my password.
I can use gpg2 --clearsign
with no problems but it seems to fail no matter what key I specify in firegpg.
Forum for the FireGPG's extention. (!Don't post too links or wait we unban your, akismet is very aggressive)
You are not logged in. Please login or register.
I just upgraded and now I can't sign anything. It fails with my password.
I can use gpg2 --clearsign
with no problems but it seems to fail no matter what key I specify in firegpg.
You're on windows or linux ? Is the gpg's path good ? Can you decrypt, crypt and verify ?
Thanks for the precisions.
You're on windows or linux ? Is the gpg's path good ? Can you decrypt, crypt and verify ?
Thanks for the precisions.
Sorry linux
firegpg 0.4.2
firefox 2.0.0.4
gpg2 2.0.1
I can verify but I just learned something about pgp the editor might mess up the message before sending it because it may have to word wrap
I didn't understand the "also how do you encrypt with gpg2 to get it in email send-able form?". Simply use FireGPG's editor...
No, it's should work... Is your passwork with very stranges charackters ? (like
yes I do have symbols in most of my passwords let me try ones without
We can send you a special version of FireGPG who do this...
With gpg, it's work ?
Try with a stupid password (like 123) and look if it's work...
Strange characters did not cause any of the problems it should be fine using any character combination. :-)
Following is my script to intercept gpg and copy important files for troubleshooting. :-/ sorry for accusing your plugin it wasn't your plugin at all it was me choosing gpg2 which completely ignores the --no-use-agent and the --passphrase-file options. I was also having issues because previous versions of my intercept script were messing up.
#!/bin/bash
# This script is to intercept arguments being passed to gpg and to
# copy the important files needed for trouble shooting.
# I needed to make sure the files contained what I thought they contained
# It was very helpful in trouble shooting the
# signature inside a signature problem
date=`date +%Y%m%d%H%M%S`
echo input args >>$0_passed_arguments_${date}
echo $* >>$0_passed_arguments_${date}
usgae()
{
echo $0 gpg arguments
}
longopts="quiet,no-tty,no-verbose,status-fd:,armor,version,"
longopts="${longopts}clearsign:,batch,default-key:,output:,"
longopts="${longopts}passphrase-file:,comment:,with-colons,"
longopts="${longopts}no-use-agent,list-secret-keys,"
longopts="${longopts}verify:,trust-model:"
shortopts="qhs"
argument()
{
echo $1|sed s/^\'// |sed s/\'$//
}
args=`getopt -l ${longopts} ${shortopts} $*`||error=1
if [ "${error}" = "1" ];then
usage
exit 1
fi
set -- ignored ${args}
for i
do
shift
if [ "$1" != "--" ];then
arglist="${arglist} `argument $1`"
fi
case "$1" in
--passphrase-file)
shift
arglist="${arglist} `argument $1`"
cat `argument $1` > $0_sent_password_${date}
continue;
;;
--verify)
shift
arglist="${arglist} `argument $1`"
cat `argument $1` > $0_verify_${date}
continue;
;;
--)
break;
;;
*)
echo unknown;
;;
esac
done
echo output args >>$0_passed_arguments_${date}
echo ${arglist} >>$0_passed_arguments_${date}
gpg ${arglist}
Last edited by jeff.sadowski (2007-07-10 17:17:32)
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 2 official extensions. Copyright © 2003–2009 PunBB.