So, I'm going to upload a new package (python-dsniff) and maintain (or
co-maintain, with faidon) dsniff (the classical one) in the meantime.
Personally, I'm going to leave the dsniff maintenance when python-dsniff
becomes a comparable alternative.
Thanks for all your opinions,
luciano
--
T
Luciano Bello wrote:
> I'm the dsniff[1] maintainer, which is a pretty dead project[2]. Dug
> Song (the upstream) is putting his efforts in rewrite the project in
> python[3], which is quite limited compared to the previous one.
> The question is: should I package this new version as a
Citando Carlos Galisteo :
On Tue, Mar 9, 2010 at 5:01 PM, Luciano Bello wrote:
The question is: should I package this new version as a replacement
of the previous one, even one there is a big reduction in the feature
list? Or, should I create a new package (let's say, python-dsniff) and
On Tue, Mar 9, 2010 at 5:01 PM, Luciano Bello wrote:
> The question is: should I package this new version as a replacement
> of the previous one, even one there is a big reduction in the feature
> list? Or, should I create a new package (let's say, python-dsniff) and
> RM dsniff?
As an o
Please, CC me (my usual account is off-line momentarily)
Hi all,
I'm the dsniff[1] maintainer, which is a pretty dead project[2]. Dug
Song (the upstream) is putting his efforts in rewrite the project in
python[3], which is quite limited compared to the previous one.
The question is
5 matches
Mail list logo
