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.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • 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
David3141593's profile
Dаvіd Вucһаnаn
Dаvіd Вucһаnаn
Dаvіd Вucһаnаn
@David3141593

Tweets

Dаvіd Вucһаnаn

@David3141593

from pwn import *; alias = "Retr0id"

Ring -1
da.vidbuchanan.co.uk
Joined December 2013

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • 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.

    1. Nick Drage‏ @SonOfSunTzu 23 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @quentynblog @cybergibbons and

      Bah, it's a minor security feature too - no harm in avoiding a whole swathe of automated attacks - providing this kind of measure doesn't give you any admin overhead I think "additional security through a little obscurity" is under-rated.

      2 replies 0 retweets 0 likes
    2. Sven Slootweg‏ @joepie91 23 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @SonOfSunTzu @quentynblog and

      If you are already following good security practices (eg. using keypair authentication), then moving to a different port will accomplish exactly nothing in terms of security. No, it isn't even a minor security feature.

      2 replies 0 retweets 0 likes
    3. Sven Slootweg‏ @joepie91 23 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @joepie91 @SonOfSunTzu and

      (And if you *aren't* following good security practices, then *at best* it delays the inevitable moment that your box gets popped by a few days.)

      1 reply 0 retweets 0 likes
    4. Nick Drage‏ @SonOfSunTzu 23 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @joepie91 @quentynblog and

      Good security practices such as keypair authentication generally help, but there's an issue with the SSH daemon itself, you will avoid any scattergun attacks by being on a non-standard port. Also your threat model assumes a determined attacker, which isn't always the case.

      1 reply 0 retweets 0 likes
    5. Sven Slootweg‏ @joepie91 23 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @SonOfSunTzu @quentynblog and

      No, you won't. SSH scans haven't been limited to port 22 for a few years now, so you'll still get hit by automated scans; just less of them.

      2 replies 0 retweets 0 likes
    6. Cybergibbons‏ @cybergibbons 23 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @joepie91 @SonOfSunTzu and

      A lot less of them though.

      1 reply 0 retweets 1 like
    7. Sven Slootweg‏ @joepie91 23 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @cybergibbons @SonOfSunTzu and

      But "a lot less" doesn't matter if compromise is still inevitable, that's my point. Whether it takes 5 days or 10 days, you're still pwnt.

      2 replies 0 retweets 0 likes
    8. Cybergibbons‏ @cybergibbons 23 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @joepie91 @SonOfSunTzu and

      I don't understand why. You would need my private key and then further priv esc for that to happen.

      1 reply 0 retweets 1 like
    9. Sven Slootweg‏ @joepie91 23 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @cybergibbons @SonOfSunTzu and

      I'm assuming an improperly secured system, eg. using a trivially bruteforceable password. If you're using a strong randomly generated password or keypair authentication, then the entire discussion is moot because your system won't be pwned on port 22 either.

      1 reply 0 retweets 0 likes
    10. Sven Slootweg‏ @joepie91 23 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @joepie91 @cybergibbons and

      Either way, moving your SSHd to a different port does not produce any meaningful difference in susceptibility to attacks. It's rearranging the deck chairs on the Titanic.

      2 replies 0 retweets 0 likes
      Dаvіd Вucһаnаn‏ @David3141593 23 Aug 2018
      • Report Tweet
      • Report NetzDG Violation
      Replying to @joepie91 @cybergibbons and

      Lets say an SSHd 0day comes out tomorrow. All the vuln scanners will be targeting port 22 at first, because that's where they're guaranteed to get hits. Sure, the more obscure ports will get scanned eventually, but that at least gives you more time to patch.

      4:17 PM - 23 Aug 2018
      • 1 Like
      • Whitney
      1 reply 0 retweets 1 like
        1. New conversation
        2. Sven Slootweg‏ @joepie91 23 Aug 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @David3141593 @cybergibbons and

          Given how fast it is to do an address-space-wide scan on all ports nowadays, the time difference is absolutely not going to matter.

          1 reply 0 retweets 0 likes
        3. Cybergibbons‏ @cybergibbons 23 Aug 2018
          • Report Tweet
          • Report NetzDG Violation
          Replying to @joepie91 @David3141593 and

          Again, not sure if I agree. I have left services running on non-standard ports and they went months between being fingerprinted. Port scans might be easy and quick. Fingerprinting every service, not really.

          0 replies 0 retweets 0 likes
        4. End of conversation

      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

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