cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

stronger browser security...

http://community.ebay.com/t5/Announcements/Stronger-Browser-Security-Standards-Ahead/ba-p/27389922

 

OK i'll admit.. I have no idea what this all means....can someone , in a nut shell, give me a version i can understand?

 

Message 1 of 112
latest reply
111 REPLIES 111

stronger browser security...


@rainbowcolorz wrote:

@a_c_green wrote:

@pingpong517 wrote:

 

OK i'll admit.. I have no idea what this all means....can someone , in a nut shell, give me a version i can understand?


I can have a bash at it. Let me try to boil it down to a bulleted list...

  • About half the users out there are using Google Chrome, so eBay wants to play nice with it.
  • In this coming October, Google will be updating the browser to display a "Not Secure" message if the header is showing a web page that's either not using a secure connection (i.e. a web page beginning with "https:" rather than "http:"), or a secure connection that's got some insecure (http: ) code inside it. 
  • Web pages with addresses beginning with "https:" are secure (such as what you see for on-line banking and such)
  • Web pages with addresses beginning with "http:" are not secure. It's possible to download something nefarious via an http: connection that would be blocked by a secure https: connection.
  • It's possible to embed http: code within a page that itself is https: secure. That could be a Bad Thingâ„¢.
  • eBay recognizes that a user could upload http: code within their product descriptions that could cause trouble within eBay's https: web pages, such as links to external sources.
  • If that happens, the new Google Chrome will detect the lurking http: code, and flash a "Not Secure" warning across the top of the eBay viewer's screen.
  • eBay believes that this may cause undue alarm among potential eBay buyers, causing some of them to become dizzy or lightheaded, and have to go lie down for a while, thus preventing them from buying things. eBay says that the "Not Secure" warning may cause you to suffer a decrease in conversion rates as a result. (When that happens to me, I recommend Metamucil.)
  • Therefore, if eBay finds that you've got http: coding in your listing, they will hide it behind a button in the desktop view, telling users to click the button in order to see your description.
  • This doesn't affect mobile viewers, for unexplained reasons. (Possibly their view of your description is already hidden behind a button anyway.)
  • Therefore the best thing to do is ensure that you don't have http: coding in your listing. Something called the "i-ways tool" (here) can inspect your listings for you.
  • Therefore, when it comes to listing layout, the K.I.S.S. rule ("Keep It Simple, Stupid") is becoming more important all the time.

Wow.  @a_c_green, thanks for all that info.  I bookmarked your post and got that blue box that said Success Bookmarked!  

But where did it bookmark your post to???  


Your Profile/Settings/SUBSCRIPTIONS & NOTIFICATIONS/BookMarks

~Pika~
People in life that are the happiest don't have the most,, they make the most of what they have...

Message 31 of 112
latest reply

stronger browser security...


@rainbowcolorz wrote:

@a_c_green wrote:

@pingpong517 wrote:

 

OK i'll admit.. I have no idea what this all means....can someone , in a nut shell, give me a version i can understand?


I can have a bash at it. Let me try to boil it down to a bulleted list...

  • About half the users out there are using Google Chrome, so eBay wants to play nice with it.
  • In this coming October, Google will be updating the browser to display a "Not Secure" message if the header is showing a web page that's either not using a secure connection (i.e. a web page beginning with "https:" rather than "http:"), or a secure connection that's got some insecure (http: ) code inside it. 
  • Web pages with addresses beginning with "https:" are secure (such as what you see for on-line banking and such)
  • Web pages with addresses beginning with "http:" are not secure. It's possible to download something nefarious via an http: connection that would be blocked by a secure https: connection.
  • It's possible to embed http: code within a page that itself is https: secure. That could be a Bad Thingâ„¢.
  • eBay recognizes that a user could upload http: code within their product descriptions that could cause trouble within eBay's https: web pages, such as links to external sources.
  • If that happens, the new Google Chrome will detect the lurking http: code, and flash a "Not Secure" warning across the top of the eBay viewer's screen.
  • eBay believes that this may cause undue alarm among potential eBay buyers, causing some of them to become dizzy or lightheaded, and have to go lie down for a while, thus preventing them from buying things. eBay says that the "Not Secure" warning may cause you to suffer a decrease in conversion rates as a result. (When that happens to me, I recommend Metamucil.)
  • Therefore, if eBay finds that you've got http: coding in your listing, they will hide it behind a button in the desktop view, telling users to click the button in order to see your description.
  • This doesn't affect mobile viewers, for unexplained reasons. (Possibly their view of your description is already hidden behind a button anyway.)
  • Therefore the best thing to do is ensure that you don't have http: coding in your listing. Something called the "i-ways tool" (here) can inspect your listings for you.
  • Therefore, when it comes to listing layout, the K.I.S.S. rule ("Keep It Simple, Stupid") is becoming more important all the time.

