相关文章推荐
深沉的便当  ·  GitHub | DevOps ...·  5 月前    · 
绅士的竹笋  ·  海悅聯名卡·  1 年前    · 
阳刚的烤地瓜  ·  Parsing dates in ...·  1 年前    · 
刚毅的酱牛肉  ·  java bufferedwriter ...·  1 年前    · 
  • Go here
  • Get the line that looks like this: const BYPASS_SEQUENCE = window.atob('dGhpc2lzdW5zYWZl');
  • Get a cert error, e.g. HSTS
  • Pull up developer tools (F12) and go to the console tab
  • Paste in everything that you got after the = back in step 2. (i.e. window.atob('dGhpc2lzdW5zYWZl') )
  • a. This will give you a plaintext bypass keystroke sequence to bypass the cert warning. 6. Get focus on the cert error page and type in the keystroke exactly how it appeared in the output of the console command. For the example above, it was `thisisunsafe'. This code is periodically changed. 7. woosh You're in.

    Or rather than all this hussle simply type this: thisisunsafe
    ...on that page and chrome will take you there.

    that string in window_atob() is just a base64 of thisisunsafe .

    Or rather than all this hussle simply type this: thisisunsafe
    ...on that page and chrome will take you there.

    that string in window_atob() is just a base64 of thisisunsafe .

    True, but they have changed what the string is before. It used to be badidea .