View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002250 | GNUnet | GNS | public | 2012-04-02 11:00 | 2012-11-05 17:34 |
| Reporter | schanzen | Assigned To | schanzen | Due Date | |
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | Git master | ||||
| Target Version | 0.9.4 | Fixed in Version | 0.9.4 | ||
| Summary | 0002250: GNS proxy needs to speak SSL | ||||
| Description | The proxy does not speak SSL atm. Maybe use SSLsniff to implement this. The proxy needs to validate the server side certificate via LEHO and then generate its own for the .gnunet request for the client to verify (ie to make the browser happy) | ||||
| Tags | No tags attached. | ||||
| After some research I think it makes sense to use ss5p as a basis and then port the certificate generation from sslsniff into this. The http parsing can be done using mhd and curl. One disadvantage will be that we always have to mitm for ssl. Even for non .gnunet enabled services. * http://code.google.com/p/ss5p * http://www.thoughtcrime.org/software/sslsniff/ | |
| In SVN | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-04-02 11:00 | schanzen | New Issue | |
| 2012-04-02 11:00 | schanzen | Status | new => assigned |
| 2012-04-02 11:00 | schanzen | Assigned To | => schanzen |
| 2012-04-18 13:51 | Christian Grothoff | Severity | minor => feature |
| 2012-05-14 22:26 | schanzen | Note Added: 0005894 | |
| 2012-05-28 13:12 | Christian Grothoff | Product Version | => Git master |
| 2012-06-11 21:50 | schanzen | Note Added: 0006043 | |
| 2012-06-11 21:50 | schanzen | Status | assigned => resolved |
| 2012-06-11 21:50 | schanzen | Resolution | open => fixed |
| 2012-06-12 19:25 | Christian Grothoff | Fixed in Version | => 0.9.4 |
| 2012-06-12 19:25 | Christian Grothoff | Target Version | => 0.9.4 |
| 2012-11-05 17:34 | Christian Grothoff | Status | resolved => closed |