Clint,
 
If I properly understand you the https (ssl) support is already embedded by default? I prefer to build Unicon myself so to add some libraries or definitions is not a problem too.
As for ssl keys - is it possible to generate their with help of ssh-keygen, for example? I use git portable client on my Windows computer. SSL key by default shall be just placed to user's home directory.
Could you clarify this? I would like to check https:// with Unicon.
Sergey
 
03.08.2016, 09:14, "Jeffery, Clint (jeffe...@uidaho.edu)" <jeffe...@uidaho.edu>:

http has been in the messaging facilities since 2001 or earlier.  It is straightforward. The code was by Steve Lumos and we have improved it a bit since then.

 

https preliminary support works, but is not yet mature.  I have not adequately documented or publicized it, because I am not satisfied with the usability yet.

You could say that I consider it not finished. Here are a couple of the issues.

 

https depends on a particular API provided by a C library, libssl. If you have libssl headers and libraries, https may be built into your Unicon. I am not sure how universal libssl is. If Jafar says Windows and Mac builds HAVE_SSL, maybe it meets a minimal portability standard to be a general Unicon feature. We should add a feature for SSL to &features.  &features is getting too long, by the way, and checking for a feature needs to be re-architected.

 

https uses encryption keys which are not yet very well packaged/abstracted

in Unicon binary distributions.  If you do have Unicon binaries with https,

there may yet be some setup required for it to work.  Like for example, 

Unicon will want to know where your suite of encryption keys is. So far, the

code probably works on 1-2 operating systems with 1-2 popular web browsers'

keys. It needs to be made more portable.


cheers,

Clint


From: Jafar Al-Gharaibeh <to.ja...@gmail.com>
Sent: Tuesday, August 2, 2016 9:57:07 PM
To: Sergey Logichev; Unicon group
Subject: Re: [Unicon-group] HTTPS and FTP protocols
 

Not too long ago, Clint added preliminary support for SSL, which should pave the way for https. Not sure how far along he got it or if he managed to get https to work in Unicon. As to why we don't have https, ftp or several other protocols for that matter, the answer is the scarcity of contributors. The Unicon Project is underfunded and understaffed. We want more people to get involved in the development :-)
 
Cheers,
Jafar   

On Tue, Aug 2, 2016 at 11:36 PM Sergey Logichev <slogic...@yandex.ru> wrote:
Yes, I mean exactly https:// and ftp://
 
03.08.2016, 07:28, "Jafar Al-Gharaibeh" <to.ja...@gmail.com>:
Do you mean HTTPS? Because HTTP is supported.
--Jafar

On Tue, Aug 2, 2016, 10:53 PM Sergey Logichev <slogic...@yandex.ru> wrote:
Hello!
I would appreciate if someone could clarify why HTTP and FTP protocols were not implemented in Unicon networking?
Maybe it is planned for future?
Thanks,
Sergey
 
------------------------------------------------------------------------------
_______________________________________________
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group
--

-- Sent From My Smartphone

--

-- Sent From My Smartphone

------------------------------------------------------------------------------
_______________________________________________
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group

Reply via email to