error using gpg....

i'm getting an error when I try to run gpg thru a thin client,

this is the command I'm using:

cat /home/cdb1/.passphrase |gpg --passphrase-fd 0 --output OUTPUT.TXT
--decrypt FILE.PGP > tmp 2>&1

this is the error in tmp:

gpg: cannot open /dev/tty: No such address or device

I'm using a thin client app called DBC Smart Client, it seems as if
this doesn't support the /dev/tty feature, it connects to our Linux
server from a windows workstation (DOS prompt) using TCP/IP.

Does anyone know a way around this ?

thanks in advance....

On Wed, 13 Jul 2005 10:22:55 -0700, dorantes mumbled something like this:

> i'm getting an error when I try to run gpg thru a thin client,
>
> this is the command I'm using:
>
> cat /home/cdb1/.passphrase |gpg --passphrase-fd 0 --output OUTPUT.TXT
> --decrypt FILE.PGP > tmp 2>&1
>
> this is the error in tmp:
>
> gpg: cannot open /dev/tty: No such address or device

<snip>

linux terminals are usually named /dev/ttyX with X being a number between
0 and whatever the upper limit of ttys is set to on your system.

For example on the Fedora Core 3 workstation I am currently using they run
from /dev/tty0 to /dev/tty63. There are also serial port ttys(for modem
connection and the like). On the same machine, these run from /dev/ttyS0
to /dev/ttyS75.

I don't have a solution to your problem, but I hope the above helps.
--
Rinso
/\
/ \
/wizz\
~~~~~~~~~~~~

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rincewind wrote:
> On Wed, 13 Jul 2005 10:22:55 -0700, dorantes mumbled something like this:
>
>
>>i'm getting an error when I try to run gpg thru a thin client,
>>
>>this is the command I'm using:
>>
>>cat /home/cdb1/.passphrase |gpg --passphrase-fd 0 --output OUTPUT.TXT
>>--decrypt FILE.PGP > tmp 2>&1
>>
>>this is the error in tmp:
>>
>>gpg: cannot open /dev/tty: No such address or device
>
>
> <snip>
>
> linux terminals are usually named /dev/ttyX with X being a number between
> 0 and whatever the upper limit of ttys is set to on your system.

In addition, the generic devicename "/dev/tty" is made available to
access your specific /dev/ttyX device. That is to say, a program that
opens "/dev/tty" will open the /dev/ttyX that the user initiated the
process from. (This is a general statement, subject to the use of
process groups, process group leaders, and controlling TTYs).




- --

Lew Pitcher, IT Specialist, Enterprise Data Systems
Enterprise Technology Solutions, TD Bank Financial Group

(Opinions expressed here are my own, not my employer's)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)

iD8DBQFC1VfXagVFX4UWr64RAhadAJ0YRd8oNO7VDycuemsYxG kEbyXHhwCgpoCe
bCS7ulsxufqksO12dVc5YOs=
=Hzqw
-----END PGP SIGNATURE-----

On Wed, 13 Jul 2005 10:22:55 -0700, dorantes wrote:

[...]

> cat /home/cdb1/.passphrase |gpg --passphrase-fd 0 --output OUTPUT.TXT
> --decrypt FILE.PGP > tmp 2>&1

[...]

I might be all wrong about this but it seems I remember something from the
gpg instructions that specifically warns against piping the output of
another command into gpg. Structure your command according to their
instructions, with gpg as the first process, per instructions on their web
site. Best wishes.

> thanks in advance....

just FYI to all, what fixed my problem was the --no-tty option and it
worked !!!

thanks for all of the input ...

On 13.07.2005, Lew Pitcher <Lew.Pitcher@td.com> wrote:
>
> Rincewind wrote:
>> On Wed, 13 Jul 2005 10:22:55 -0700, dorantes mumbled something like this:
>>
>>
>>>i'm getting an error when I try to run gpg thru a thin client,
>>>
>>>this is the command I'm using:
>>>
>>>cat /home/cdb1/.passphrase |gpg --passphrase-fd 0 --output OUTPUT.TXT
>>>--decrypt FILE.PGP > tmp 2>&1
>>>
>>>this is the error in tmp:
>>>
>>>gpg: cannot open /dev/tty: No such address or device
>>
>>
>> <snip>
>>
>> linux terminals are usually named /dev/ttyX with X being a number between
>> 0 and whatever the upper limit of ttys is set to on your system.
>
> In addition, the generic devicename "/dev/tty" is made available to
> access your specific /dev/ttyX device.

....as well as /dev/pts/* devices, depending on which terminal are you
connected to.

> That is to say, a program that
> opens "/dev/tty" will open the /dev/ttyX that the user initiated the
> process from. (This is a general statement, subject to the use of
> process groups, process group leaders, and controlling TTYs).

--
Feel free to correct my English
Stanislaw Klekot