| 167 | * future plans? mid term, long term? |
| 168 | * 2.4 (mid-term goals for 2.x) |
| 169 | * interactive service! MUST HAVE |
| 170 | * timeout stuff fixes (Arne) |
| 171 | * peer-id MUST HAVE |
| 172 | * inotify "good chance", async plugin "depends on time" |
| 173 | * IPv6 gateway handling - really should go in, but cron2 has no time :( - depends on how the remaining schedule surrounding 2.4 goes |
| 174 | * AEAD/GCM - code is there, not performing nicely yet - MUST HAVE |
| 175 | * EC with external keys is not working yet - "nice to have", nobody working on it, not actually hard, just "many small pieces to touch" |
| 176 | * new data packet format (COMPRESS_V2) |
| 177 | * NTLMv2 proxy fixes (in 2.4.0 and 2.3.x, please - bugfix!) |
| 178 | * new windows installer for gui and everything (mattock), fixes lots of bugs, should be in 2.4.0 - MUST HAVE |
| 179 | * rough timeline: march 2015 for 2.4.0-RC? |
| 180 | * coding style change right before 2.4.0-RC |
| 181 | * improve systemd support (patches on the list) |
| 182 | * --enable/disable-ssl -> remove #ifdefs |
| 183 | * get rid of "useless #define" - find your pet peeve, ask on the list, send patch if feature-ACK |
| 184 | * look at trac |
| 185 | * auth-user-pass inline (patch from pekster?) - status? followup on it? |
| 186 | * GOST (nice to have, but no pressing need now - Heiko to rebase to master, overlap with AEAD for "newer openssl APIs"? - look at it) |
| 187 | * 2.5 (long term goal for 2.x) |
| 188 | * multiple server sockets (TCP+UDP) |
| 189 | * multiple threads ("however it might look like in the end"), depending on the performance bottlenecks discovered |
| 190 | * improved testing framework (andj) - MUST HAVE, some stuff might go to 2.4 |
| 191 | * isolate functionality better (no central context everywhere, gets into the way of testing) (syzzer) |
| 192 | * better document internal API and wire protocol - go for a (personal) RFC? (syzzer/james) |
| 193 | * cipher negotiation |
| 194 | * 3.0 (mid term and long term)? |
| 195 | * today: solid client (iOS, Android) |
| 196 | * work being done on adding server functionality |
| 197 | * James feels more comfortable about "putting it out to the public" when it has (basic) server functionality |
| 198 | * CLA issues still open - current state: discussed inside OpenVPN Tech, "nearly done"; similar to Google CLA for Android |
| 199 | * 3 being used as a testbed for new ideas |
| 200 | * James: "I've watched python 2 to 3 deseaster, learned from it" - on the wire protocol will be 100% compatible, most client config stuff is compatible |
| 201 | * Andj: splitting community resources is tricky, James agrees |
| 202 | * Heiko: it would be nice to have a "cli wrapper" that presents the same cli + mgmt interface to "GUI users" (like Tunnelblick, etc.) |
| 203 | * James: agree, mgmt interface would be good |
| 204 | * Arne: I can push an Android version with my gui, if James is comfortable with it - James: "when I'm comfortable with the code, still very much refactoring going on, so wait for the server functionality to be done" |
| 205 | * Andj: multithreading? James: it's sort of thread-agnostic, but there is no active multithreading functionality yet |
| 206 | * multi-socket server is actually very easy, as you just create a few ASIO socket objects and listen to them (and it's **fast** too!) |
| 207 | |
| 208 | * weekly community meetings: **new time** Monday, 20:00-22:00 european local time, make it more frequently again - first meeting: Monday 21st |
| 209 | |