Debian Codegraph @

TODO

raw
1 Future plans are currently hanging on what people want out of this.
2 It appears
3
4 ^^^^^ ROAD MAP ^^^^^
5
6 \/\/\/ CURRENT VERSION \/\/\/
7
8 Version 0.7.0-beta
9 ------------------
10
11 * Renamed/relabled things to be consistent with a general PPPd service
12 * Total revamp of the configuration interface
13 - More abstract. Seperated the dialog (glade) details
14 from behaviour considerable. Implementation now simply
15 requires a glade file and a few lines of rather declarative
16 code.
17 * Add configuration options to select alternative ptys
18 - though only PPTP is actually defined at the moment
19 - Dial-up has been put in to the configuration as a
20 "feature preview" but it doesn't actually do anything
21 at present.
22 * Runs pppd asynchronously (allows pppd to fork)
23 * Crash on disconnect fixed.
24 * Added "debug mode" to show more detailed output.
25
26 Bugs:
27 * Does not seem to remember you login information even if
28 told to do so. (FIXED)
29 * Still only support for CHAP authentication.
30
31
32 Version 0.6.9
33 --------------------------------
34
35 Bugs:
36 * Possible NetworkManager crash on disconnect from VPN! (FIXED)
37 * Add dialog option to select different authentication methods
38 * Add dialog options for the rest of the 'hard coded' pppd options. (FIXED)
39
40
41
42 --------------------------------
43 PREHISTORY
44 Version 0.1.0 -> 0.5.0
45
46 Hi Nikolaus,
47
48 Yes, I've did quite a bit of work on it. Infact I totally revamped it to use a pppd plugin as it's helper. (Thus is can do the DNS + routing without modifications to your local /etc/ppp files)
49
50 Actually there is one exception... Many distros have an ip-up script which implements usepeerdns functionality thus replacing resolve.conf... This conflicts with NetworkManager's actions so may need to be removed. Sadly there appears to be no way to tell pppd NOT to execute /etc/ppp/ip-up if it exists!
51
52 Uses a pppd plugin to handle CHAP authentication (not sure of the V2 implications...) and ip-up functionality... It explicitly resolves the IP of the vpn server before starting pppd. And starts pppd with the pty option rather than letting pptp start pppd (as recomented by the pptp maintainer).
53
54 Sadly, I haven't quite figured out how I'm gonna get the username and password from the vpn-daemon to the pppd helper plugin infact I've just got my credentials hard coded in the plugin for testing!
55 The reason I haven't fixed that is that there is another strange behaviour where by the pptp vpn daemon (sometimes!) takes NM down when it exits!! It seems to seg fault but I can't find the cause. I've been really busy but would love somone to take a look at this. I can upload it in it's present state with instructions for where to insert your credentials if you/anyone else would be willing to try it and perhaps assist me.
56
57 tOnY
58
59
60 Nikolaus Filus wrote:
61
62 > Hi,
63 >
64 > I just managed to get your pptp plugin "working" for my university setup. It was a hard piece of work, since I'm not familiar with NM or pptp details. There are several issues to be fixed and I hope this report will be usefull for you. I don't attach patches as my modifications are just hacks :)
65 >
66 > 1. nm-pptp-service-pptp-helper
67 > The while-loop doesn't work, as I wasn't able to find a place, where
68 > foreign_option_%i shall be defined. It seems to me as if this code is incomplete and you wanted to scan through the whole environment and
69 > analyse the options. I had to manually add parsing of DNS, DNS1 and DNS2 which are set in my environment, or my resolv.conf is empty after connecting to the vpn.
70 >
71 > 2. nm-pptp-service
72 > encrypt-mppe was never attached to my pppd options and I had to add
73 >
74 > g_ptr_array_add (pptp_argv, (gpointer) "require-mschap-v2");
75 > g_ptr_array_add (pptp_argv, (gpointer) "mppe");
76 > g_ptr_array_add (pptp_argv, (gpointer) "required,stateless");
77 >
78 > outside the for-loop. As you can see, I also need the "require-mschap-v2" option. For this to work I need to specify a special remotename, which is NOT the hostname, as used in your code. This also requires a second line
79 > in chap-secrets.
80 >
81 > 3. configuration
82 > By default a new default route to ppp0 is specified, deleting the old one. I need to preserve it (by setting vpn-routes to 0.0.0.0/0) and add
83 >
84 > route add -host vpn-gw dev eth1
85 > route add default dev ppp0
86 >
87 > manually.
88 >
89 >
90 > With this modifications, I was able to connect the vpn at my university "using" networkmanager.
91 >
92 >
93 > Are you working on the pppd plugin as announced on the mailinglist? I would be glad to test it :)
94 >
95 >
96 > Thanks for your work
97 >
98 > Nikolaus Filus
99 >
100 >
101 >
102
103
104
105
106
107 Dan Williams wrote:
108
109 > But in your case, the pppd-vpn-service daemon could just do whatever it
110 > does to start the connection, but provide a dbus service that when
111 > called, returns the password and username. The pppd plugin would then
112 > call this dbus service and request the pass & user.
113 >
114 >
115 >
116 That is precisely what I intend and started implementing it. I just wanted to fix the strange and 'intermittent' segfault before
117 adding anymore complexity.
118
119 I only hesitated when naming the dbus service.
120
121 > There are some things to think hard about here though, namely the
122 > security of it. If you have a daemon providing a dbus service, unless
123 > you lock it down anyone can call its methods. So you'd have to make
124 > sure that you lock down the dbus policy for the service-daemon pretty
125 > tight. If you restrict it to just 'root'/uid 0, any root app could ask
126 > for the user and password. But then again, any 'root' app can do
127 > horrible things to your system anyway. So this might be an acceptable
128 > course of action.
129 >
130 >
131 I imagined that root access would be sufficient in this case too. I suppose
132 the only other way is for the vpn-daemon to pass some secret cookie to the
133 pppd on start up that the plugin then uses when asking for the user/pass later
134 but that too would open all kinds of security holes I suppose.
135
136 Anyway... A root process could overwrite the pppd plugin in /usr/lib with
137 something malicious so I can't see any possible gain. Just as a root process could
138 overwrite the vpnc binary with a script which 'tee' s the standard input to a file :-)
139
140 > Ideally this could be solved upstream in pppd. But at some point you
141 > simply do best-effort to hide the username & password from view, keep
142 > investigating how to do it better, and fix it a bit later.
143 >
144 >
145 Exactly. "Just works" not "Will at some future time just work" right :-)
146
147 tOnY