Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

comment-in-comment not supportedFirst TLV is MtaConfigDelimiter, forcing PacketCable MTA file #58

Open
p-alik opened this issue Feb 19, 2018 · 0 comments

Comments

@p-alik
Copy link

p-alik commented Feb 19, 2018

Usually docsis breaks encoding if config file is malformed. According to our resent experience there may be at least one exception.

We got an issue by encoding MTA config file with nested/malformed comments. docsis encrypted our malformed foo.txt with only a complain:
line 6: comment-in-comment not supportedFirst TLV is MtaConfigDelimiter, forcing PacketCable MTA file..

I'm not entirely sure if it's a bug or expected behavior and therefor report it you know.
Below some information could help you to reproduce the issue.
Tested with 6b23fd2

  • foo.txt MTA configuration file
Main
{
  MtaConfigDelimiter 1;

  SnmpMibObject .1.3.6.1.6.3.18.1.1.1.2.1 String "foo12@";    /* malformed comment /
  SnmpMibObject .1.3.6.1.6.3.18.1.1.1.8.1 Integer 4;               /* well-formed comment */

  MtaConfigDelimiter 255;
}
  • encrypt command
    $ ./src/docsis -e foo.txt examples/keyfile foo.cfg

  • decrypt
    $ ./src/docsis -d foo.cfg examples/keyfile

Main 
{
        MtaConfigDelimiter 1;
        SnmpMibObject iso.3.6.1.6.3.18.1.1.1.2.1 String "foo12@";
        MtaConfigDelimiter 255;
}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant