<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Order Processing.  in Plusnet Feedback</title>
    <link>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305473#M69653</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Quote from: ejs&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;The password for the PPP auth would need to be retrievable.&lt;BR /&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;I think it would be practical to store the password encrypted as a one way hash and the on PPP authentication one uses the same encryption on the supplied password and compares it to the stored hash. If they match the supplied password is deemed to be correct.</description>
    <pubDate>Fri, 15 Jan 2016 23:05:24 GMT</pubDate>
    <dc:creator>Townman</dc:creator>
    <dc:date>2016-01-15T23:05:24Z</dc:date>
    <item>
      <title>Order Processing.</title>
      <link>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305469#M69649</link>
      <description>Not sure where I can post this, but I have noticed an error on the order tracing page, &lt;BR /&gt;On the Broadband part is states&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Quote&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Your order is due to complete&lt;BR /&gt;The engineer appointment to install your broadband service is booked for %appointmentDate% between %appointmentStartTime% and %appointmentFinishTime%.&lt;BR /&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;So a&amp;nbsp; little quality control would be of use here.&lt;BR /&gt;I'm also concerned about parts of passwords being printed in letters, see my other post, does this mean PlusNet are storing plain text passwords, (ie not encrypted)</description>
      <pubDate>Fri, 15 Jan 2016 19:19:27 GMT</pubDate>
      <guid>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305469#M69649</guid>
      <dc:creator>leonaplusnet</dc:creator>
      <dc:date>2016-01-15T19:19:27Z</dc:date>
    </item>
    <item>
      <title>Re: Order Processing.</title>
      <link>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305470#M69650</link>
      <description>This is the right place for this post.&lt;BR /&gt;Thanks for the feedback, I'll get that flagged up tomorrow when I'm back in work. &lt;BR /&gt;In regards to the passwords, no we do not store these as plain text.</description>
      <pubDate>Fri, 15 Jan 2016 19:45:40 GMT</pubDate>
      <guid>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305470#M69650</guid>
      <dc:creator>HarryB</dc:creator>
      <dc:date>2016-01-15T19:45:40Z</dc:date>
    </item>
    <item>
      <title>Re: Order Processing.</title>
      <link>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305471#M69651</link>
      <description>But the passwords are stored so that the plain text of the password can be retrieved. This issue must have been raised numerous times over the years. Changing it would require having one password for the member centre, and another password for the PPP authentication the router does when it connects to Plusnet. The password for the PPP auth would need to be retrievable.</description>
      <pubDate>Fri, 15 Jan 2016 19:57:41 GMT</pubDate>
      <guid>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305471#M69651</guid>
      <dc:creator>ejs</dc:creator>
      <dc:date>2016-01-15T19:57:41Z</dc:date>
    </item>
    <item>
      <title>Re: Order Processing.</title>
      <link>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305472#M69652</link>
      <description>Thank you HarryB, look forward to the results of your investigation. &lt;BR /&gt;Indeed EJS, the password for our online account should NOT be the same as for our Broadband access, as this password can be 'sniffed' or otherwise recovered and then used to log into our on-line accounts, this is surly a very high security risk, with the attach on TalkTalk very recently, (my previous supplier, thankfully my data wasn't stolen) my anxiety level is Very high, I am a software developer with experience in the area of security and I can see that there is a security hole here that needs to be closed before another school kid decides to take advantage of it &lt;BR /&gt;While you might not store them as plain text, they are being decrypted, this shouldn't be possible, they should be hashed and salted, then a comparison performed to compare patterns, they should not be retrievable and most certainly not printed in letters! &lt;BR /&gt;Our online account have our bank, home and personal details, this would allow anyone who comprised your system to use this data illegally, I surely don't have to highlight how much damaging this would be, maybe over reacting but, as I said I've been bitten before by poorly secured systems, I don't want to be a victim of another, I need reassurance, backed up with evidence that your systems are secure, ie, do you run penetration tests, security checks, monitoring, etc?</description>
      <pubDate>Fri, 15 Jan 2016 22:25:59 GMT</pubDate>
      <guid>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305472#M69652</guid>
      <dc:creator>leonaplusnet</dc:creator>
      <dc:date>2016-01-15T22:25:59Z</dc:date>
    </item>
    <item>
      <title>Re: Order Processing.</title>
      <link>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305473#M69653</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Quote from: ejs&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;The password for the PPP auth would need to be retrievable.&lt;BR /&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;I think it would be practical to store the password encrypted as a one way hash and the on PPP authentication one uses the same encryption on the supplied password and compares it to the stored hash. If they match the supplied password is deemed to be correct.</description>
      <pubDate>Fri, 15 Jan 2016 23:05:24 GMT</pubDate>
      <guid>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305473#M69653</guid>
      <dc:creator>Townman</dc:creator>
      <dc:date>2016-01-15T23:05:24Z</dc:date>
    </item>
    <item>
      <title>Re: Order Processing.</title>
      <link>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305474#M69654</link>
      <description>Someone might think that, if they don't know how it works.&lt;BR /&gt;&lt;A href="https://tools.ietf.org/html/rfc1994" target="_blank"&gt;https://tools.ietf.org/html/rfc1994&lt;/A&gt;&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Quote&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;[tt]&lt;B&gt;2.1.&amp;nbsp; Advantages&lt;/B&gt;&lt;BR /&gt;...&lt;BR /&gt;&amp;nbsp;  This authentication method depends upon a "secret" known only to the&lt;BR /&gt;&amp;nbsp;  authenticator and that peer.&amp;nbsp; The secret is not sent over the link.&lt;BR /&gt;...&lt;BR /&gt;&lt;B&gt;2.2.&amp;nbsp; Disadvantages&lt;/B&gt;&lt;BR /&gt;&amp;nbsp;  CHAP requires that the secret be available in plaintext form.&lt;BR /&gt;&amp;nbsp;  Irreversably encrypted password databases commonly available cannot&lt;BR /&gt;&amp;nbsp;  be used.[/tt]&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;The other end does not receive a supplied password during the PPP authentication.</description>
      <pubDate>Sat, 16 Jan 2016 07:24:32 GMT</pubDate>
      <guid>https://community.plus.net/t5/Plusnet-Feedback/Order-Processing/m-p/1305474#M69654</guid>
      <dc:creator>ejs</dc:creator>
      <dc:date>2016-01-16T07:24:32Z</dc:date>
    </item>
  </channel>
</rss>

