| freemangordon | Wizzup: help: https://datatracker.ietf.org/doc/html/rfc3711#section-9.5 | 07:57 |
|---|---|---|
| freemangordon | https://github.com/cisco/libsrtp/pull/757#issuecomment-2923383677 | 07:57 |
| freemangordon | do I read the RFC right, like, it allows null auth but discourages it? | 07:58 |
| Wizzup | reading | 11:15 |
| freemangordon | thanks | 11:17 |
| Wizzup | I mean from a glance it seems like yes, they do carve out some reasons to use NULL autentication | 11:18 |
| Wizzup | but SRTCP is not the same as SRTP | 11:18 |
| Wizzup | it does say: SRTCP MUST NOT be used with weak (or NULL) authentication. | 11:19 |
| Wizzup | but then carves out exceptions for SRTP (not SRTCP) | 11:19 |
| arno11 | freemangordon: btw i got sip working both ways with sphone and without last vcm changes | 12:37 |
| arno11 | modifying /usr/share/farstream/0.2/fsrtpconference/default-element-properties | 12:38 |
| arno11 | adding buffer-time=200000 and latency-time=40000 in [pulsesrc] | 12:39 |
| arno11 | outgoing sound is crappy but 100% it is my home network. will try with hspa later | 12:40 |
| arno11 | *100% sure | 12:40 |
| arno11 | (ofc those values are probably incorrect but it makes things kind of working) | 12:42 |
| arno11 | i've tested with tcp between leste n900 (ippi) and android (linphone) | 12:43 |
| arno11 | i think i made some changes in FS properties with chimaera to make sip working with sphone too. i need to check in my chimaera sd | 12:47 |
| dsc_ | arno11: fyi some conversations updates since last few days | 12:47 |
| arno11 | ah ok cool will try a bit later | 12:47 |
| freemangordon | Wizzup: srtcp is 'control channel', right? | 12:50 |
| Wizzup | >SRTP has a sister protocol, called Secure RTCP (SRTCP); it securely provides the same functions to SRTP as the ones provided by RTCP to RTP. | 12:53 |
| Wizzup | (according to wikipedia, I didn't know until just now) | 12:54 |
| Wizzup | https://en.wikipedia.org/wiki/Secure_Real-time_Transport_Protocol | 12:54 |
| Wizzup | Utilization of SRTP or SRTCP is optional in RTP or RTCP applications; but even if SRTP or SRTCP are used, all provided features (such as encryption and authentication) are optional and can be separately enabled or disabled. The only exception is the message authentication feature which is indispensable and required when using SRTCP. | 12:54 |
| freemangordon | ok, so there is no point in arguing then | 13:00 |
| freemangordon | and we'll have to fix farstream | 13:01 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!