<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Andrew Wiik on Medium]]></title>
        <description><![CDATA[Stories by Andrew Wiik on Medium]]></description>
        <link>https://medium.com/@Andywiik?source=rss-53fc9e5c79e8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*FGx2IctRLgP3WE6a.jpg</url>
            <title>Stories by Andrew Wiik on Medium</title>
            <link>https://medium.com/@Andywiik?source=rss-53fc9e5c79e8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:49:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Andywiik/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Twickd Security Vulnerability]]></title>
            <link>https://medium.com/@Andywiik/twickd-security-vulnerability-01-7dd2074dfcaf?source=rss-53fc9e5c79e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/7dd2074dfcaf</guid>
            <category><![CDATA[web]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cydia]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[jailbreak]]></category>
            <dc:creator><![CDATA[Andrew Wiik]]></dc:creator>
            <pubDate>Mon, 27 Apr 2020 16:50:43 GMT</pubDate>
            <atom:updated>2020-04-27T16:52:37.599Z</atom:updated>
            <cc:license>https://creativecommons.org/publicdomain/mark/1.0/</cc:license>
            <content:encoded><![CDATA[<p>For those unaware <a href="https://repo.twickd.com/">Twickd</a> is a Cydia Repository that facilitates the distribution and sale of software/design packages created by developers and designers for jailbroken iOS devices. Through a quick security audit I discovered that they had a pre-production environment exposed to the public that could be manipulated to expose database credentials and be used as a DDOS vector (and possibly other things, after I discovered the database issue I stopped looking).</p><h3>Database Credentials</h3><p>Using <a href="https://dnsdumpster.com/">dnsdumpster.com</a> I entered “twickd.com” and discovered a few sub-domains like <em>repo.pre-release.twickd.com </em>existed. That domain appeared to host a pre-production version of the main websites they run along with…. <strong>a debugging UI</strong>. The debugging UI by default blocked out any of the secrets in the configuration variables, which is great. It was however possible to crash pages that used a database connection and then have the database credentials exposed in the logs of the crash as seen below (database details have been omitted for obvious reasons).</p><figure><img alt="Screenshot showing the log where the database credidentials were leaked." src="https://cdn-images-1.medium.com/max/1024/1*CcOVoNC0neJ6tuM--qtIKA.jpeg" /></figure><p>I did initially check if the database was listening publicly using a simple web-based mysql tool and the tool said it could not connect. I could have been using the tool wrong so I amnot too sure whether that was accurate but when I contacted the developers they said the database was not listening publicly so that was also a win for them. The database not listening publicly means without gaining access to that server first I could not access data using the credentials I had obtained. While the developers told me the pre-production database was empty because they were using the root password to access it if the database instance had been listening publicly data would still have been accessible on the production instance using the same credentials.</p><h3>DDOS Vector</h3><p>The pre-production website also exposed how much CPU and RAM it took to load particular pages, the site also was not rate-limited. This made it possible for just about anyone to perform a DDOS attack on the server. The production and pre-production sites at the time of discovery in Janurary 2020 were both hosted on the same server. I was made aware this is not the case anymore as of a month ago. This meant a DDOS on the pre-production site would have also brought down the production site when they were still hosted on the same server.</p><h3>Twickd’s Response</h3><p>When I was finally able to get a hold of the developers they fixed the issue immediately by blocking access to the pre-production site and changing the root user database credentials. They also asked me to mention that they don’t use the root database user to connect to the database in production.</p><h3>Final Note</h3><p>While I run and own a competing commercial Cydia Repository (<a href="https://repo.packix.com/">repo.packix.com</a>) I still very much believe in the responsible disclosure of vulnerabilities to competitors as well. This is especially important in small communities like the jailbreak one where a single repository mishandling data may lead users to not trust any repository to handle their data.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7dd2074dfcaf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Hidden PayPal API for Adding Tracking Info]]></title>
            <link>https://medium.com/@Andywiik/the-hidden-paypal-api-for-adding-tracking-info-c4049e07c68f?source=rss-53fc9e5c79e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4049e07c68f</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[payments]]></category>
            <category><![CDATA[paypal]]></category>
            <dc:creator><![CDATA[Andrew Wiik]]></dc:creator>
            <pubDate>Wed, 24 Apr 2019 14:42:00 GMT</pubDate>
            <atom:updated>2019-04-24T14:42:00.761Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*lUK7uWr_ruajahQ2p3iOpw.png" /></figure><p>So I run a software e-commerce platform called Packix. PayPal is one of the payment methods that is offered but since all the goods sold are digital we needed a way to mark the transactions as “Processed” to PayPal. PayPal has no public documentation on how to do this solely using the APIs so I went digging across the internet to find a solution and thankfully I found one that I will outline below in Javascript.</p><p>So the code is pretty simple, just note this is ES6 code that is usually transpiled with Babel.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9f68fee82fa4a0968957f2613da7a1f6/href">https://medium.com/media/9f68fee82fa4a0968957f2613da7a1f6/href</a></iframe><p>If you have any questions don’t hesitate to post them below or on the GitHub Gist.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4049e07c68f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Patreon — A Flawed Rewards System]]></title>
            <link>https://medium.com/@Andywiik/patreon-a-flawed-rewards-system-51e072cdd2ec?source=rss-53fc9e5c79e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/51e072cdd2ec</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[patreon]]></category>
            <category><![CDATA[support]]></category>
            <category><![CDATA[bugs]]></category>
            <dc:creator><![CDATA[Andrew Wiik]]></dc:creator>
            <pubDate>Fri, 23 Feb 2018 04:56:32 GMT</pubDate>
            <atom:updated>2018-02-23T04:56:32.708Z</atom:updated>
            <content:encoded><![CDATA[<p>About a month ago iOS Creatix started using Patreon as a means of rewarding those who support the work we do through bonus content such as extra downloads to early access of our creations.</p><p>Patreon has an issue though we discovered, someone may just pledge, go to all the paid content posts, download everything, then unpledge. This is a major blow to the users that do spend the money to help support Creatix because those who don’t are getting the same benefits as them. Patreon even recommends not giving access to content until a user has paid. This is great advice except Patreon currently offers no way to marks posts as only being available to those who have already been charged, and their API has no concrete way of currently finding out whether a user has been charged successfully through un-pledging, refunds, and other transactions.</p><p>The platform has a ‘Beta’ feature called ‘Charge up Front’ that would allow creators to make it so patreon’s are charged as soon as they pledge. This feature however is only rolled out to certain accounts and the majority of creators on the platform do not have this option available for their campaigns.</p><p>I really hope the developers of Patreon see this and can do something about it in the near future or I could see a lot of Creators moving to a platform where this flaw is not present.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51e072cdd2ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Apple, make your .caml format a public API please]]></title>
            <link>https://medium.com/ios-creatix/apple-make-your-caml-format-a-public-api-please-9e10ba126e9d?source=rss-53fc9e5c79e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e10ba126e9d</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[svg]]></category>
            <dc:creator><![CDATA[Andrew Wiik]]></dc:creator>
            <pubDate>Wed, 09 Aug 2017 17:38:34 GMT</pubDate>
            <atom:updated>2017-08-09T18:27:16.762Z</atom:updated>
            <content:encoded><![CDATA[<p>While working on an upcoming jailbreak tweak called “Maize” that is meant to bring the iOS 11 Control Center back to iOS 10 I came across .caml files. I found out these were how apple was animating the Control Center Toggles. After researching the file format more and how Apple was using it I wondered why the API wasn’t a public one.</p><h3>Wait, what are .caml files?</h3><p>.caml files are files that store information for core graphics and core animation code in a xml file format. To my best guess <strong>CAML</strong> stands for <strong>Core Animation Markup Language</strong>. CAML files can basically store CALayer’s and animations for them. Here is a short example of what the contents of a .caml file may look like:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e53f13a0692a3210f7813b7dc83de6d1/href">https://medium.com/media/e53f13a0692a3210f7813b7dc83de6d1/href</a></iframe><p>If you have every worked with <strong>CALayer’s</strong> or any of its various subclass a lot of this may look very familiar to you, like the <strong>CATransformLayer </strong>or <strong>CAShapeLayer</strong>. The path property for the CAShapeLayer is very similar to the path of a <strong>SVG</strong> document , actually a lot of the .caml format can be related to a <strong>SVG</strong> file.</p><h3>Animations in a .caml file</h3><p>Here is what is really cool about <strong>CAML</strong> files, they can store animations and those animations can be named and then simply invoked via code, here is an example of the same bluetooth toggle except now it has a on, off, and searching state, when in the search state the toggle fades in and out in an infinite loop.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/55d26a65c2cc90c162abf2f4f02c90be/href">https://medium.com/media/55d26a65c2cc90c162abf2f4f02c90be/href</a></iframe><p>Notice now we have a “states” key and value, this defines all the different “states” this object can have along with how it should animate to each state and how long those animations should last. each state is defined as an <strong>LKState</strong>, though in reality it is really a <strong>CAState</strong>, each state has a name along with optionally being “based-on’ aka inheriting from another state. Each <strong>CAState</strong> can alse define what properties on each <strong>CALayer</strong> should be changed for that state. When the layers and sublayers were first defined they could be given an <strong>id</strong> with a number along with a <strong>name</strong> which is humanized string of what that layer may represent in respect to the overall “design” the file is producing. The <strong>id</strong> is used to specify what layer you want to do a property change on when you define the changed properties for a state. Then you can define “state transitions” for each state that defines how each property change should be animated via <strong>LKStateTransition</strong>, which is really a <strong>CAStateTransition</strong>. CAStateTransition can define durations along with whether certain changes should be keyframe based or just a simple timing curve, both which are in the example above. A <strong>CAStateTransition</strong> can be defined for every possible “state-to-state” so that your animations always look smooth.</p><p><strong>This is all great but why would this be useful for app developers and designers?</strong></p><p>Some great apps exist like <strong>PaintCode</strong> that can take SVGs and convert them to CoreGraphics drawing code for your app, this is great because having your graphic assets of your app be one size fits all can make the overall size of your app smaller and having that in code makes it even better, but the current state of using these apps results in a couple problems I believe. One being that it can make a code base very messy in the long run and a lot of the code these apps produce isn’t very “human readable”. Also most of these apps don’t support animations or the ones that do just produce even more spaghetti code that then causes your app to take even longer to compile. If apple made the .caml file format allowed to be used Apps along with making the corresponding CoreAnimation classes public it could drastically reduce the size of some apps even more and make animations that much more easier for apps to implementation for simple things like glyphs up to complex scenes like a fancy intro screen. You could even for example just have your app download new animations on the fly and then store them in the local user directory. The power of being able to decouple your design assets from your code while allowing those design assets to be vectorized and each have their own animations is a powerful thing. I truly believe Apple’s currently non-public .caml file format and its corresponding private CoreAnimation classes could be the future of iOS Design and Graphic Assets. They would allow even smaller app sizes with even more beautiful graphic assets that can each have their own animations.</p><p>More examples of .caml files and how to display them can be found on the public repository for <strong>Maize, </strong>for how to display them look at the <strong>MZECAPackageView </strong>class in the <strong>MaizeUI</strong> folder, and for the actual .caml files look under the <strong>Modules</strong> folder in various Modules, a good example is the <strong>ConnectivityModule</strong>. The Maize repository can be found <a href="https://github.com/ioscreatix/Maize">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e10ba126e9d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ios-creatix/apple-make-your-caml-format-a-public-api-please-9e10ba126e9d">Apple, make your .caml format a public API please</a> was originally published in <a href="https://medium.com/ios-creatix">iOS Creatix</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We now have a Blog!!!]]></title>
            <link>https://medium.com/ios-creatix/we-now-have-a-blog-be3147d3b869?source=rss-53fc9e5c79e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/be3147d3b869</guid>
            <dc:creator><![CDATA[Andrew Wiik]]></dc:creator>
            <pubDate>Fri, 04 Aug 2017 06:16:18 GMT</pubDate>
            <atom:updated>2017-08-04T06:16:18.017Z</atom:updated>
            <content:encoded><![CDATA[<p>This is just an introductory post to let you guys know we now have a blog and will be trying to use it whenever possible</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=be3147d3b869" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ios-creatix/we-now-have-a-blog-be3147d3b869">We now have a Blog!!!</a> was originally published in <a href="https://medium.com/ios-creatix">iOS Creatix</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>