You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(5) |
Feb
(1) |
Mar
(7) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(6) |
Nov
(4) |
Dec
|
2003 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
(5) |
May
(5) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
(1) |
Oct
(3) |
Nov
(2) |
Dec
|
2004 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2005 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(6) |
Aug
(2) |
Sep
|
Oct
(3) |
Nov
(13) |
Dec
|
2006 |
Jan
(3) |
Feb
(3) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
(1) |
Oct
(6) |
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
(2) |
Apr
(4) |
May
|
Jun
(3) |
Jul
(6) |
Aug
(2) |
Sep
|
Oct
|
Nov
(3) |
Dec
|
2008 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(9) |
Sep
(5) |
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
(13) |
Jun
(7) |
Jul
(2) |
Aug
(2) |
Sep
(2) |
Oct
(2) |
Nov
(3) |
Dec
(1) |
2010 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
(2) |
Oct
|
Nov
(12) |
Dec
(3) |
2011 |
Jan
|
Feb
|
Mar
(7) |
Apr
|
May
(8) |
Jun
(6) |
Jul
|
Aug
|
Sep
(11) |
Oct
(8) |
Nov
(3) |
Dec
(2) |
2012 |
Jan
(9) |
Feb
(3) |
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(9) |
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
|
Feb
(3) |
Mar
(6) |
Apr
|
May
(8) |
Jun
|
Jul
(5) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
(1) |
Oct
(1) |
Nov
(1) |
Dec
(2) |
2018 |
Jan
|
Feb
(3) |
Mar
(4) |
Apr
|
May
|
Jun
(2) |
Jul
(5) |
Aug
|
Sep
(4) |
Oct
(2) |
Nov
(1) |
Dec
(2) |
2019 |
Jan
(2) |
Feb
(4) |
Mar
(4) |
Apr
|
May
(8) |
Jun
(3) |
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(1) |
Nov
|
Dec
(2) |
2020 |
Jan
(4) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(6) |
Jun
(3) |
Jul
(2) |
Aug
(1) |
Sep
(3) |
Oct
|
Nov
(3) |
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Ray L <gob...@gm...> - 2018-06-24 10:01:22
|
need info please |
From: <279...@qq...> - 2018-03-27 10:48:40
|
那它们就会占据我们的整个视线范围。一旦我们与这些东西拉 |
From: <279...@qq...> - 2018-03-27 10:28:03
|
于预见和恐惧的原因而增加了十倍之多。 |
From: <279...@qq...> - 2018-03-12 12:43:05
|
欲转过头来拒绝了生命——这是悲剧中回荡的一种直接的或 |
From: Kroger.com <ca...@kr...> - 2018-02-28 06:24:29
|
Shop for free in Kroger! <br> We need real people to give us real reviews of their local stores and we'll give you $200 Gift Card to spend. <br> Sign up for free here <a href="http://apelectrical.net/new/"}>link </a> <br> |
Bambanhtuswanro |
Mohon di masukan sya ke rum indonesia |
From: Thomas <th...@ma...> - 2017-11-29 13:27:07
|
Hey, Are you planning to outsource your SEO offshore? You are at the right place by reading this! We are the leading SEO Company in India working with a number of agencies and generating awesome leads for their clients. Here are the highlights of our SEO Reseller Program: 1 No Set up Fees. 2 Free 15 Days trial on any of your 3 projects. 3 Free Site Audit Reports and SEO Proposals for your clients. 4 100% White Labeled Reports with your brand name and logo. 5 Handy Project Management through Basecamp. 6 Creation of a rich backlink profile with backlinks coming from sites with DA, TF>15. 7 Weekly Rankings and Monthly Performance Reports. While we’ll manage everything at our end, you can sit back and enjoy the extra profits! We also offer SMO, PPC, Website Development, Content marketing, Facebook Marketing, LinkedIn Marketing and Brand Reputation Management. If there’s something else you’re challenged with, drop your Skype id or Phone No. and I’ll get back to you instantly. Regards, Thomas, Business Development Executive P.S. This is an advertisement and a promotional mail strictly on the guidelines of CAN-SPAM act of 2003. We have clearly mentioned the source mail-id of this mail, also clearly mentioned the subject lines and they are in no way misleading in any form. We have found your mail address through our own efforts on the web search and not through any illegal way. If you find this mail unsolicited, please reply with "Remove" in the subject line and we will take care that you do not receive any further promotional mail. |
From: Edward A. <ed...@se...> - 2017-10-28 06:09:02
|
Hello dnsjava Team, Hope this email provides you better business opportunity. All major search engines such as Google, Yahoo and Bing have primary search results, where web pages and other content are ranked based on what the search engine considers most relevant to users. Site trust plays a big role here whether it will succeed or fail from a search perspective. Along with it, Social accounts are must to build reputation and brand awareness for all type of online business. A single SEO factor will not guarantee search engine rankings. Insertion of a great HTML title & multiple links won’t help if a page has low quality content. Therefore, introducing several positive factors can increase the odds of success however presence of one negative factor can worsen those odds. There are some techniques that search engines deem “black hat”, which could result your pages receiving a ranking penalty or being banned from the search engines entirely. Considering above factors, as a web owner you should always leave your websites in safe hands to overcome all the huddles which comes on the way while promoting a website. With our alliance we can assure you to get your website visible and maximize online business. If you find this interesting, then please ask for a *no obligation *website analysis report where a detailed insight with deliverable will be mentioned. We will be looking forward to your response. *Edward Allen*Site Analyst /Digital Marketing Tel: USA (813) 708-8643 *Skype*: high.rank ………………………………………………………….. Ps: If you do not want such emails ask us to “REMOVE”. This e-mail is an initiative to let you know about your website performance through our Marketing ID. Once you revert us back, we will start communicating with you from our Corporate ID. [image: beacon] |
From: Doug K. <dou...@li...> - 2017-09-29 23:05:00
|
How do I query a list of ip addresses for a dns pool in end java? Thank you! Doug Get Outlook for Android<https://aka.ms/ghei36> |
From: Senthil K. <sku...@gm...> - 2017-08-13 20:26:40
|
Ingo, Thanks for the info and the links! cheers Kumar On Sun, Aug 13, 2017 at 1:18 PM, Ingo Bauersachs <in...@ji...> wrote: > > dnsjava works perfectly for me when I do a single PTR record lookup. > > However, if I try to do more than 1, it always fails for me (regardless > of > > the DNS server I point to) > > > > Here's the code snippet and the response. Can anyone tell me how I can > get > > this to work? > > Nothing, since this is a DNS limitation and not specific to dnsjava. See > also the answers in [1] or [2]. You'll need to send separate queries. > > > Any insight would be appreciated! -Kumar > > Ingo > > [1] https://lists.isc.org/pipermail/bind-users/2008-August/072383.html > [2] https://stackoverflow.com/questions/4082081 > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > dnsjava-users mailing list > dns...@li... > https://lists.sourceforge.net/lists/listinfo/dnsjava-users > |
From: Ingo B. <in...@ji...> - 2017-08-13 19:47:58
|
> dnsjava works perfectly for me when I do a single PTR record lookup. > However, if I try to do more than 1, it always fails for me (regardless of > the DNS server I point to) > > Here's the code snippet and the response. Can anyone tell me how I can get > this to work? Nothing, since this is a DNS limitation and not specific to dnsjava. See also the answers in [1] or [2]. You'll need to send separate queries. > Any insight would be appreciated! -Kumar Ingo [1] https://lists.isc.org/pipermail/bind-users/2008-August/072383.html [2] https://stackoverflow.com/questions/4082081 |
From: Senthil K. <sku...@gm...> - 2017-08-13 19:00:33
|
Hello, dnsjava works perfectly for me when I do a single PTR record lookup. However, if I try to do more than 1, it always fails for me (regardless of the DNS server I point to) Here's the code snippet and the response. Can anyone tell me how I can get this to work? Any insight would be appreciated! -Kumar -- public static void lookupPTRMultiple() throws IOException { Resolver res = new SimpleResolver("209.244.0.3"); // level 3 dns server res.setTCP(true); res.setTimeout(Integer.MAX_VALUE); Message request = new Message(); Record rec1 = Record.newRecord(ReverseMap.fromAddress("206.190.36.105"), Type.PTR, DClass.IN); request.addRecord(rec1, Section.QUESTION); Record rec2 = Record.newRecord(ReverseMap.fromAddress("199.27.145.64"), Type.PTR, DClass.IN); request.addRecord(rec2, Section.QUESTION); System.err.println("Request: " + request); Message response = res.send(request); System.err.println("Response: " + response); } -- Response: ;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 32188 ;; flags: qr ; qd: 2 an: 0 au: 0 ad: 0 ;; QUESTIONS: ;; 105.36.190.206.in-addr.arpa., type = PTR, class = IN ;; 64.145.27.199.in-addr.arpa., type = PTR, class = IN ;; ANSWERS: ;; AUTHORITY RECORDS: ;; ADDITIONAL RECORDS: ;; Message size: 65 bytes |
From: Brian W. <bwe...@xb...> - 2016-06-22 18:23:15
|
> On Jun 22, 2016, at 7:02 AM, Alastair Donlon <ala...@op...> wrote: > > > It looks like the Lookup class returns a status of Lookup.TRY_AGAIN when > the server responds with a NOTZONE status. I find that a little bit > surprising - I would have expected this response to be seen as some kind > of fatal error. Is there something I'm misunderstanding either about > NOTZONE or the Lookup class? I believe that it’s treating any unexpected rcode as something which could be a transient problem, and definitely shouldn’t cause the Lookup to immediately fail (as the UNRECOVERABLE errors do). Simply treating an unexpected rcode as an unrecoverable error isn’t enough, because a single Lookup will often send multiple queries to each of multiple servers, and getting something like NOTZONE for one of those queries doesn’t necessarily mean total failure at all. It’s possible that there could be some additional code handling the case when all queries get unexpected rcode values, but that’s a pretty special case. Brian |
From: Alastair D. <ala...@op...> - 2016-06-22 14:17:52
|
It looks like the Lookup class returns a status of Lookup.TRY_AGAIN when the server responds with a NOTZONE status. I find that a little bit surprising - I would have expected this response to be seen as some kind of fatal error. Is there something I'm misunderstanding either about NOTZONE or the Lookup class? Cheers, Alastair. |
From: Garth P. <ga...@tw...> - 2014-05-16 21:56:15
|
Is it possible to pipeline several queries over a single, persistent tcp connection? We are using a provider for NAPTR record lookups that is asking us to make requests over a single persistent connection. Is it possible with the library? I can't figure out how you would modify TCPClient to allow it, or how you would identify that a record was associated with a particular query. Any ideas? Thanks, Garth |
From: Jack T. <j.t...@F5...> - 2014-05-09 20:09:24
|
If you want the host name to be treated like an absolute name, you need to provide an absolute name. In other words, terminate your host name with a dot "." So your code should be: Lookup lookup = new Lookup("2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.", > -----Original Message----- > From: Garth Patil [mailto:ga...@tw...] > Sent: Friday, May 09, 2014 11:56 AM > To: dns...@li... > Subject: Appending to absolute name on failure > > I am using the dnsjava library to query a NAPTR record: > > SimpleResolver resolver = new SimpleResolver(X.X.X.X); > resolver.setPort(53); > Lookup lookup = new Lookup("2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net", > Type.NAPTR); > lookup.setResolver(resolver); > Record[] records = lookup.run(); > > When the initial query fails for some reason (e.g. REFUSED), the library > seems to be adding additional terminating domains to the end of the > hostname string. E.g. > "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net" > becomes > "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.blah.com" > "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.foo.net" > > These are specified in my /etc/resolve.conf as > > search blah.com foo.net > > Is there a way to tell the lookup that the initial name passed to the Lookup > constructor is absolute, and no additional resolution should be done? > > Thanks, > Garth > > ------------------------------------------------------------------------------ > Is your legacy SCM system holding you back? Join Perforce May 7 to find out: > • 3 signs your SCM is hindering your productivity • Requirements > for releasing software faster • Expert tips and advice for migrating your > SCM now http://p.sf.net/sfu/perforce > _______________________________________________ > dnsjava-users mailing list > dns...@li... > https://lists.sourceforge.net/lists/listinfo/dnsjava-users |
From: Garth P. <ga...@tw...> - 2014-05-09 19:45:51
|
Thank you! On Fri, May 9, 2014 at 12:34 PM, Jack Tavares <j.t...@f5...> wrote: > If you want the host name to be treated like an absolute name, you need > to provide an absolute name. > > In other words, terminate your host name with a dot "." > > So your code should be: > Lookup lookup = new Lookup("2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.", > >> -----Original Message----- >> From: Garth Patil [mailto:ga...@tw...] >> Sent: Friday, May 09, 2014 11:56 AM >> To: dns...@li... >> Subject: Appending to absolute name on failure >> >> I am using the dnsjava library to query a NAPTR record: >> >> SimpleResolver resolver = new SimpleResolver(X.X.X.X); >> resolver.setPort(53); >> Lookup lookup = new Lookup("2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net", >> Type.NAPTR); >> lookup.setResolver(resolver); >> Record[] records = lookup.run(); >> >> When the initial query fails for some reason (e.g. REFUSED), the library >> seems to be adding additional terminating domains to the end of the >> hostname string. E.g. >> "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net" >> becomes >> "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.blah.com" >> "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.foo.net" >> >> These are specified in my /etc/resolve.conf as >> >> search blah.com foo.net >> >> Is there a way to tell the lookup that the initial name passed to the Lookup >> constructor is absolute, and no additional resolution should be done? >> >> Thanks, >> Garth >> >> ------------------------------------------------------------------------------ >> Is your legacy SCM system holding you back? Join Perforce May 7 to find out: >> • 3 signs your SCM is hindering your productivity • Requirements >> for releasing software faster • Expert tips and advice for migrating your >> SCM now http://p.sf.net/sfu/perforce >> _______________________________________________ >> dnsjava-users mailing list >> dns...@li... >> https://lists.sourceforge.net/lists/listinfo/dnsjava-users |
From: Garth P. <ga...@tw...> - 2014-05-09 19:20:09
|
I am using the dnsjava library to query a NAPTR record: SimpleResolver resolver = new SimpleResolver(X.X.X.X); resolver.setPort(53); Lookup lookup = new Lookup("2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net", Type.NAPTR); lookup.setResolver(resolver); Record[] records = lookup.run(); When the initial query fails for some reason (e.g. REFUSED), the library seems to be adding additional terminating domains to the end of the hostname string. E.g. "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net" becomes "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.blah.com" "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.foo.net" These are specified in my /etc/resolve.conf as search blah.com foo.net Is there a way to tell the lookup that the initial name passed to the Lookup constructor is absolute, and no additional resolution should be done? Thanks, Garth |
From: Garth P. <ga...@tw...> - 2014-05-09 19:19:35
|
Is it sufficient to set the search path to an empty array? lookup.setSearchPath(new String[0]); On Fri, May 9, 2014 at 11:55 AM, Garth Patil <ga...@tw...> wrote: > I am using the dnsjava library to query a NAPTR record: > > SimpleResolver resolver = new SimpleResolver(X.X.X.X); > resolver.setPort(53); > Lookup lookup = new Lookup("2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net", > Type.NAPTR); > lookup.setResolver(resolver); > Record[] records = lookup.run(); > > When the initial query fails for some reason (e.g. REFUSED), the > library seems to be adding additional terminating domains to the end > of the hostname string. E.g. > "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net" > becomes > "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.blah.com" > "2.1.2.1.5.5.5.5.1.4.1.1.e164enum.net.foo.net" > > These are specified in my /etc/resolve.conf as > > search blah.com foo.net > > Is there a way to tell the lookup that the initial name passed to the > Lookup constructor is absolute, and no additional resolution should be > done? > > Thanks, > Garth |
From: <ste...@or...> - 2013-12-04 17:47:38
|
In a SRV record, there are 4 parameters, so the replace has to be something like: update.replace(host, Type.SRV, 3600, "0 0 30443 host"); De : ste...@or... [mailto:ste...@or...] Envoyé : mercredi 4 décembre 2013 18:09 À : dns...@li... Objet : SRV Type record Hello, I would like to update a SRV record with the following code: Name zone = Name.fromString("mydomain.com."); Name host = Name.fromString("host", zone); Update update = new Update(zone); update.replace(host, Type.SRV, 3600, "30443"); Resolver res = new SimpleResolver(); res.setTSIGKey(new TSIG("HMAC-MD5", "ddns-key", "jlkdlfkjereuj" )); res.setTCP(true); Message response = res.send(update); But, the following error occurs: org.xbill.DNS.Tokenizer$TokenizerException: <none>:1: expected an integer at org.xbill.DNS.Tokenizer.exception(Tokenizer.java:691) at org.xbill.DNS.Tokenizer._getIdentifier(Tokenizer.java:383) The replace() is ok with other type of record (A for instance), but not with SRV. Any help, please ? Stéphane _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. |
From: <ste...@or...> - 2013-12-04 17:09:38
|
Hello, I would like to update a SRV record with the following code: Name zone = Name.fromString("mydomain.com."); Name host = Name.fromString("host", zone); Update update = new Update(zone); update.replace(host, Type.SRV, 3600, "30443"); Resolver res = new SimpleResolver(); res.setTSIGKey(new TSIG("HMAC-MD5", "ddns-key", "jlkdlfkjereuj" )); res.setTCP(true); Message response = res.send(update); But, the following error occurs: org.xbill.DNS.Tokenizer$TokenizerException: <none>:1: expected an integer at org.xbill.DNS.Tokenizer.exception(Tokenizer.java:691) at org.xbill.DNS.Tokenizer._getIdentifier(Tokenizer.java:383) The replace() is ok with other type of record (A for instance), but not with SRV. Any help, please ? Stéphane _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. |
From: Brian W. <bwe...@xb...> - 2013-08-01 01:42:19
|
On Jul 31, 2013, at 5:09 AM, Tekto <te...@ge...> wrote: > Hi Brian, > > On 07/26/2013 09:06 PM, Brian Wellington wrote:> > > > > I assume there's some missing code between the signMessage and verifyMessage? > > Passing the same Message object to both signMessage and verifyMessage > > doesn't work, since some of the internal Message state needed to > > verify is only filled in when the Message is parsed from wire format; > > that is, something like: > > Yes, you're right. I'd tried misc. thing to fiddle that out (including injecting captured requests with nsupdate) so I didn't remember > for sure the last steps. No problem. > > SIG0.signMessage(updateMessage, keyRecord, privKey, null); > > byte [] wire = msg.toWire(); > > Message msg = new Message(wire); > > SIG0.verifyMessage(msg, msg.toWire(), keyRecord, null); > > > > Without that, the code throws an ArrayIndexOutOfBoundsException, because it's badly handling the fact that the Message doesn't know where the start of the SIG0 record is (I've locally updated the code to throw a more useful NoSignatureException). > > > > With code like that added, I'm seeing the failure, although I'm not sure why I'm not seeing the same failure in the existing SIG0 test code I have. > > > > I'm going to try and adapt this sample code into a unit test, and commit the changes in the next few days. > > If you like, I can send you the test-key and host a used. I committed the fix and a unit test yesterday. Hopefully I'll have time to do a new release sometime in the next few days. Thanks again! Brian |
From: Tekto <te...@ge...> - 2013-07-31 12:09:27
|
Hi Brian, On 07/26/2013 09:06 PM, Brian Wellington wrote:> > > I assume there's some missing code between the signMessage and verifyMessage? > Passing the same Message object to both signMessage and verifyMessage > doesn't work, since some of the internal Message state needed to > verify is only filled in when the Message is parsed from wire format; > that is, something like: Yes, you're right. I'd tried misc. thing to fiddle that out (including injecting captured requests with nsupdate) so I didn't remember for sure the last steps. > SIG0.signMessage(updateMessage, keyRecord, privKey, null); > byte [] wire = msg.toWire(); > Message msg = new Message(wire); > SIG0.verifyMessage(msg, msg.toWire(), keyRecord, null); > > Without that, the code throws an ArrayIndexOutOfBoundsException, because it's badly handling the fact that the Message doesn't know where the start of the SIG0 record is (I've locally updated the code to throw a more useful NoSignatureException). > > With code like that added, I'm seeing the failure, although I'm not sure why I'm not seeing the same failure in the existing SIG0 test code I have. > > I'm going to try and adapt this sample code into a unit test, and commit the changes in the next few days. If you like, I can send you the test-key and host a used. > > Thanks! > > Brian > Bye, Adam |