Re: Client-Server Protocol in a more secure way?

Karsten Wemheuer <[email protected]> Fri, 16 Dec 2016 17:48:52 +0100
Newsgroups gmane.comp.telephony.fax.hylafax.devel
Message-ID <[email protected]>
Hi,

Am Freitag, den 16.12.2016, 08:30 -0800 schrieb Lee Howard:
> On 12/16/2016 06:27 AM, Karsten Wemheuer wrote:
> >=20
> > I can not search the archive of this mailing list, so excuse me, if
> > this question was asked before.
> >=20
> > The current implementation of the client-server HylaFax Protocol
> > ist
> > ftp based, so that the password is transferred as clear text.
> >=20
> > Are there any plans to do this in a more secure way? Maybe a
> > challenge
> > response mechanism or a ssl tunnel or ftps or sftp?
> It's something that has been discussed as a possibility, but I don't=C2=
=A0
> know that anyone is working on it.
>=20
> For those who have needed the communication encrypted I have
> typically=C2=A0
> seen them establish VPNs between the client and server... and then
> run=C2=A0
> the hfaxd communication over the VPN.

Thanks for Your quick response. I was hoping, someone is working on the
topic. Unfortunately a VPN is not an option for us.

Best regards,

Karsten


____________________ HylaFAX(tm) Developers Mailing List ____________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe [email protected] < /dev/null