Wow.  @a_c_green, thanks for all that info.  I bookmarked your post and got that blue box that said Success Bookmarked!  

But where did it bookmark your post to???  


wow..that is a good question too....

Message 32 of 112
latest reply

stronger browser security...

Sounds like a trap to me.! 

I'm the suspicious type. My older brother was always playing he was some kind of commie hiding in the bushes and ambushing me. For you trusting folks, get back to us on this...if you can...

Message 33 of 112
latest reply

stronger browser security...

readabouthorses wrote:
@pikabo-icu wrote:

This will give any buyer using Chrome a warning of an NON SECURE page..

That is distressing to many people. It's for the use of HTML coding. 

 

So in the post by Sweet Tea or the link here: http://community.ebay.com/t5/Announcements/Stronger-Browser-Security-Standards-Ahead/ba-p/27389922

There's a program/link to test your listings..

 

If they have HTML, you can edit it out and your buyers will not see the warning on Chrome.. 

So I'm guessing you are giving that company the same permission to access your listings/account that you do with a third party listing service? Because when I tried it they wanted my User ID and password to eBay.

You can back out of that and enter in listing numbers. I sure didn't give them any user info.

 

 

_____________________________
"Nothing is obvious to the oblivious"
Message 34 of 112
latest reply

stronger browser security...

ersatz did he ever make you narkel the garfunk?

Message 35 of 112
latest reply

stronger browser security...


@pikabo-icu wrote:

@rainbowcolorz wrote:

@a_c_green wrote:

@pingpong517 wrote:

 

OK i'll admit.. I have no idea what this all means....can someone , in a nut shell, give me a version i can understand?


I can have a bash at it. Let me try to boil it down to a bulleted list...

  • About half the users out there are using Google Chrome, so eBay wants to play nice with it.
  • In this coming October, Google will be updating the browser to display a "Not Secure" message if the header is showing a web page that's either not using a secure connection (i.e. a web page beginning with "https:" rather than "http:"), or a secure connection that's got some insecure (http: ) code inside it. 
  • Web pages with addresses beginning with "https:" are secure (such as what you see for on-line banking and such)
  • Web pages with addresses beginning with "http:" are not secure. It's possible to download something nefarious via an http: connection that would be blocked by a secure https: connection.
  • It's possible to embed http: code within a page that itself is https: secure. That could be a Bad Thingâ„¢.
  • eBay recognizes that a user could upload http: code within their product descriptions that could cause trouble within eBay's https: web pages, such as links to external sources.
  • If that happens, the new Google Chrome will detect the lurking http: code, and flash a "Not Secure" warning across the top of the eBay viewer's screen.
  • eBay believes that this may cause undue alarm among potential eBay buyers, causing some of them to become dizzy or lightheaded, and have to go lie down for a while, thus preventing them from buying things. eBay says that the "Not Secure" warning may cause you to suffer a decrease in conversion rates as a result. (When that happens to me, I recommend Metamucil.)
  • Therefore, if eBay finds that you've got http: coding in your listing, they will hide it behind a button in the desktop view, telling users to click the button in order to see your description.
  • This doesn't affect mobile viewers, for unexplained reasons. (Possibly their view of your description is already hidden behind a button anyway.)
  • Therefore the best thing to do is ensure that you don't have http: coding in your listing. Something called the "i-ways tool" (here) can inspect your listings for you.
  • Therefore, when it comes to listing layout, the K.I.S.S. rule ("Keep It Simple, Stupid") is becoming more important all the time.

Wow.  @a_c_green, thanks for all that info.  I bookmarked your post and got that blue box that said Success Bookmarked!  

But where did it bookmark your post to???  


Your Profile/Settings/SUBSCRIPTIONS & NOTIFICATIONS/BookMarks


