Greetings,
>> I talked with Francesco about it:
>>
>> umit.pm.bt_sniffer -> Bluetooth Sniffer
>>
>> umit.pm.bt_sniffer.core
>> umit.pm.bt_sniffer.gui
>>
>> It is not necessary. Just need to have umit.pm.backend.bt_sniffer.
>>
>> By the way the sniffer have a dependence of a dongle, so Francesco
suggest add it as a plugin.
>>
>> Let me know what you think about that.
>
> I'm not sure yet on what would be best. I think that perhaps, if we keep
it as a plugin, then PM will evolve in a different pace when compared to BT
Sniffing. If it happens that we don't keep both things always updated we'll
end up with BT Sniffer broken someday. What about having it as an option
during installation, and them, if there is no dongle when user tries to use
it, we raise a message? Also, I think that certainly in the future, we could
also write plugins for BT Sniffer, and if we do so with it being a plugin,
it would be a bit paradoxal. What are your opinions from this perspective?
I am advocating the current structure of umit.pm.bt_sniffer.core and
umit.pm.bt_sniffer.gui. As we know PM's main components are divided into
modules and I believe Bluetooth Sniffer should integrate at that level.
Adriano has addressed the most critical point of why Bluetooth Sniffer
should not be a mere plugin. I would also agree on the point where Bluetooth
Sniffer is an option during installation because the software requires a
specific dongle. Another major organizational strategy concern was adressed
about the posibility of having plugins specific to Bluetooth Sniffer and I
would like to add to that. Bluetooth Sniffer has commercialization potential
and expansionary growth potential. Shu has already worked on the very first
plugin for Bluetooth Sniffer which would automatically capture the LMP
packets from Bluetooth Sniffer and perform a PIN crack on the fly. I believe
I do not have to elaborate how awesome this plugin is. We have also obtained
the source file of the compiler used to develop the firmware. In time we are
looking at reverse engineering components of the firmware to optimize the
performance of Bluetooth Sniffer right from the firmware. This would be a
major effort post GSoC which depends on the success of the initial Bluetooth
Sniffer tool where the commercialization efforts would follow through.
I believe it is great that we have two great software under one hood and I
sincerely appericiate the work Francesco has put into Packet Manipulator. I
would like to see an integrated tool both functionally and visually as it
would advance not only our projects but Umit as a whole.
Cheers,
Devtar
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Umit-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/umit-devel
