scapy (1.1.1-2ubuntu1) gutsy; urgency=low
* Merge from Debian unstable. Remaining Ubuntu changes:
- ubuntuinterface.patch to wrap interface call to prevent crash due to
call to uninitialized interface.
Ubuntu unique interface management confounds scapy interface status
dete
scapy (1.1.1-1ubuntu1) gutsy; urgency=low
* Merge from Debian unstable. Remaining Ubuntu changes:
- ubuntuinterface.patch to wrap interface call to prevent crash due to
call to uninitialized interface.
Ubuntu unique interface management confounds scapy interface status
dete
scapy (1.1.1-1ubuntu1) gutsy; urgency=low
* Merge from Debian unstable. Remaining Ubuntu changes:
- ubuntuinterface.patch to wrap interface call to prevent crash due to
call to uninitialized interface.
Ubuntu unique interface management confounds scapy interface status
dete
** Changed in: scapy (Ubuntu)
Status: Fix Committed => Fix Released
--
[feisty] scapy crashes using any version of python
https://bugs.launchpad.net/bugs/96753
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
For Gutsy.
** Changed in: scapy (Ubuntu)
Status: Confirmed => Fix Committed
--
[feisty] scapy crashes using any version of python
https://bugs.launchpad.net/bugs/96753
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
FTBFS was due to hard coding Python 2.4 paths in the new Debian scapy
package. This fix is included with the proposed fix to Bug #111221 for
Gutsy.
--
[feisty] scapy crashes using any version of python
https://bugs.launchpad.net/bugs/96753
You received this bug notification because you are a mem
Note that the patch currently FTBFS in the Feisty pbuilder that I have.
Also, the scapy package what substantially reworked in Debian after
Feisty was frozen, so the packaging of this patch would not work at all
with the Feisty scapy version.
--
[feisty] scapy crashes using any version of python
Patch for Gutsy. Added patch system to make this more maintainable,
since it's likely Ubuntu unique.
** Attachment added: "Patch to catch incorrect interface status"
http://librarian.launchpad.net/7446002/scapy_crash.debdiff
--
[feisty] scapy crashes using any version of python
https://bugs.
Attempted to reproduce this in Debian Testing and was unsuccessful. It
looks like this is triggered by the way networks are managed in Ubuntu
and not necessarily in other distros.
--
[feisty] scapy crashes using any version of python
https://bugs.launchpad.net/bugs/96753
You received this bug no
I tried your suggestion and that works (as in doesn't crash). I also
discovered a simple workaround (at least if the unused interface is
dhcp). I tried
$ sudo /etc/init.d/networking restart
after dhcp failed to find any leases and went to sleep, no more crash.
I'd be curious if the same works f
I've suggested a fix/workaround on the upstream bug tracker,
http://trac.secdev.org/scapy/ticket/40
In the meantime, there's probably enough information in this bug report to get
people around the problem.
--
[feisty] scapy crashes using any version of python
https://bugs.launchpad.net/bugs/967
For me, on the machine I'm testing this on, I have a wired interface
defined in /etc/network/interfaces and a wireless interface controlled
by networkmanager. When the only active interface is the one defined in
/etc/network/interfaces, then scapy works fine. If there is no active
interface or if
Based on the discussion here and the dupe, I'm reopening this and I'll
take a look at it.
** Changed in: scapy (Ubuntu)
Importance: Undecided => Medium
Assignee: Dan O'Huiginn => Scott Kitterman
Status: Rejected => Confirmed
--
[feisty] scapy crashes using any version of python
ht
My scapy (1.0.4-1) cannot be invoked from the command line without crashing :-
$ scapy -h
/usr/bin/scapy:3101: Warning: 'with' will become a reserved keyword in Python
2.6
/usr/bin/scapy:3103: Warning: 'with' will become a reserved keyword in Python
2.6
INFO: Can't import PyX. Won't be able to us
/etc/ethertypes (provided by ebtables) is not relevant to this; fixing
that message doesn't fix the fault.
The problem appears to trigger for unconfigured interfaces; I have an
eth0 that is not configured at boot time (no cable plugged in to the UTP
socket), and 'scapy -h' (which should print out
Please merge/reference to #106768.
Same problem here:
# uname -a
Linux laila 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Lin
# python --version
Python 2.5.1c1
# scapy -s test
/usr/bin/scapy:3101: Warning: 'with' will become a reserved keyword in Python
2.6
/usr/bin/scapy:3103
Huh maybe a recent update fixed this because it now starts fine here as
well. Thanks for going over the bug.
** Changed in: scapy (Ubuntu)
Status: Needs Info => Rejected
--
[feisty] scapy crashes using any version of python
https://launchpad.net/bugs/96753
--
ubuntu-bugs mailing list
ub
Thanks for your report. What exactly do you do to make scapy crash in
this way? Just starting it from the command-line seems to work OK for
me.
** Changed in: scapy (Ubuntu)
Assignee: (unassigned) => Dan O'Huiginn
Status: Unconfirmed => Needs Info
--
[feisty] scapy crashes using any
18 matches
Mail list logo