| 01:04.12 | *** join/#asterisk-dev mjordan (~mjordan@user-69-1-6-49.knology.net) |
| 01:04.12 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 01:54.09 | *** join/#asterisk-dev zh-home (~zerohalo@74.61.196.236) |
| 02:25.15 | *** join/#asterisk-dev mjordan (~mjordan@user-69-1-6-49.knology.net) |
| 02:25.15 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 03:30.47 | *** join/#asterisk-dev moy (~moy@173.239.155.74) |
| 05:11.42 | *** join/#asterisk-dev Qwell (~north@pdpc/sponsor/digium/Qwell) |
| 05:11.42 | *** mode/#asterisk-dev [+o Qwell] by ChanServ |
| 05:34.41 | *** part/#asterisk-dev mbrevda (u5500@gateway/web/irccloud.com/x-toqvhnrmmazxpqpa) |
| 05:46.23 | *** join/#asterisk-dev oej (~olle@h87-96-134-129.dynamic.se.alltele.net) |
| 05:46.23 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 05:57.47 | *** join/#asterisk-dev schmidts (~schmidts@Lo20-rt01.lm33.sil.at) |
| 05:57.49 | schmidts | good morning |
| 06:18.43 | *** join/#asterisk-dev file (~file@asterisk/developer-and-muffin-lover/file) |
| 06:18.43 | *** mode/#asterisk-dev [+o file] by ChanServ |
| 06:48.14 | *** join/#asterisk-dev oej (~olle@h87-96-134-129.dynamic.se.alltele.net) |
| 06:48.14 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 06:49.23 | schmidts | morning oej |
| 06:49.39 | oej | Hello Schmidts |
| 06:49.42 | oej | Morning folks! |
| 06:56.40 | *** join/#asterisk-dev acidfoo (~nib@modemcable094.94-70-69.static.videotron.ca) |
| 08:10.11 | *** join/#asterisk-dev tzafrir_laptop (~tzafrir@local.xorcom.com) |
| 08:10.11 | *** mode/#asterisk-dev [+o tzafrir_laptop] by ChanServ |
| 09:23.11 | *** join/#asterisk-dev hehol (~hehol@2001:1438:1009:200:8059:878a:3a11:96b4) |
| 09:33.12 | *** join/#asterisk-dev wdoekes2 (~walter@wjd.osso.nl) |
| 10:34.35 | oej | Afternoon folks |
| 10:57.49 | WIMPy | Can someone please remove "pastebin" from https://issues.asterisk.org/jira/browse/ASTERISK-19434 ? |
| 11:10.08 | schmidts | Wimpy sure you want this removed? |
| 11:14.54 | WIMPy | Yes |
| 11:15.52 | schmidts | done |
| 11:16.08 | WIMPy | Thank you. |
| 11:16.14 | schmidts | your welcome :P |
| 11:36.01 | *** join/#asterisk-dev mjordan (~mjordan@user-69-1-6-49.knology.net) |
| 11:36.01 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 11:51.55 | leifmadsen | morning all |
| 11:52.04 | mjordan | leifmadsen: morning |
| 11:53.21 | leifmadsen | mjordan: wow, in early today! |
| 11:53.28 | mjordan | nah, on the couch at home |
| 11:53.34 | leifmadsen | most excellent |
| 11:53.52 | leifmadsen | just walked into my office... about to try and figure out why someone things I owe them money :) |
| 11:53.59 | leifmadsen | s/things/thinks/ |
| 11:54.30 | mjordan | darn system of goods & services |
| 11:54.44 | leifmadsen | indeed! |
| 11:54.47 | leifmadsen | I just want the goods! |
| 11:55.02 | leifmadsen | and for some reason I woke up and can't hear out of my left ear |
| 11:56.14 | mjordan | that's no good. I imagine you use that ear. |
| 11:56.16 | mvanbaak | morning |
| 11:56.25 | leifmadsen | mjordan: both of them yes! |
| 11:56.29 | leifmadsen | mvanbaak: howdy! |
| 11:56.34 | leifmadsen | mvanbaak: it's not afternoon where you are! |
| 11:56.40 | mjordan | ...and its time to get ready - be back in about an hour |
| 11:56.48 | *** part/#asterisk-dev mjordan (~mjordan@user-69-1-6-49.knology.net) |
| 11:56.52 | mvanbaak | leifmadsen: normally you use your left ear for phonecalls? maybe you used it too much |
| 11:57.02 | mvanbaak | leifmadsen: uhhuh, 8:56 in the morning |
| 11:57.17 | leifmadsen | mvanbaak: I tend to use speakerphone a lot |
| 11:57.18 | mvanbaak | leifmadsen: just walked into my office with a mug of coffee |
| 11:57.19 | leifmadsen | mvanbaak: yay! |
| 11:57.23 | leifmadsen | mvanbaak: same here |
| 11:57.27 | leifmadsen | 7:57am here |
| 11:59.40 | mvanbaak | damn, already 32 celcius here |
| 11:59.46 | mvanbaak | this is going to be a hot day |
| 12:06.05 | *** join/#asterisk-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 12:06.05 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 12:24.34 | *** join/#asterisk-dev oron_laptop (~oron_lapt@local.xorcom.com) |
| 13:12.33 | *** join/#asterisk-dev mjordan (~mjordan@nat/digium/x-urrhahtfahbltjwd) |
| 13:12.33 | *** mode/#asterisk-dev [+o mjordan] by ChanServ |
| 13:21.10 | *** join/#asterisk-dev serafie1 (~erin@nat/digium/x-uanohfawrxoidoud) |
| 13:28.45 | *** join/#asterisk-dev bchia (~Adium@user-24-236-95-16.knology.net) |
| 13:44.05 | pabelanger | bamboo un happy! RAWR! |
| 13:44.40 | *** join/#asterisk-dev putnopvut (~putnopvut@asterisk/master-of-queues/mmichelson) |
| 13:44.40 | *** mode/#asterisk-dev [+o putnopvut] by ChanServ |
| 13:45.19 | pabelanger | If only bamboo had a plugin this like: http://wiki.hudson-ci.org/display/HUDSON/Reviewboard+Plugin |
| 13:46.12 | pabelanger | then we could create a bamboo plan to download the reviewboard patch first, build asterisk will it and confirm asterisk compiles |
| 14:06.56 | *** join/#asterisk-dev otherwiseguy (~otherwise@69.76.221.79) |
| 14:08.01 | *** join/#asterisk-dev anonymouz666 (~anonymouz@189.25.124.163) |
| 14:09.42 | elguero | pabelanger: hopefully bamboo will be happy again soon |
| 14:11.23 | pabelanger | elguero: understood. I'm going to see if there are said hooks available. Then we don't have to worry about these compile issues again |
| 14:12.14 | elguero | pabelanger: I have it building now on my machine... what is the procedure for these situations? reviewboard and then commit? |
| 14:12.20 | mjordan | pabelanger: I think the end idea would be to point bamboo at a developer branch. |
| 14:12.25 | mjordan | elguero: yes plz |
| 14:12.45 | elguero | mjordan: no need for issue, just straight reviewboard? |
| 14:13.01 | mjordan | elguero: yup. If you'd like, you can link it to the original issue, since this was caused by that |
| 14:13.05 | mjordan | pulling a diff out of reviewboard is a nifty idea however. |
| 14:13.11 | elguero | okay |
| 14:13.45 | mjordan | I imagine since the diff is downloadable out of rb, we could script that. Wouldn't be as clean as a plug-in, but probably not terrible. |
| 14:29.35 | elguero | mjordan: review request posted; I figured it was important to get things building again on bamboo... I can work on adding some tests for security events with another patch if that is okay |
| 14:31.25 | mjordan | elguero: sounds good |
| 14:40.11 | *** join/#asterisk-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 14:40.12 | *** mode/#asterisk-dev [+o kpfleming] by ChanServ |
| 14:40.56 | *** join/#asterisk-dev sruffell (~Adium@asterisk/the-kernel-guy/sruffell) |
| 14:40.57 | *** mode/#asterisk-dev [+o sruffell] by ChanServ |
| 15:11.56 | *** join/#asterisk-dev bchia (~Adium@nat/digium/x-nkfdzqbtsgtclgdm) |
| 15:16.22 | *** join/#asterisk-dev anthm (~anthm@freeswitch/developer/anthm) |
| 15:35.19 | *** join/#asterisk-dev jeffg (~jeffg@pdpc/supporter/professional/jeffg) |
| 15:43.44 | WIMPy | Is there something to debug the search for priority lables in the dialplan? |
| 15:45.10 | leifmadsen | I don't think so... |
| 15:45.38 | *** join/#asterisk-dev philipp64|laptop (~chatzilla@38.100.211.103) |
| 15:46.13 | WIMPy | I'd like to find out under which circumstances they work and und which ones they fail. |
| 15:47.52 | leifmadsen | I don't think they should ever fail.... |
| 15:48.58 | WIMPy | But they do. |
| 15:49.22 | WIMPy | I guess it has to do with switches, but I'm not sure. |
| 16:01.07 | *** join/#asterisk-dev mbrevda (u5500@gateway/web/irccloud.com/x-toqvhnrmmazxpqpa) |
| 16:01.43 | mbrevda | leifmadsen: whats dose 19678 have to do with app_confbridge?? |
| 16:04.21 | leifmadsen | mbrevda: nothing -- misclicked |
| 16:05.34 | mbrevda | :) |
| 16:05.54 | mbrevda | leifmadsen: is there a second private ticket opened for all issues?! |
| 16:06.02 | Qwell | sort of |
| 16:06.19 | mbrevda | is that like the internal work queue? |
| 16:06.25 | Qwell | basically |
| 16:06.26 | leifmadsen | yes |
| 16:06.34 | leifmadsen | internal work queue for Digium developers |
| 16:06.49 | mbrevda | ah. right, obviously |
| 16:07.00 | mbrevda | dose jira not support like private comments or something? |
| 16:07.12 | Qwell | mbrevda: it's the tool we use to track stuff |
| 16:07.23 | Qwell | in the future it shouldn't be necessary, but for now it has to track an entire project |
| 16:07.39 | Qwell | and since we queue stuff across projects, there has to be that central project for the tracking |
| 16:08.12 | mbrevda | oh, I see |
| 16:14.15 | mjordan | putnopvunt: in the memory leak review 1875 addresses, does it happen only on reloads? Or does it happen during normal operation? |
| 16:15.37 | mjordan | heh, putnopvut: ^^^ |
| 16:16.30 | putnopvut | mjordan: I'm not 100% sure, but I *think* it can happen during normal operation. |
| 16:17.02 | mjordan | ugh, nevermind, it can. It will happen anything we call ast_tcptls_client_start, which occurs for any TLS client connection |
| 16:17.06 | putnopvut | That __ssl_setup() function is called by ast_tcptls_client_start |
| 16:17.07 | mjordan | in chan_sip |
| 16:17.12 | mjordan | yeah, I just saw that. |
| 16:17.16 | putnopvut | yerp |
| 16:18.37 | kpfleming | herp? derp? |
| 16:44.20 | tzafrir_laptop | sruffell, hi. Anything still holding off dahdi 2.6.1? |
| 16:57.12 | sruffell | nopeā¦.I'll tag it today |
| 17:04.01 | *** join/#asterisk-dev jeffg (~jeffg@pdpc/supporter/professional/jeffg) |
| 17:09.34 | *** join/#asterisk-dev frawd (~francois@142.Red-88-27-150.staticIP.rima-tde.net) |
| 17:29.09 | *** join/#asterisk-dev frawd (~francois@221.red-80-28-139.adsl.static.ccgg.telefonica.net) |
| 18:04.55 | *** join/#asterisk-dev oej (~olle@h87-96-134-129.dynamic.se.alltele.net) |
| 18:04.55 | *** mode/#asterisk-dev [+o oej] by ChanServ |
| 19:31.22 | *** join/#asterisk-dev ggtest (~ggtest@c207.134.154-241.clta.globetrotter.net) |
| 19:31.47 | ggtest | Hi guys! I have a question about this https://wiki.asterisk.org/wiki/display/AST/SIP+Security+Events |
| 19:32.06 | jsmith | ~ask |
| 19:32.07 | infobot | Questions in the channel should be specific, informative, complete, concise, and on-topic. Don't ask if you can ask a question first. Don't ask if a person is there; just ask what you intended to ask them. Better questions more frequently yield better answers. We are all here voluntarily or against our will. |
| 19:32.31 | ggtest | is "sip security events" ready to use in asterisk 10 ? |
| 19:34.15 | Qwell | "ready to use" isn't really a meaningful question. The code exists. The question is whether what's there will do what you need it to or not. |
| 19:34.15 | jsmith | Depends on what you mean by "ready to use" |
| 19:34.48 | jsmith | For example, they might not throw events for all the security things you're interested in, but the framework is certainly there, and ready for you to start experimenting with |
| 19:35.05 | ggtest | ok ok |
| 19:35.21 | ggtest | but where is the file that I need to edit ? |
| 19:35.55 | jsmith | You'll likely need to edit the source code to add events for the things you are interested in |
| 19:37.45 | ggtest | oh |
| 19:37.48 | Qwell | There is no specific file. If you need an event, you'll need to add it to the right place. |
| 19:38.15 | pabelanger | well, you need to enable it in logger.conf |
| 19:38.21 | pabelanger | if you want it to actually log |
| 19:38.27 | pabelanger | security => security |
| 19:38.52 | ggtest | and is it possible to send this security log into manager event ? |
| 19:40.45 | pabelanger | No, I think it only gets send to logger.c; a log file. You _should_ be able to log it to syslog. Sending it to manager would require somebody to write a patch for asterisk |
| 19:41.21 | ggtest | pabelanger, ok I understand |
| 19:41.44 | pabelanger | You've likely one of the only people using it, so don't expect much info on it yet |
| 19:41.49 | pabelanger | you're* |
| 19:42.26 | ggtest | yeah maybe, I would like to experiment with this |
| 19:42.29 | pabelanger | unless elguero is using it |
| 19:42.57 | kpfleming | no, it would not require a patch, it would require writing a module that listens for security events and generates manager events. no existing code would need to be touched. |
| 19:43.47 | ggtest | when I read https://wiki.asterisk.org/wiki/display/AST/SIP+Security+Events, they talk about sample configuration file that can filter and react with iptables |
| 19:44.08 | kpfleming | that is an idea for something that could exist, it is not included with asterisk. |
| 19:44.12 | ggtest | it's why I'm trying to find how to achieve that |
| 19:44.19 | ggtest | ok ok |
| 19:45.24 | elguero | I just use it to do the standard logging of security events... events that are generated by AMI and chan_sip are logged to the security log file |
| 19:45.29 | kpfleming | and it wouldn't be a config file... it would be some code listening to security events and deciding how to react to them. that code could have its own config file, but the code would not need to (or benefit from) living in asterisk. |
| 19:46.04 | ggtest | perfect |
| 19:46.09 | kpfleming | for example, it would be straightforward to listen to security events and forward notifications to fail2ban, so that it didn't have to scan and parse log files. |
| 19:46.45 | ggtest | right ! |
| 19:46.49 | elguero | ggtest: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Security+Framework will give you an idea on how to use the framework |
| 19:47.28 | ggtest | so asterisk 10 can detect and log dos attack ? |
| 19:47.34 | kpfleming | no |
| 19:47.40 | ggtest | :( |
| 19:47.52 | kpfleming | it can report fine-grained events that occur. determining whether those events constiture a DoS or not is up to you. |
| 19:48.11 | kpfleming | s/constiture/constitute/ |
| 19:49.02 | Corydon76-home | Basically, you're going to have to write an external piece. Asterisk isn't going to do that part for you. |
| 19:49.12 | ggtest | but it logs something with the source IP address |
| 19:49.45 | Corydon76-home | Uh, well, kind of |
| 19:49.58 | kpfleming | please read the wiki pages... they describe all of this in great detail |
| 19:50.01 | ggtest | because with asterisk 1.4, fail2ban can't block anything |
| 19:50.27 | kpfleming | sure it can, people have been using it with asterisk 1.4 for quite a while. |
| 19:50.34 | kpfleming | it's not ideal, but it can be done. |
| 19:50.34 | Corydon76-home | This is all UDP, so with an intentional DoS attack, the source IPs are going to be randomized. |
| 19:51.07 | ggtest | ok |
| 19:51.32 | ggtest | it seems to be impossible to block kind of attack |
| 19:51.45 | Corydon76-home | The security framework won't help with a DoS. |
| 19:51.50 | ggtest | ok |
| 19:52.01 | kpfleming | it is very difficult to block such attacks, yes. such is the nature of UDP. |
| 19:52.04 | Corydon76-home | It might help with a username scan, though |
| 19:53.22 | pabelanger | Plus, isn't blocking a DoS at the far end pointless, since all your bandwidth will be saturated at that point in time. |
| 19:53.29 | Corydon76-home | It's easier to block those types of attacks at your provider's router |
| 19:53.37 | pabelanger | yar |
| 19:53.51 | Corydon76-home | Or at the backbone router, really |
| 19:54.01 | kpfleming | or via cruise missile |
| 19:54.22 | Corydon76-home | only if you know where the command-and-control server is located. |
| 19:55.12 | pabelanger | but then you need to deal with the Brotherhood of Nod |
| 19:56.30 | Corydon76-home | A clean shot to the back of the head is a more permanent solution, though. |
| 19:56.41 | ggtest | :D |
| 19:57.51 | Corydon76-home | Let the word get out that you crushed his skull with an ATM, and nobody will fsck with you. |
| 20:02.45 | *** join/#asterisk-dev malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd) |
| 20:02.45 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
| 21:04.05 | *** join/#asterisk-dev malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd) |
| 21:04.05 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
| 21:04.55 | *** join/#asterisk-dev malcolmd (~malcolmd@pdpc/sponsor/digium/malcolmd) |
| 21:04.55 | *** mode/#asterisk-dev [+o malcolmd] by ChanServ |
| 21:27.12 | *** part/#asterisk-dev bchia (~Adium@nat/digium/x-nkfdzqbtsgtclgdm) |
| 21:53.29 | *** join/#asterisk-dev leifmadsen (~Leif@asterisk/documenteur-extraordinaire/blitzrage) |
| 21:53.29 | *** mode/#asterisk-dev [+o leifmadsen] by ChanServ |
| 22:23.45 | *** part/#asterisk-dev mjordan (~mjordan@nat/digium/x-urrhahtfahbltjwd) |
| 22:41.40 | *** join/#asterisk-dev wudles (~wudles@gateway.secureinstrument.com) |