Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.
  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
fs0c131y's profile
Elliot Alderson
Elliot Alderson
Elliot Alderson
@fs0c131y

Tweets

Elliot Alderson

@fs0c131y

French security researcher. Worst nightmare of Oneplus, Wiko, UIDAI, Kimbho, Donald Daters and others. Not completely schizophrenic. Not related to USANetwork.

Joined June 2015

Tweets

  • © 2018 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    Elliot Alderson‏ @fs0c131y Oct 15

    It's probably not a good idea to expose all your ids and keys... In the app you can find: - google_api_key - google_app_id - google_crash_reporting_api_key - default_web_client_id - facebook_app_id - RNB_GOOGLE_PLAY_LICENSE_KEYpic.twitter.com/5CUxlqggFs

    1:09 PM - 15 Oct 2018
    • 27 Retweets
    • 117 Likes
    • GalGaloot 🇮🇱 fe 🔥ĈȳβεЯيӛƈƧƫƯ🔥 نیما Mußeen Sháikh Justin_Powzy hardikp13 Étienne Parth Shaha
    6 replies 27 retweets 117 likes
      1. New conversation
      2. Aissen‏ @Aissn Oct 15
        Replying to @fs0c131y

        That's how those SDKs work. They require an API key in the client. Which are trivial to extract for most apps. Some attempt to obfuscate with native libs, custom protocols, attestations, etc. But most juicy targets end up leaking.

        2 replies 0 retweets 12 likes
      3. Eliseo Martelli‏ @eliseomartelli Oct 15
        Replying to @Aissn @fs0c131y

        Yeah but have the decency of not putting them in the res folder!

        1 reply 0 retweets 2 likes
      4. Aissen‏ @Aissn Oct 15
        Replying to @eliseomartelli @fs0c131y

        Meh, it's a broken model from the start.

        2 replies 0 retweets 4 likes
      5. Michael  🔥 McDonald‏ @asciimike Oct 16
        Replying to @Aissn @eliseomartelli @fs0c131y

        (Disclosure: Firebase PM) Storing resource identifiers client side is not a broken model: consider an app that stores a URL to their API (which is what we see here with `firebase_database_url`). It's necessary for the app to work, and not intended to be secret.

        1 reply 4 retweets 21 likes
      6. Michael  🔥 McDonald‏ @asciimike Oct 16
        Replying to @asciimike @Aissn and

        API keys may or may not be secret, depending on what the authN/Z model of the backend systems are. Generally speaking, API keys should be used to identify a client (so as to apply quota/rate limits, billing), not to authenticate/authorize an application.

        1 reply 0 retweets 5 likes
      7. Michael  🔥 McDonald‏ @asciimike Oct 16
        Replying to @asciimike @Aissn and

        For services that do treat API keys as shared secrets; obviously, storing them client side is a bad idea. Some Google APIs do allow API key only access, but we've strongly discouraged use (https://cloud.google.com/docs/authentication/#api_keys …).

        1 reply 0 retweets 3 likes
      8. Michael  🔥 McDonald‏ @asciimike Oct 16
        Replying to @asciimike @Aissn and

        That's also not to say there aren't attack vectors here. Someone can abuse your API (consume quota, economic DoS), or clone your app. But that's not what happened here.

        1 reply 0 retweets 2 likes
      9. Michael  🔥 McDonald‏ @asciimike Oct 16
        Replying to @asciimike @Aissn and

        Regardless of the backend you use (built by you, your best friend, or your favorite cloud provider), you need to implement reasonable server side security in order to prevent issues that malicious clients may cause.

        1 reply 0 retweets 1 like
      10. 7 more replies
      1. abc123‏ @junooniyaat Oct 15
        Replying to @fs0c131y

        But on the other hand, the app developers are a good reflection of the base. Both are dumb.

        0 replies 0 retweets 2 likes
        Thanks. Twitter will use this to make your timeline better. Undo
        Undo
      1. ‏لوپریت سنگھ‏ @luvpreet33 Oct 15
        Replying to @fs0c131y

        thanks

        0 replies 0 retweets 2 likes
        Thanks. Twitter will use this to make your timeline better. Undo
        Undo
      1. New conversation
      2. Mayank raj‏ @imRajMayank Oct 15
        Replying to @fs0c131y

        Ok so, where should it be kept ?

        1 reply 0 retweets 2 likes
      3. 1 more reply
      1. WADEL STRUZIK‏ @StruzikWadel Oct 16
        Replying to @fs0c131y

        Kek!

        0 replies 0 retweets 0 likes
        Thanks. Twitter will use this to make your timeline better. Undo
        Undo
      1.  ⚡️marpme‏ @marpme_ Oct 15
        Replying to @fs0c131y

        The least you could have done is to not share them over here too 🤭

        0 replies 0 retweets 0 likes
        Thanks. Twitter will use this to make your timeline better. Undo
        Undo

    Loading seems to be taking a while.

    Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

      Promoted Tweet

      false

      • © 2018 Twitter
      • About
      • Help Center
      • Terms
      • Privacy policy
      • Cookies
      • Ads info