Skip to content

fix #918#919

Merged
slingamn merged 8 commits intoergochat:masterfrom
slingamn:issue918_standard_config
Apr 1, 2020
Merged

fix #918#919
slingamn merged 8 commits intoergochat:masterfrom
slingamn:issue918_standard_config

Conversation

@slingamn
Copy link
Copy Markdown
Member

This is the diff from oragono.yaml to conventional.yaml (I decided against "standard" to suggest that oragono.yaml violates any standards --- AFAICT it does not):

diff --git a/oragono.yaml b/conventional.yaml
index 36813370..cd085787 100644
--- a/oragono.yaml
+++ b/conventional.yaml
@@ -1,7 +1,7 @@
-# This is the default config file for Oragono.
-# It contains recommended defaults for all settings, including some behaviors
-# that differ from conventional ircds. See conventional.yaml for a config
-# with more "mainstream" behavior.
+# This is the "conventional" or "mainstream" config file for Oragono.
+# It tries to replicate the behavior of other ircds, at the cost of not
+# taking full advantage of Oragono's features. This config is suitable for use
+# in IRCv3 conformance testing.
 
 # network configuration
 network:
@@ -15,18 +15,11 @@ server:
 
     # addresses to listen on
     listeners:
-        # The standard plaintext port for IRC is 6667. Allowing plaintext over the
-        # public Internet poses serious security and privacy issues. Accordingly,
-        # we recommend using plaintext only on local (loopback) interfaces:
-        "127.0.0.1:6667": # (loopback ipv4, localhost-only)
-        "[::1]:6667":     # (loopback ipv6, localhost-only)
-        # If you need to serve plaintext on public interfaces, comment out the above
-        # two lines and uncomment the line below (which listens on all interfaces):
-        # ":6667":
-        # Alternately, if you have a TLS certificate issued by a recognized CA,
-        # you can configure port 6667 as an STS-only listener that only serves
-        # "redirects" to the TLS port, but doesn't allow chat. See the manual
-        # for details.
+        # This version of the config provides a public plaintext listener on
+        # port 6667 for testing and compatibility with legacy applications.
+        # We recommend disabling this listener in a production setting
+        # and replacing it with loopback-only listeners (see oragono.yaml):
+        ":6667":
 
         # The standard SSL/TLS port for IRC is 6697. This will listen on all interfaces:
         ":6697":
@@ -109,7 +102,7 @@ server:
     forward-confirm-hostnames: true
 
     # use ident protocol to get usernames
-    check-ident: false
+    check-ident: true
 
     # password to login to the server
     # generated using  "oragono genpasswd"
@@ -345,11 +338,11 @@ accounts:
         #
         # 'optional' matches the behavior of other NickServs, but 'strict' is
         # preferable if all your users can enable SASL.
-        method: strict
+        method: optional
 
         # allow users to set their own nickname enforcement status, e.g.,
         # to opt out of strict enforcement
-        allow-custom-enforcement: false
+        allow-custom-enforcement: true
 
         # rename-timeout - this is how long users have 'til they're renamed
         rename-timeout: 30s
@@ -373,7 +366,7 @@ accounts:
         # account name as their nickname. when combined with strict nickname
         # enforcement, this lets users treat nicknames and account names
         # as equivalent for the purpose of ban/invite/exception lists.
-        force-nick-equals-account: true
+        force-nick-equals-account: false
 
     # multiclient controls whether oragono allows multiple connections to
     # attach to the same client/nickname identity; this is part of the
@@ -388,7 +381,7 @@ accounts:
         # if this is disabled, clients have to opt in to bouncer functionality
         # using nickserv or the cap system. if it's enabled, they can opt out
         # via nickserv
-        allowed-by-default: true
+        allowed-by-default: false
 
         # whether to allow clients that remain on the server even
         # when they have no active connections. The possible values are:

I decided to recommend against allow-custom-enforcement. This is a little surprising but I think it's probably the right move, especially with force-nick-equals-account providing automatic nick changes after ns identify.

@DanielOaks
Copy link
Copy Markdown
Member

Nice, looks good. Thanks very much for this mate, appreciated~

@slingamn slingamn merged commit 6374a31 into ergochat:master Apr 1, 2020
@slingamn slingamn deleted the issue918_standard_config branch May 20, 2020 16:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants