In the TiK Suggestions forum, jamesb posted on 5/22/00 12:54
============[ Quoting from other forum ]==============
How hard would it be to pass text through gpg (or pgp or any other
app that can process stdin and output to stdout) before sending it
over the wire?
This wouldn't be the best way for encrypting chat, but it would be
suitable until we have a better, more widespread solution.
For example, I could agree with someone (via encrypted e-mail) to
use a specific phrase or word for encrypting our IM sessions for this
week/month/whatever. Then I could put that phrase/word into a file
(I know the problems this poses) and TiK could pre-process it by
sending the real text to gpg on stdin like this:
(One problem I can see however, is that the output would be considerably
larger than the original text and might be considered a flood by the TOC
server. :-\ )
===========[ End quoted message ]========
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Many encryption libraries also include gzip-style compression
which for plain text can often offset the expansion seen in
ASCII 4:3 expansion through things like Base64 encoding.
What's needed is a stream cipher, BUT yes, your idea of using
PGP or GNUpg as a stop-gap is quite doable from an add-on
plugin dealing at the RAW send/receive level.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the TiK Suggestions forum, jamesb posted on 5/22/00 12:54
============[ Quoting from other forum ]==============
How hard would it be to pass text through gpg (or pgp or any other
app that can process stdin and output to stdout) before sending it
over the wire?
This wouldn't be the best way for encrypting chat, but it would be
suitable until we have a better, more widespread solution.
For example, I could agree with someone (via encrypted e-mail) to
use a specific phrase or word for encrypting our IM sessions for this
week/month/whatever. Then I could put that phrase/word into a file
(I know the problems this poses) and TiK could pre-process it by
sending the real text to gpg on stdin like this:
gpg -c --armor --passphrase-fd 4 4<file_containing_password.
(One problem I can see however, is that the output would be considerably
larger than the original text and might be considered a flood by the TOC
server. :-\ )
===========[ End quoted message ]========
Many encryption libraries also include gzip-style compression
which for plain text can often offset the expansion seen in
ASCII 4:3 expansion through things like Base64 encoding.
What's needed is a stream cipher, BUT yes, your idea of using
PGP or GNUpg as a stop-gap is quite doable from an add-on
plugin dealing at the RAW send/receive level.