Just download the zip-File, and unzip it onto your usb-pendrive. Then simply change into the folder gpg4usb at your usb-drive, and execute the binary in there
http://gpg4usb.cpunk.de/

M@tty,M@tty wrote:Unfortunately gnupg creates an empty folder in the Application Data folder upon startup, thus making the program not stealth.
In using GPG from the command line, a user can always put --homedir d:\gnupg (or whatever, perhaps even a relative directory) as the first element of the gpg command and the user app's folder will not be touched, so GPG from the command line can be stealth. Unfortuantely, this option cannot be added to the gpg.conf file to set a default home directory.Home directory:
===============
GnuPG makes use of a per user home directory to store its keys as well
as configuration files. The default home directory is a directory
named "gnupg" below the application data directory of the user. This
directory will be created if it does not exist. Being only a default,
it may be changed by setting the name of the home directory into the
Registry under the key HKEY_CURRENT_USER\Software\GNU\GnuPG using the
name "HomeDir". If an environment variable "GNUPGHOME" exists, this
even overrides the registry setting. The command line option
"--homedir" may be used to override all other settings of the home
directory.
In terms of program size, windows users can delete the linux elements and UPX-compress the start_windows.exe and gpg.exe files, resulting in a total size about 3.5 MB uncompressed.ashghost wrote: ...
The biggest problem I see is that it [gpg4usb] doesn't include robust key management. You can only import keys, you can't generate them (though I see that's on the to-do list).
...
Size: 23.6 MB uncompressed (a little big, but it is cross-platform)
...
Code: Select all
@echo off
:: This generates a new key pair for use in gpg4usb
%~dp0\bin\gpg --homedir %~dp0\keydb --gen-key
echo.
echo Operation complete. Press any key to close . . .
echo.
pause > nul
exit
Code: Select all
@echo off
:: This exports a public key from gpg4usb
echo.
set /p expkey=What is the KeyID (Name, Email or Number) of key to be exported? &::
%~dp0\bin\gpg --homedir %~dp0\keydb --armor -o "%~dp0\keydb\exportedkey.txt" --export "%expkey%"
Notepad "%~dp0\keydb\exportedkey.txt"
echo.
echo.
echo Exported key can be found in "%~dp0\keydb\exportedkey.txt".
echo.
echo Operation complete. Press any key to close . . .
echo.
pause > nul
exit
Code: Select all
@echo off
:: This clearsigns a text file with default signing key
echo.
set /p infile=What is dir:\path\filename of the text file to be signed? &::
echo.
echo.
set /p signedfile=What is dir:\path\filename of the output file with signature? &::
%~dp0\bin\gpg --homedir %~dp0\keydb -o "%signedfile%" --clearsign "%infile%"
Notepad "%signedfile%"
echo.
echo Signed file is "%signedfile%" .
echo Operation complete. Press any key to close . . .
echo.
pause > nul
exit
Code: Select all
@echo off
:: This verifies the signature of signed text in a text file
echo.
set /p sigfile=What is dir:\path\filename of the text file with signed text? &::
echo.
%~dp0\bin\gpg --homedir %~dp0\keydb -o "%signedfile%" --verify "%sigfile%"
echo.
echo.
echo Operation complete. Press any key to close . . .
echo.
pause > nul
exit
gpg4usb,gpg4usb wrote:Key Management is one important point on our TODO-List - before we work on this, binary-encryption is our top-priority and will be added in our next release.
Yucca,I'm not sure I understand your logic about risk, however, since you already support decryption which requires inputing a passphrase. Signing a message, which requires inputing a passphrase, would not be any riskier in a cafe than decrypting a message.