CVS log for loncom/LondConnection.pm

Up to [LON-CAPA] / loncom

Request diff between arbitrary revisions

Keyword substitution: kv
Default branch: MAIN

- Include verification of common name when creating SSL tunnel unless
  connecting to/from pre-2.12 node.
- $IO::Socket::SSL::DEBUG is set to current $DEBUG value so debugging
  from IO/Socket/SSL.pm is written to lond_errors or lonc_errors.

- Sanity checking

- Remove trailing whitespace.

- Verification of CN when creating SSL tunnel on multi-domain servers.
  CN is default lonid, i.e., one listed last for the node's hostname in
  hosts.tab and/or dns_hosts.tab.

- Remove linefeed from buildkey for consistency with lond.

- For 2.11
  Backport 1.55

- Support Certificate Revocation List checking when using SSL channel
  for key exchange during negotiation of connection to remote lond.

- Include verification of common name when creating SSL tunnel. Fall back
  to insecure connection (if allowed) if verification fails.

- Log hostID for completed deferred transactions in lonnet.perm.log.

- Use of LON-CAPA SSL certificates to create secure channel for exchange of
  encryption key between LON-CAPA nodes can be set to: "no", "yes", "req"
  (i.e., required) separately for outbound (i.e., lonc) and inbound connections
  (i.e., lond) in domain config (default domain only on a multi-domain server).
- Can differentiate between connections between nodes in same domain, nodes
  in same "internet" domain. and nodes in neither.
- Supercedes use of loncAllowInsecure and londAllowInsecure from loncapa.conf
  on each node.
- Run /home/httpd/perl/loncron --justreload (as www) after changing domain config

Fix timeout edgecase (But 6610?).

Add a 'ClientData' member to LondConnection and have loncnew use it to
properly keep track of which connection is which.
(Bug 6377 comment 43).

Turn on keepalive with the default timing for now.

- A bit of formatting.
- A bit more care when the timeout counter is reset.

- Bug 6377.  Revert TimeoutValue to 30 s.

Bug 6304:
- Timeout is reset after each successful send.
- Timeout was raised to 300 seconds.

- Distinctive courseID for Communities - all begin with 0
- LONCAPA::match_community will match this type of courseID
- Client session sends installed LON-CAPA version when initiating lonc/lond
  connection to remote server.
- Roles in Communities unavailable for user sessions hosted on LON-CAPA
  releases which predate 2.9.

- restore old timeout value

- fix log all

- eliminate any reading of hosts.tab from loncnew
- launch of lonc connection requires passing the lonid through the common
  launch socket
- dealyed messages getting sent again (requires loncnew using lonnet....)

Allow configuration files to be read in SLES10 when files are located in /etc/apache2.  lonnet now reads in from loncapa.conf and loncapa_apache.conf using Configuration::read_conf().

- $socket already exists and has the same value

- correcting some documentation

- have lond handle the inline sethost: cmd
- set the lond version in lonc which can handle this

- connections are now be hostname not lon machine id
- socket files are by hostname
- lonnet.pm prepends sethost:<lonid>: to each command
- LondConnection takes care of tracking with machine id the lond thinks it
    - it strips the sethost command if it's unneeded
    - it splits it into two seperate commands that it sends in order
      if lond needs to be told
    - eventually for lond of late enoyugh heritage it will just
      send the whole command

- the return value of chomp isn't the unchomped strign

- login on wether or not we should dump was backwards

- The second part of BUG#2330, removing the IPs from hosts.tab, converting loncnew/d to not expect them in there. Right now lond still needs them, so it does lookups on start up and SIGUSR2

Time stamp socket dumps so I can make sense of what's going on.

- Fixed defect in handling lond data that required decryption:  Had forgotton
  to put the trailing \n back in the string.   This causes lonc and its clients
  to hang waiting on completion.  This all implies BTW that eget is either never used
  or nobody has cared all this time that it wasn't working correctly !!?!

If the certificate files or host key are missing, than
switch to insecure authentication if allowed.  The idea
is this: After an upgrade to lond/lond ssl, you won't in general
have your signed host certificate yet.  We want to support uninterrupted
service until your certs are granted, so although the software is ssl
capable, it must, in the interim, do insecure authentication, if permitted
by the administrators.

One case not handled, and left not handled: if the lonCerts directory does not
exist the init:local key exchange cannot work.  This case can be ignored because
that diretory will be created as part of the update/upgrade.  If it does not exist
it's a sign of some other serious problem that ought to be fixed IMHO.

Turn down the logging volume now that the ssl stuff looks like it's functional.

Debug changes to get SSL and local file secure key exchanges done

Match parameter receiving to coding standard when # parameters is > 1.

- making the regexp effieceint

- correcting tabination

- Return an error condition on  Readable and Writable if socket is not defined...
- Do unto recv with eval as was done unto send in Writable.

- should prevent a logging death spiral when socket becomes undefined

-fix tabination

Add a pile of new states at connection setup to:
- Ask for the version of the remote lond.
- Set the domain of the remote lond to whatever we were asked toconnect to.

The trailing banner for dump should also go to stderr.

Redirect Dump -> stderr (was going to stdout) this s just to let those programs
that send stderr to file capture these dumps.

Debugging support for local configuration

- was throwing Event errors when it couldn't connect and marking things Dead

- print to STDOUT

Attempt to send "exit" to the lond partner on Shutdown in order to
try to force lond to exit promptly as well.

- Add SetDebugLevel to allow clients to control debugging output.
- Fix ReadConfig, ReadForeignConfig - needed to set configuration read flag
  else new would re-read the default config and wipe out lonManage's
  attempts to read foreign config files e.g.

Add function to set the module debug level.

Added ReadForeignConfig for use outside the LonCAPA environment (e.g. in lonManage).

Start building support for LondConnection.pm to be used by LonManage.
- Separate the configuration read from initialization:
  o Read if not read on first new using ReadConfig
  o Read if explicityl requeste by client doing LondConnection::ReadConfig
- Incorporate LONCAPA::Configuration textually so that LondConnection
  can be used outside of the LonCAPA environment (e.g. in lonManage).

Reduce the timeout

Move configuration read into a sub so that it can be called again on reinits.

Fix a little looney typo in a comment.

Correctly catch the refused string from peers that don't want to talk with us.
Honestly it was there initially.. just left the \n off the target of the comparison.

Make the socket/connection timeoutable during connection setup negotiation.
Otherwise  we can have some nasty cases where we are able to connect within
the socket connection timeout to a brain dead lond, but then the connection
setup negotiation (init etc.) can take much longer than our paitence permits to
complete.

1. Shorten the connection timeout to 5 seconds so lonnet in loncron
   doesn't take forever in the presence of down nodes.
2. Correct the handling of failed sends... an errno of 0 should be an error
   as it indicates a end file condition which means the remote peer hung up
   on us.  This is the probable cause of the compute bound looping of
   loncnew.

- Add some debugging to killthemall
- Add better error handling to LondReadable
- Remove tick logging in the timer handler.

Debug loncnew logging.

Add function to shutdown socket.

Support delayed transactions... this is done uniformly by encapsulating
transactions in an object ... a LondTransaction that is implemented by
LondTransaction.pm

- correcting pod formatting

- adding GNU GPL header

Move class that manages a connection from lonc to lond into the mainline
development cvs from the experimental sandbox.