Thanks but  when I clicked that link /SUBSCRIPTIONS & NOTIFICATIONS/ I got a message that said: You do not have sufficient privileges for this resource or its parent to perform this action.

Click your browser's Back button to continue.

Message 36 of 112
latest reply

stronger browser security...


@rainbowcolorz wrote:

@pikabo-icu wrote:

@rainbowcolorz wrote:

@a_c_green wrote:

@pingpong517 wrote:

 

OK i'll admit.. I have no idea what this all means....can someone , in a nut shell, give me a version i can understand?


I can have a bash at it. Let me try to boil it down to a bulleted list...

  • About half the users out there are using Google Chrome, so eBay wants to play nice with it.
  • In this coming October, Google will be updating the browser to display a "Not Secure" message if the header is showing a web page that's either not using a secure connection (i.e. a web page beginning with "https:" rather than "http:"), or a secure connection that's got some insecure (http: ) code inside it. 
  • Web pages with addresses beginning with "https:" are secure (such as what you see for on-line banking and such)
  • Web pages with addresses beginning with "http:" are not secure. It's possible to download something nefarious via an http: connection that would be blocked by a secure https: connection.
  • It's possible to embed http: code within a page that itself is https: secure. That could be a Bad Thingâ„¢.
  • eBay recognizes that a user could upload http: code within their product descriptions that could cause trouble within eBay's https: web pages, such as links to external sources.
  • If that happens, the new Google Chrome will detect the lurking http: code, and flash a "Not Secure" warning across the top of the eBay viewer's screen.
  • eBay believes that this may cause undue alarm among potential eBay buyers, causing some of them to become dizzy or lightheaded, and have to go lie down for a while, thus preventing them from buying things. eBay says that the "Not Secure" warning may cause you to suffer a decrease in conversion rates as a result. (When that happens to me, I recommend Metamucil.)
  • Therefore, if eBay finds that you've got http: coding in your listing, they will hide it behind a button in the desktop view, telling users to click the button in order to see your description.
  • This doesn't affect mobile viewers, for unexplained reasons. (Possibly their view of your description is already hidden behind a button anyway.)
  • Therefore the best thing to do is ensure that you don't have http: coding in your listing. Something called the "i-ways tool" (here) can inspect your listings for you.
  • Therefore, when it comes to listing layout, the K.I.S.S. rule ("Keep It Simple, Stupid") is becoming more important all the time.

Wow.  @a_c_green, thanks for all that info.  I bookmarked your post and got that blue box that said Success Bookmarked!  

But where did it bookmark your post to???  


Your Profile/Settings/SUBSCRIPTIONS & NOTIFICATIONS/BookMarks


Thanks but  when I clicked that link /SUBSCRIPTIONS & NOTIFICATIONS/ I got a message that said: You do not have sufficient privileges for this resource or its parent to perform this action.

Click your browser's Back button to continue.


wow that stinks..."You do not have sufficient privileges" and they said call your parent...lol ..i just wonder what you have to do to have a place for a bookmark?... wahoo!

Message 37 of 112
latest reply

stronger browser security...

  • Web pages with addresses beginning with "http:" are not secure. It's possible to download something nefarious via an http: connection that would be blocked by a secure https: connection.

 

It's just as possible to download something nefarious via an https: connection.

 

_____________________________
"Nothing is obvious to the oblivious"
Message 38 of 112
latest reply

stronger browser security...

@sandyoutlet

 

I decided to just do a test of one item so I didn't have to give them my ID and Password. Everything checked out EXCEPT the ebaythumbs failed the test.

 

Will Ebay be fixing these before the deadline?

Message 39 of 112
latest reply

stronger browser security...


@readabouthorses wrote:

@pikabo-icu wrote:

This will give any buyer using Chrome a warning of an NON SECURE page..

That is distressing to many people. It's for the use of HTML coding. 

 

So in the post by Sweet Tea or the link here: http://community.ebay.com/t5/Announcements/Stronger-Browser-Security-Standards-Ahead/ba-p/27389922

There's a program/link to test your listings..

 

If they have HTML, you can edit it out and your buyers will not see the warning on Chrome.. 


So I'm guessing you are giving that company the same permission to access your listings/account that you do with a third party listing service? Because when I tried it they wanted my User ID and password to eBay.


