<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
dears Andrew & James:<BR>
<BR>
i agree at all... <BR>
weak password, just can become stronger when were replaced with other storng !<BR>
this is absolutly truth! and can't be discussed in any way, and ever we must use strongest pass that can. <BR>
<BR>
then, also is truth that any security on transport layer don't become pass stronger, but gives less chances for sniffing an public sytes/hsotpost/ wifi, also does not enforce against the attack basesdit on test users/passswords, just only can treat this with an IDS systems blocking the src that try to register , because of it , must be searched on any logs file , like fail2ban do or like could someone do by him self, this defines a scenario with an open network and some "IDS strategy" <BR>
<BR>
i think that the security is the result that you get when add resoruces + procedures, <BR>
ie there is no system that protect from "pishing " if you will answer with your user and pass, at any questions that you have received. or if your usr/pass o certiciates was stollen . <BR>
in each proyject must there be a little from all Authentication, Validation,encryption, auditoring, over all if you think ,like i do: <BR>
<BR>
" it's so cheaper a betrayal than a hacking".... , but this talk its about tech...<BR>
<BR>
The idea that send ealier , try to follow this concept: close the network and open just to a konwn bunch with no fixed ip avoiding conections from unknown ips :<BR>
<BR>
keep track on the ipchanges with this change "linked" to a user on easy to use way , with a few steps, it nos os robust like toher but is MUCH better than nothing. so we can reduce the src from the attack going down from "all network" to "not so many places" , from the firewall in the asterisk box and on the asterisk himself.. <BR>
<BR>
..... so it means there will be less chances for the attack, becuase must come from the ip resgitred for user or inside the time slot until renew the ip that has changed . <BR>
<BR>
ie a wifi zone , internet caffe, hotel, hacking wifi routers,... then the user and the atack both behind the same router or share the same public ip.<BR>
<BR>
Off course that theres are other way to do so, more exhaustive , close the access at policy and use any radius/ ppp ... etc authenticate service , also linked to a sql, keep track the ip/users changes ( to enables access and for audit too), and then dynamically refresh peers in PBX or tables for firewall , or both , to allow access or calls ,<BR>
<BR>
What a pleasure , write with people so kind and that have such acknowledgments.<BR>
<BR>
Thanks<BR>
<BR>
marcos<BR>
<BR> <BR>> From: asterisk-biz-request@lists.digium.com<BR>> Subject: asterisk-biz Digest, Vol 71, Issue 44<BR>> To: asterisk-biz@lists.digium.com<BR>> Date: Mon, 28 Jun 2010 00:23:17 -0500<BR>> <BR>> Send asterisk-biz mailing list submissions to<BR>> asterisk-biz@lists.digium.com<BR>> <BR>> To subscribe or unsubscribe via the World Wide Web, visit<BR>> http://lists.digium.com/mailman/listinfo/asterisk-biz<BR>> or, via email, send a message with subject or body 'help' to<BR>> asterisk-biz-request@lists.digium.com<BR>> <BR>> You can reach the person managing the list at<BR>> asterisk-biz-owner@lists.digium.com<BR>> <BR>> When replying, please edit your Subject line so it is more specific<BR>> than "Re: Contents of asterisk-biz digest..."<BR>> <BR>> <BR>> Today's Topics:<BR>> <BR>> 1. Re: 87.230.80.186 (James Sharp)<BR>> 2. Re: 87.230.80.186 (Bret McDanel)<BR>> 3. Re: 87.230.80.186 (Calleasy BsAS)<BR>> 4. Re: 87.230.80.186 (Calleasy BsAS)<BR>> <BR>> <BR>> ----------------------------------------------------------------------<BR>> <BR>> Message: 1<BR>> Date: Sun, 27 Jun 2010 15:53:25 -0400<BR>> From: James Sharp <jsharp@psychoses.org><BR>> Subject: Re: [asterisk-biz] 87.230.80.186<BR>> To: Commercial and Business-Oriented Asterisk Discussion<BR>> <asterisk-biz@lists.digium.com><BR>> Message-ID: <4C27AC35.7070303@psychoses.org><BR>> Content-Type: text/plain; charset=UTF-8<BR>> <BR>> Andrew Latham wrote:<BR>> > SIP TLS or a nice SNOM phone with VPN will do the trick...<BR>> <BR>> No it won't. Transport layer encryption won't solve the problem of<BR>> brute forcing weak passwords, which is what I believe this whole<BR>> discussion started with.<BR>> <BR>> The SNOM phone is a little stronger, but only through<BR>> security-through-obscurity of having to crack the VPN, then knowing how<BR>> to configure your SIP client to talk through the VPN. Still, not<BR>> entirely secure.<BR>> <BR>> Of course, the only completely secure system is the one that doesn't<BR>> exist. The only winning move is not to play.<BR>> <BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 2<BR>> Date: Sun, 27 Jun 2010 13:15:55 -0700<BR>> From: Bret McDanel <trixter@0xdecafbad.com><BR>> Subject: Re: [asterisk-biz] 87.230.80.186<BR>> To: Commercial and Business-Oriented Asterisk Discussion<BR>> <asterisk-biz@lists.digium.com><BR>> Message-ID: <1277669755.3012.828.camel@trixeee.0xdecafbad.com><BR>> Content-Type: text/plain; charset="UTF-8"<BR>> <BR>> On Sun, 2010-06-27 at 15:53 -0400, James Sharp wrote:<BR>> > Andrew Latham wrote:<BR>> > > SIP TLS or a nice SNOM phone with VPN will do the trick...<BR>> > <BR>> > No it won't. Transport layer encryption won't solve the problem of<BR>> > brute forcing weak passwords, which is what I believe this whole<BR>> > discussion started with.<BR>> > <BR>> > The SNOM phone is a little stronger, but only through<BR>> > security-through-obscurity of having to crack the VPN, then knowing how<BR>> > to configure your SIP client to talk through the VPN. Still, not<BR>> > entirely secure.<BR>> > <BR>> <BR>> I thought that TLS was documented, after all products like<BR>> freeswitch.org support it, and the snom phones. If that is the case its<BR>> not security by obscurity.<BR>> <BR>> TLS as I understand it can be configured to use certificates for<BR>> authentication, which means that you would have to either break the<BR>> ciphers used for the certificate or steal the certificate itself.<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 3<BR>> Date: Sun, 27 Jun 2010 22:54:58 -0300<BR>> From: Calleasy BsAS <sisint2005@hotmail.com><BR>> Subject: Re: [asterisk-biz] 87.230.80.186<BR>> To: <asterisk-biz@lists.digium.com>, Calleasy <sisint2005@hotmail.com><BR>> Message-ID: <BAY147-w32FDDC9728FE07BF6B1ADD2CA0@phx.gbl><BR>> Content-Type: text/plain; charset="iso-8859-1"<BR>> <BR>> <BR>> Dear friends, like someone said before me in the list : neither of both extrems could be pretty good!!<BR>> <BR>> one for dangerous the other for heavy dutty requeirements in maintenance for users changes...<BR>> <BR>> <BR>> <BR>> thus leave the system open with out Firewall+ IDS system this will be dangerous <BR>> <BR>> , or closing the firewall at all , if you needs to lead with users that will be travelling or changing from ip address , and need to use the same account from any IP, from anywhere.. then the users will be angry any timne that they can't make a call.<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> So i think we must workaround the needs and search the mix that better serves to our purproses. many times the solution may seems something "out of good arts rules" or , but if it works with efficciency, and it is non expensive... then " ARE WELLCOME"<BR>> <BR>> <BR>> <BR>> VPNs routed end to end with VPN- Routers requeires some hardware that limits the mobile use and requeires more expensive hard, i.e. if i have my sip acocunt configured on my handheld using it with wifi behind a VPN router i can't to use it to make calls in a hotel or airpot or any wifi zones o hotspot, with the exception that this unit can run a vpn client too.<BR>> <BR>> <BR>> <BR>> on other hand, if i have a notebook, laptop or netbook using a softphone with TLS may be usefull, but a bunch of IP telephones, sofphones and gateway not support TLS , or many protocols , then it will depend on the user ....<BR>> <BR>> <BR>> <BR>> On my mind asking to my self, " some advice to follow?? " and the answer could be <BR>> <BR>> <BR>> <BR>> try using services that enable me to locate users from domains and at the same time define yours accoutns using it ... it may requieres aditional efforts to use them, but setting up the peers using host with DNS resolution , avoiding the resgiter use from users,may help <BR>> <BR>> <BR>> <BR>> host= my.domain<BR>> <BR>> <BR>> <BR>> What will be happen if the ip changes or the user hasn't your own domain??? askme again , and asnwer me:<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> try this DDNS service like this :<BR>> <BR>> <BR>> <BR>> host=my.domain.in.prefer.ddns.service.<BR>> <BR>> <BR>> <BR>> may be helpull , any servers from popular ones, ( dyndns, no-ip, ...)<BR>> <BR>> it will requiere that the user can run at same time a DDNS client ( many router/ATAs/Gateways have embeded on them) and a softphone/SIP Client from same ip address,<BR>> <BR>> and the other end , on the PBX , also need reload the sip module each time that the ip changes , to reload the news ip from those domains, this must be so often like the client's ip changes...<BR>> <BR>> <BR>> <BR>> WHAT A CHEAP SOLUTION !!! <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> this task for reload , could be MADE at fixed period of time , ie the same value that you usually speficiy in the expire options for registering , thus the "GAP " between the old ip and the new, has the same behavior if you customer changes th ip addres with out re-registering, ie an user using DHCP in you internet conection , that changes your ip adders and not restart your softphone or gateway., i means : the the incoming calls goes to old ip , until the client re-register orput an outgoing call.<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> in the same way , for the inbound connections to the servers ( a PBX or any other server too) ,some similar can be made with iptables modules , it's quite simple, former set the policy to DENNY all connections and then enables just according ddns domains that you will accept ..<BR>> <BR>> <BR>> <BR>> iptables -P INPUT DROP<BR>> <BR>> iptables -I INPUT -s my.first.client,inddns.service -j ACCEPT<BR>> <BR>> iptables -I INPUT -s my.fsecond.client,in-other-ddns.service -j ACCEPT<BR>> <BR>> <BR>> <BR>> ( some specfication for ports and protocols may be added, i dont include in the example to make it easier )<BR>> <BR>> <BR>> <BR>> after made this, only the ip according to domains can connnect to server , <BR>> <BR>> but at any time that the ips may change, you need to restart iptables services ,and the input filter will be refilled with the ips according that domains defined on DDNS service ....<BR>> <BR>> <BR>> <BR>> to restart this at regular frecuencies in "automatic mode", just need to enable this task in CRON service, also can be joined with the sip module reload to update the host definition in the peer/users/friend in the PBX , for that must need include any script that has this two lines for system excution <BR>> <BR>> <BR>> <BR>> sevrice iptables restart ( restarting iptables fedora /centos style other use init.rc services)<BR>> <BR>> asterisk -rx sip reload ( relaod the sip modules , renewing the domain definitios for peers , be carefull that your PBX systems must resolve using DNS service )<BR>> <BR>> <BR>> <BR>> and... that's all <BR>> <BR>> <BR>> <BR>> now can renew the ip that can connect with the server and also the host defined to make calls <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> easy efecctive and cheap, may be other solution betters ,, yeap....so more expensive too<BR>> <BR>> <BR>> <BR>> Feel free to contact off the list.<BR>> <BR>> I hope that it can be helpfull.<BR>> <BR>> <BR>> <BR>> Marcos<BR>> <BR>> info@calleasy.com.ar<BR>> <BR>> <BR>> <BR>> _________________________________________________________________<BR>> Ahora Hotmail es un 70% m?s r?pido. Para que chequear correos sea cada vez m?s f?cil. Ver m?s<BR>> http://www.descubrehotmail.com/velocidad.asp <BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: http://lists.digium.com/pipermail/asterisk-biz/attachments/20100627/be28aea1/attachment-0001.htm <BR>> <BR>> ------------------------------<BR>> <BR>> Message: 4<BR>> Date: Mon, 28 Jun 2010 02:23:09 -0300<BR>> From: Calleasy BsAS <sisint2005@hotmail.com><BR>> Subject: Re: [asterisk-biz] 87.230.80.186<BR>> To: <brett@voicefoxtelephony.com>, <asterisk-biz@lists.digium.com><BR>> Cc: Calleasy <sisint2005@hotmail.com><BR>> Message-ID: <BAY147-w657111DB9FBE4C91BC3D4BD2CA0@phx.gbl><BR>> Content-Type: text/plain; charset="iso-8859-1"<BR>> <BR>> <BR>> Dear Brett<BR>> <BR>> <BR>> <BR>> Many thanks for your comment.<BR>> <BR>> <BR>> <BR>> any method that reads logs to detect a failrude auth , may be suitable , fail2ban make this <BR>> <BR>> or just reading files from logs directory ( register and messages files ). to know if were any intents refused and then block the src ip..<BR>> <BR>> <BR>> <BR>> with any script that works on this could be found the ip from where come the intents. <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> cat \etc\asterisk\messages | grep Reg | grep @my.domian <BR>> <BR>> <BR>> <BR>> or <BR>> <BR>> <BR>> <BR>> cat \etc\asterisk\messages | grep Reg | grep my.ip.add.res<BR>> <BR>> <BR>> <BR>> processing it could be add the iip to the iptables ruiles for block...<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> in this process, like ever , former we must chose the path to follow , from two possibles to implement .<BR>> <BR>> <BR>> <BR>> 1) closed netowroks , denny all , enables some host to connect. simple, not flexible, not suitbale continuous changing networks, <BR>> <BR>> <BR>> <BR>> 2) open networks, accept all , we must detect intrussion+ attacks and denny all ip for any attack detected o not trusted .. need much intelligence, resources and efforts to identify and blocks anything that seem dangerous <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> this breif comment was aimed to help some guys that were tryiing to get works some iptables conf to avoid undesired conections.<BR>> <BR>> <BR>> <BR>> in short:<BR>> <BR>> <BR>> <BR>> YES...publics DDNS, have some delay to progress in refresh cache. there is no doubt about that.<BR>> <BR>> <BR>> <BR>> <BR>> <BR>> >From my own expeirencie I have dns server from own from fixed ip, but some PBXs from some customers are pointed trough ddns servers to my switch , using no-ip, and they are conected by cable modem with dhcp . when ip changes take a few minutes , yes , its a quite slow. but it's so SIMPLE, SO CHEAP and not requiere advanced acknowledgements, i think that is a suitable way to connect a some sip users that haven't a fixed ip , but this has some delay to update changes. it wiil be shure <BR>> <BR>> <BR>> <BR>> Better solution more efective and fast , could be make a kind of simple DDNS service running on your ouwn server, with any TCP client just need to open any TCP conection to your server reporting user and pass and then catching the source ip , ... it willbe automated version so fast , and reliable , but need more expertise like programming, beyond from them were asking about basic option form iptbales to avoid calls from undesired ips .<BR>> <BR>> <BR>> <BR>> Without go so for, ALSO CAN USE A FORM IN A HTTPS SERVER CONNECTION for something like loggin , THAT WILL START THE SCRIPT FOR RENEWING after send the form, the action started by the CGI just must include the same , the action for reload modules after renews ips <BR>> <BR>> <BR>> <BR>> yes, its no automatic , but really works too. fast and enable to get a cheap way to get closer TO a "closed network" , but in open ambient, because any user authenticate using in secure tuinnel tosend the usr and pss and with that update te ip for peer , but it will requiere user action , <BR>> <BR>> <BR>> <BR>> like i said earlier <BR>> <BR>> All this is a mix, branded with less expensive options for bring up something to get better.. <BR>> <BR>> <BR>> <BR>> Marcos<BR>> <BR>> Thanks again <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> > From: brett@voicefoxtelephony.com<BR>> > To: brett@voicefoxtelephony.com<BR>> > Subject: Re: [asterisk-biz] 87.230.80.186<BR>> > Date: Sun, 27 Jun 2010 21:15:02 -0500<BR>> > CC: asterisk-biz@lists.digium.com; asterisk-biz@lists.digium.com; sisint2005@hotmail.com<BR>> > <BR>> > Yow,<BR>> > Sorry list for the trigger happy reply...<BR>> > <BR>> > What I was saying is that it's an interesting idea but I think DNS <BR>> > caching will make it not really feasible.<BR>> > <BR>> > For me fail2ban + good passwords works as a really good system where a <BR>> > VPN can't be used.<BR>> > <BR>> > <BR>> > -Brett<BR>> > <BR>> > On Jun 27, 2010, at 9:10 PM, Brett Nemeroff <BR>> > <brett@voicefoxtelephony.com> wrote:<BR>> > <BR>> > > Interesting idea, but I think DBS caching will make this not really <BR>> > > usable.<BR>> > ><BR>> > ><BR>> > > For me, fail2<BR>> > ><BR>> > ><BR>> > ><BR>> > > On Jun 27, 2010, at 8:54 PM, Calleasy BsAS <sisint2005@hotmail.com> <BR>> > > wrote:<BR>> > ><BR>> > >><BR>> <BR>> _________________________________________________________________<BR>> Ahora Hotmail es un 70% m?s r?pido. Para que chequear correos sea cada vez m?s f?cil. Ver m?s<BR>> http://www.descubrehotmail.com/velocidad.asp <BR>> -------------- next part --------------<BR>> An HTML attachment was scrubbed...<BR>> URL: http://lists.digium.com/pipermail/asterisk-biz/attachments/20100628/9423d852/attachment.htm <BR>> <BR>> ------------------------------<BR>> <BR>> _______________________________________________<BR>> --Bandwidth and Colocation Provided by http://www.api-digital.com--<BR>> <BR>> asterisk-biz mailing list<BR>> To UNSUBSCRIBE or update options visit:<BR>> http://lists.digium.com/mailman/listinfo/asterisk-biz<BR>> <BR>> End of asterisk-biz Digest, Vol 71, Issue 44<BR>> ********************************************<BR> <br /><hr />Ahora Hotmail es un 70% más veloz. Acceder a tu casilla nunca fue tan rápido. <a href='http://www.descubrehotmail.com/velocidad.asp ' target='_new'>Ver más</a></body>
</html>