(AntiDialer is a GNU/Linux broadband dialer for Sify broadband users)
Hi,
I have released AntiDialer v0.1 into the wild today. The main feature of this release is that it is no longer just a GUI dialer. It is now a console based dialer with a GUI plugin. Here are the details:
AntiDialer version 0.1 is out today. Get it here:
https://sourceforge.net/project/showfiles.php?group_id=157014&package_id...
This version has been released in three forms:
0) source tarball 1) debian package 2) rpm package (auto-created from the deb package with alien)
New Features: ------------------
0. Complete rewrite of the core to remove all dependence on QT libraries. QT dependency is only for the UI plugin now. 1. Console based interface for the shell junkies 2. Plugin interface to allow new feature implementation in the form of separate plugin libraries 3. A GUI plugin based on QT 4. Ability to provide username/password at console. You may write the command with username and password into an rc.d file and it will autoconnect on startup.
Features removed: --------------------------
0. Heartbeat: This feature is useless unless you want a tray icon alive all the time. A tray icon can be implemented as a plugin. The old heartbeat code is still there in the tarball if anyone's interested.
Regards, Siddhesh
Hi Siddhesh,
How is the sify dialer different from other dialers. Does it use some unconventional protocols.
Steven
On Wednesday 07 June 2006 04:30, Siddhesh Poyarekar wrote:
(AntiDialer is a GNU/Linux broadband dialer for Sify broadband users)
Hi,
I have released AntiDialer v0.1 into the wild today. The main feature of this release is that it is no longer just a GUI dialer. It is now a console based dialer with a GUI plugin. Here are the details:
AntiDialer version 0.1 is out today. Get it here:
https://sourceforge.net/project/showfiles.php?group_id=157014&package_id... 5411&release_id=422809
This version has been released in three forms:
- source tarball
- debian package
- rpm package (auto-created from the deb package with alien)
New Features:
- Complete rewrite of the core to remove all dependence on QT
libraries. QT dependency is only for the UI plugin now.
- Console based interface for the shell junkies
- Plugin interface to allow new feature implementation in the form of
separate plugin libraries 3. A GUI plugin based on QT 4. Ability to provide username/password at console. You may write the command with username and password into an rc.d file and it will autoconnect on startup.
Features removed:
- Heartbeat: This feature is useless unless you want a tray icon
alive all the time. A tray icon can be implemented as a plugin. The old heartbeat code is still there in the tarball if anyone's interested.
Regards, Siddhesh
On 6/15/06, Steven Joseph stevenjose@gmail.com wrote:
How is the sify dialer different from other dialers. Does it use some unconventional protocols.
Well Sify has conjured up its own protocol for its dialer. They have not released documentation for it but Pratap P V reverse-engineered their linux dialer and put up a small article with protocol details. Here's the article if you want to know the specifics:
http://www.indiasec.com/papers/pratap/sify.html
Siddhesh
On Thursday 15 June 2006 10:38, Siddhesh Poyarekar wrote:
On 6/15/06, Steven Joseph stevenjose@gmail.com wrote:
How is the sify dialer different from other dialers. Does it use some unconventional protocols.
Well Sify has conjured up its own protocol for its dialer. They have not released documentation for it but Pratap P V reverse-engineered their linux dialer and put up a small article with protocol details. Here's the article if you want to know the specifics:
Why are they reinventing the wheel ... is there any advantage of doing this. ?
On 6/17/06, Steven Joseph stevenjose@gmail.com wrote:
Why are they reinventing the wheel ... is there any advantage of doing this. ?
Hehe... none that I can imagine. Infact they're wasting resources on developers to develop dialers and protocols. They could just have used the cyberoam client and protocol. But I guess Sify simply loves doing things the hard way ;-)
They have a few other uses for their dialer protocol on the windows environment like antivirus installation, version detection, etc. Also, their protocol is extensible in the sense that it uses XML strings to send parameters instead of delimited strings. That's why they're able to easily support two different types of protocols (there's a version 3 protocol as well which includes some cryptography just to dissuade independently released dialers for windows. They probably are too lazy to modify their linux dialer for that protocol).
Siddhesh
On 17/06/06 18:12 +0530, Siddhesh Poyarekar wrote:
On 6/17/06, Steven Joseph stevenjose@gmail.com wrote:
Why are they reinventing the wheel ... is there any advantage of doing this. ?
Hehe... none that I can imagine. Infact they're wasting resources on developers to develop dialers and protocols. They could just have used the cyberoam client and protocol. But I guess Sify simply loves doing things the hard way ;-)
As opposed to, oh port based authentication via 802.1x, or PPPoE? Why would you replace one propietary protocol with another when you could go with industry standard protocols?
Devdas Bhagat
On Saturday 17 June 2006 12:42, Siddhesh Poyarekar wrote:
Hehe... none that I can imagine. Infact they're wasting resources on developers to develop dialers and protocols. They could just have used the cyberoam client and protocol. But I guess Sify simply loves doing things the hard way ;-)
*snip*
No...its a perfectly formulated strategy. Cyberoam client is quite decent as compared to sify client. The sify client gives the ISP ( sify ) a lot of control over the user's activities eg. they can modify *your* firewall rules remotely by instructing their client. I think BBImpSec is the module which does that. There are several other "features" which resemble that of a RAT than a simple authentication client ;).
-
Devdas Bhagat -
Dinesh Joshi -
Siddhesh Poyarekar -
Steven Joseph