Thanks for your comment. We partnered with i-ways to help identify listings that contain HTTP content. We asked them to use a sign-in token to ensure that your full listing compliance report was not public to anyone else. You can view single item IDs without signing in, but if you want to see your entire list of inventory, it requires a sign in. Thanks! 

Message 40 of 112
latest reply

stronger browser security...

I have no idea what any of this HTTP thing refers to. Ebay's info page does nothing to clarify. Why can't they just show some examples of what a HTTP listing that will be an issue looks like! There's absolutely no way I feel comfortable giving my user ID and password to some third party company. I can imagine that company becoming a hacking target, knowing they've obtained possibly millions of ebay user passwords. I don't believe that when you disable their permissions, your password would be removed. It's like those who think when you remove facebook posts they're gone forever...NOT!

So nice to know with it being hard enough to get sales here, it will become even harder! Ebay can't even figure out that one shouldn't be charged for bulk relists, and I'm supposed to believe they can handle this atrocity!
Message 41 of 112
latest reply

stronger browser security...


@sandyoutlet wrote:

@readabouthorses wrote:

@pikabo-icu wrote:

This will give any buyer using Chrome a warning of an NON SECURE page..

That is distressing to many people. It's for the use of HTML coding. 

 

So in the post by Sweet Tea or the link here: http://community.ebay.com/t5/Announcements/Stronger-Browser-Security-Standards-Ahead/ba-p/27389922

There's a program/link to test your listings..

 

If they have HTML, you can edit it out and your buyers will not see the warning on Chrome.. 


So I'm guessing you are giving that company the same permission to access your listings/account that you do with a third party listing service? Because when I tried it they wanted my User ID and password to eBay.


Thanks for your comment. We partnered with i-ways to help identify listings that contain HTTP content. We asked them to use a sign-in token to ensure that your full listing compliance report was not public to anyone else. You can view single item IDs without signing in, but if you want to see your entire list of inventory, it requires a sign in. Thanks! 


So why would they need the ebay login/password?

 

_____________________________
"Nothing is obvious to the oblivious"
Message 42 of 112
latest reply

stronger browser security...


@pingpong517 wrote:

http://community.ebay.com/t5/Announcements/Stronger-Browser-Security-Standards-Ahead/ba-p/27389922

 

OK i'll admit.. I have no idea what this all means....can someone , in a nut shell, give me a version i can understand?

 


after all the help and explaining.. I re tried the i-whatever tool in the announcement... i find that i am all secure HTTPS... so wow...BUT this mobil friendly checking thing..guess i gotta figure that out now...

and i use the seller hub..because i am ebay! lol

Message 43 of 112
latest reply

stronger browser security...


@bubbleman2010 wrote:

ping if you cookie cutter list I just checked the newest item you listed and there are no problems with it so this issue will have no bearing on you....


i see now how that tool works..thank you for the help...what a nutty thing in one announcement...

 

Message 44 of 112
latest reply

stronger browser security...


@sandyoutlet wrote:

@readabouthorses wrote:

@pikabo-icu wrote:

This will give any buyer using Chrome a warning of an NON SECURE page..

That is distressing to many people. It's for the use of HTML coding. 

 

So in the post by Sweet Tea or the link here: http://community.ebay.com/t5/Announcements/Stronger-Browser-Security-Standards-Ahead/ba-p/27389922

There's a program/link to test your listings..

 

If they have HTML, you can edit it out and your buyers will not see the warning on Chrome.. 


So I'm guessing you are giving that company the same permission to access your listings/account that you do with a third party listing service? Because when I tried it they wanted my User ID and password to eBay.


Thanks for your comment. We partnered with i-ways to help identify listings that contain HTTP content. We asked them to use a sign-in token to ensure that your full listing compliance report was not public to anyone else. You can view single item IDs without signing in, but if you want to see your entire list of inventory, it requires a sign in. Thanks! 


Wow, that sure would have been nice to know from the get-go!  So, this is apparently a SAFE thing to do -- for everyone using Chrome to list their items on eBay  - to give out their eBay USER ID and PASSWORD to i-ways.    Hmmm ....   I think I will view single items since I only have about 25-30 items listed.    And then just use the link (if I can find it in my bookmarks) to view all new listings.  

 

Geez ... what's next?  

Message 45 of 112
latest reply