Forums
New posts
New posts
Search forums
Market
Domains/Websites Wanted
.com Domain Market
gTLD Domain Market
ccTLD Domain Market
Web3 Domain Market
Third-Level Domain Market
Adult Domain Market
What's New
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Account Upgrade
Premium Members Directory
Log in
Register
What's New
calendar
Search
Search
Search titles only
By:
New posts
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Enjoy unlimited access to all forum features for FREE! Optional upgrade available for extra perks.
Forums
Domain Discussion
Domain Name News
Was there a Hack/Data Breach at Epik?
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Tom K." data-source="post: 2348971" data-attributes="member: 67334"><p>You can get a lot results in Google. But for example, when connecting to the database you should write prepared statements, open and close transactions when doing updates, keep the code up to date with the current language processor updates. Secure code is only part of the equation. The list is too long to write here.</p><p></p><p></p><p></p><p>[USER=143534]@robmonster[/USER] made it clear that the code was kept captive by the developer, it was boxed, and he operated with the Russia-based dev team on the basis of trust. And the code was from 2009. So that is very old code. Rob admitted it was seriously weak. So it raises the question, when did the code become open-source to Epik and when was the last security update made?</p><p></p><p></p><p></p><p>If the code was not being updated to work with the latest language processor versions over the years, and that's what it sounds like, the only option is a complete rewrite. IMHO.</p></blockquote><p></p>
[QUOTE="Tom K., post: 2348971, member: 67334"] You can get a lot results in Google. But for example, when connecting to the database you should write prepared statements, open and close transactions when doing updates, keep the code up to date with the current language processor updates. Secure code is only part of the equation. The list is too long to write here. [USER=143534]@robmonster[/USER] made it clear that the code was kept captive by the developer, it was boxed, and he operated with the Russia-based dev team on the basis of trust. And the code was from 2009. So that is very old code. Rob admitted it was seriously weak. So it raises the question, when did the code become open-source to Epik and when was the last security update made? If the code was not being updated to work with the latest language processor versions over the years, and that's what it sounds like, the only option is a complete rewrite. IMHO. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Domain Discussion
Domain Name News
Was there a Hack/Data Breach at Epik?
Top
Bottom