VYSPER
  1. VYSPER
  2. VYSPER-285

Ability to communicate without encryption

    Details

    • Type: Wish Wish
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 0.7
    • Fix Version/s: None
    • Component/s: core protocol
    • Labels:
      None
    • Environment:
      windows/linux/android

      Description

      Hello,
      I have been toying with vysper for a while, but I haven't found way for TcpEndPoint to communicate only without encryption. I found method:

      "org.apache.vysper.xmpp.server.XMPPServer.getServerRuntimeContext().getServerFeatures().setStartTLSRequired(false);"

      but that's not working for me.

      Am I missing something? Is it possible? If not I think it should be.

        Activity

        Hide
        Bernd Fondermann added a comment -

        The follow up issue is now in JIRA VYSPER-287.
        NOTE: I'll not be able to spent time implementing GSSAPI or the like at the moment. Sorry for that.

        Show
        Bernd Fondermann added a comment - The follow up issue is now in JIRA VYSPER-287 . NOTE: I'll not be able to spent time implementing GSSAPI or the like at the moment. Sorry for that.
        Hide
        Bernd Fondermann added a comment -

        Fixing this leads to follow-up problem: we currently only offer PLAIN SASL auth, which is sufficiently secure over TLS, but not without.

        Show
        Bernd Fondermann added a comment - Fixing this leads to follow-up problem: we currently only offer PLAIN SASL auth, which is sufficiently secure over TLS, but not without.
        Hide
        Bernd Fondermann added a comment -

        At first, the call you gave is absolutely correct and should work.

        And yes, Vysper in this case does NOT anounce StartTLS as REQUIRED.
        However, since we do not anounce anything else in the related stanza (such as SASL mechanisms), this counts as if StartTLS was required NONETHELESS.

        I'm working on a patch.

        Show
        Bernd Fondermann added a comment - At first, the call you gave is absolutely correct and should work. And yes, Vysper in this case does NOT anounce StartTLS as REQUIRED. However, since we do not anounce anything else in the related stanza (such as SASL mechanisms), this counts as if StartTLS was required NONETHELESS. I'm working on a patch.

          People

          • Assignee:
            Bernd Fondermann
            Reporter:
            Kaja Hovi
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development