Class DefaultServerKexExtensionHandler

    • Constructor Detail

      • DefaultServerKexExtensionHandler

        public DefaultServerKexExtensionHandler()
    • Method Detail

      • handleKexInitProposal

        public void handleKexInitProposal​(Session session,
                                          boolean initiator,
                                          java.util.Map<KexProposalOption,​java.lang.String> proposal)
                                   throws java.lang.Exception
        Description copied from interface: KexExtensionHandler
        Invoked when a peer is ready to send the KEX options proposal or has received such a proposal. Note: this method is called during the negotiation phase even if isKexExtensionsAvailable returns false for the session.
        Specified by:
        handleKexInitProposal in interface KexExtensionHandler
        Parameters:
        session - The Session initiating or receiving the proposal
        initiator - true if the proposal is about to be sent, false if this is a proposal received from the peer.
        proposal - The proposal contents - Caveat emptor: the proposal is modifiable i.e., the handler can modify it before being sent or before being processed (if incoming)
        Throws:
        java.lang.Exception - If failed to handle the request
      • sendKexExtensions

        public void sendKexExtensions​(Session session,
                                      KexExtensionHandler.KexPhase phase)
                               throws java.lang.Exception
        Description copied from interface: KexExtensionHandler
        Invoked in order to allow the handler to send an SSH_MSG_EXT_INFO message. Note: this method is called only if isKexExtensionsAvailable returns true for the session.
        Specified by:
        sendKexExtensions in interface KexExtensionHandler
        Parameters:
        session - The Session
        phase - The phase at which the handler is invoked
        Throws:
        java.lang.Exception - If failed to handle the invocation
        See Also:
        RFC-8308 - section 2.4