The system is coming along nicely. I'm stuck at the moment, however, trying to determine the best way to go from socket monitoring to authentication handling. I can fork and have two processes, one for socket monitoring, one for the auth server, but then I can't easily share my linked list of people. I think I'm going to go for threads, as it is the only solution I can think of at the moment that will work the way I want it to.
tk: I guess weird is one way to describe it. It's just one of those ideas that just rushed into my head one day. Nothing prompted it, and I wasn't looking for new ideas (my list of projects is far too big as it stands).
Personally, I think it would be very useful. I would love to open up FTP, CVS, and other things to certain people, but they have dynamic IPs. I would also like this stuff available to me when I'm at the college. I prefer a more secure environment, and I like to keep most of my ports closed, as people often attempt to break in here. Using this, I can close almost anything that I don't want people getting into, and still access all of my ports from anywhere using a knocker program. Because the client has to do very little, I could probably even hack up a knocker in a shell script if I had to, as long as I remembered the "secret knock" sequence.
We have a new translator, amd, on the project, who will be translating into Estonian.
I hope to do a release of libpackman, libcomprex, and gpkg in the next couple of days. I'm trying to decide if I want to hold it off to do some changes, but I suspect those changes are going to end up being bigger than I anticipate. It has been a month or so since the last releases, I think, so I might as well release now before messing things up too badly :)