Bug 1111788 - Error when using "sendp" with DNS package (no split attribute, but seems to work with the fix i made)
Summary: Error when using "sendp" with DNS package (no split attribute, but seems to w...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: scapy
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Devan Goodwin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-21 13:15 UTC by Jp1337
Modified: 2015-06-29 21:15 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 21:15:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
how i managed to make it seem to work (11.82 KB, image/png)
2014-06-21 13:15 UTC, Jp1337
no flags Details

Description Jp1337 2014-06-21 13:15:52 UTC
Created attachment 911008 [details]
how i managed to make it seem to work

Description of problem:

Attempt to use function sendp(package, iface) of scapy, results in following error in console:

(huge chunck of stuff)
...
  File "/usr/lib/python2.7/site-packages/scapy/layers/dns.py", line 28, in i2m
    x = [k[:63] for k in x.split(".")] # Truncate chunks that cannot be encoded (more than 63 bytes..)
AttributeError: 'builtin_function_or_method' object has no attribute 'split'


Version-Release number of selected component (if applicable):

scapy-noarch 2.2.0-3.fc20

How reproducible:

attempt to use the sendp function.

Steps to Reproduce:

1. make a package (mine had a DNS field, DNQR and DNRR).
2. select interface.
3. execute.

Apparently it happens when encoding a domain name.

Actual results:

The named error.

Expected results:

Awesomely sent package and an angry DNS poisoned victim.

Additional info:

Despite not knowing python I mannaged to make a temporary workaround by editting the file indicated in the bug.
I attach a screenshot.

Ps: Pardon my poor english.

Comment 1 Jp1337 2014-06-22 18:21:58 UTC
Ps2: It doesn't work, it runs, but doesn't work :(

Comment 2 Fedora End Of Life 2015-05-29 12:10:51 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-06-29 21:15:00 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.