+ Reply to Thread
Page 1 of 5 1 5 LastLast
Results 1 to 20 of 90

Thread: [FIXED] Browser warnings that "Avalon is insecure"

  1. Link to Post #1
    United States Avalon Member ThePythonicCow's Avatar
    Join Date
    4th January 2011
    Location
    North Texas
    Language
    English
    Age
    73
    Posts
    27,903
    Thanks
    29,143
    Thanked 131,404 times in 20,808 posts

    Default [FIXED] Browser warnings that "Avalon is insecure"

    Members of this good forum are beginning to report to me that they are seeing a warning in their browser's address bar that ProjectAvalon.net is insecure.

    Chrome is either labeling our URL "Not secure" in the address bar, or starting to show this padlock:
    Firefox is starting to show this padlock:
    Not everyone will be seeing this "Insecure Padlock" yet. Chrome and Firefox are rolling out the change, over perhaps the next week or two.

    Presently Chrome and Firefox are only warning about sites (such as ProjectAvalon.net) that both (1) use HTTP, not HTTPS, and (2) have login or password forms displayed on the page (such as the User Name and Password "Log in" fields at the top of some PojectAvalon.net pages).

    Eventually, in some future month, Chrome and Firefox will warn about all HTTP webpages.

    I don't have an easy answer for this. When you login to ProjectAvalon.net, your password is encoded so that it cannot be easily seen in plain text by someone snooping your packets. But (1) Chrome and Firefox don't know this, and (2) the password encoding we use is not the sort of military grade encryption that you'd want to bet your life on.

    If it were easy to adapt our ProjectAvalon.net forum to use encrypted HTTPS, rather than plain text HTTP, we'd do that. The Security Certificates needed for this have been free for a while now, from https://letsencrypt.org/ However the way the forum software works on our server, this would not be an easy change.

    These new warnings, coming soon to any Chrome or Firefox browser near you, don't mean that the ProjectAvalon.net site is any less secure than it was last week. Rather it means that the standards for what Chrome and Firefox consider secure are being raised.

    If you see such a Security Padlock warning from your bank website, then you should worry. But ProjectAvalon.net is not involved with such highly sensitive data.

    Here are some articles that discuss this new security warning from Chrome and Firefox in more detail:
    I described my own tin-foil-hat conspiracy theory about this a few months ago, in the thread How the Elite Bastards will control the Wild Wild Web.

    Let us know if you have any further questions, comments, insights or information. Thanks!
    Last edited by ThePythonicCow; 29th January 2017 at 05:46.
    My (sometimes rather dormant) blog: theMooster.net

  2. The Following 55 Users Say Thank You to ThePythonicCow For This Post:

    airaspect (29th January 2017), Bill Ryan (28th January 2017), Bluegreen (29th January 2017), BMJ (29th January 2017), boja (28th January 2017), bojancan (19th March 2017), ceetee9 (29th January 2017), David Trd1 (20th June 2018), DebJoy (28th January 2017), Debra (28th January 2017), DeDukshyn (28th January 2017), DNA (30th January 2017), dynamo (29th January 2017), enigma3 (28th January 2017), Ewan (29th January 2017), ExomatrixTV (13th December 2020), Fellow Aspirant (28th January 2017), fourty-two (29th January 2017), Foxie Loxie (28th January 2017), gaiagirl (29th January 2017), Gillian (28th January 2017), Hervé (28th January 2017), ichingcarpenter (28th December 2018), Inversion (28th January 2017), Ioneo (28th January 2017), Ivanhoe (29th January 2017), Ivy23 (21st June 2018), Jean-Marie (28th January 2017), Jill (28th December 2018), joeecho (28th January 2017), Johnny (19th March 2017), Joseph McAree (16th December 2020), JRS (29th January 2017), justntime2learn (30th December 2018), Karen (Geophyz) (15th December 2020), KiwiElf (28th January 2017), Lifebringer (29th January 2017), Lost N Found (28th January 2017), Michelle Marie (29th January 2017), mojo (20th June 2018), naste.de.lumina (28th January 2017), Omni (21st June 2018), PathWalker (19th March 2017), penn (28th January 2017), RedSun88 (29th January 2017), Satori (29th January 2017), Sophocles (28th January 2017), Spellbound (29th January 2017), sunflower (30th January 2017), Timreh (30th January 2017), toppy (29th January 2017), TrumanCash (28th January 2017), uzn (28th January 2017), Watching from Cyprus (21st April 2018), wnlight (29th January 2017)

  3. Link to Post #2
    Canada Avalon Member Gillian's Avatar
    Join Date
    31st October 2016
    Location
    British Columbia
    Age
    66
    Posts
    121
    Thanks
    404
    Thanked 498 times in 109 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    I access Project Avalon from Opera with DuckDuckGo, but will watch for warnings from them, too, and will report here. I do tend to use Opera's speed dial page so probably no DuckDuckGo protection. I have Startpage on Chrome, but will watch out for problems there.

  4. The Following 8 Users Say Thank You to Gillian For This Post:

    Debra (28th January 2017), Foxie Loxie (28th January 2017), Inversion (28th January 2017), Johnny (19th March 2017), Karen (Geophyz) (15th December 2020), Lost N Found (28th January 2017), Michelle Marie (29th January 2017), ThePythonicCow (28th January 2017)

  5. Link to Post #3
    United States Avalon Retired Member
    Join Date
    18th September 2016
    Posts
    1,062
    Thanks
    2,208
    Thanked 5,360 times in 1,011 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    Paul

    What about Safari on Ipads?
    My desktop connection seems ok but since the beginning of this week I cannot access from my Ipad anymore. I get message that there was trouble loading the page so it was reloaded but it keeps doing that. It's not the ipad as I can get to other sites as usual.
    Thx

  6. The Following 3 Users Say Thank You to Helene West For This Post:

    Johnny (19th March 2017), Karen (Geophyz) (15th December 2020), Michelle Marie (29th January 2017)

  7. Link to Post #4
    United States Avalon Member ThePythonicCow's Avatar
    Join Date
    4th January 2011
    Location
    North Texas
    Language
    English
    Age
    73
    Posts
    27,903
    Thanks
    29,143
    Thanked 131,404 times in 20,808 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    Quote Posted by Helene West (here)
    Paul

    What about Safari on Ipads?
    My desktop connection seems ok but since the beginning of this week I cannot access from my Ipad anymore. I get message that there was trouble loading the page so it was reloaded but it keeps doing that. It's not the ipad as I can get to other sites as usual.
    Thx
    I have no idea what's going on there ... sorry .

    I don't have an iPad, I don't run Safari, I haven't heard of others having similar troubles, and I doubt (but don't know) that your troubles are related to this new Firefox and Chrome warning.
    My (sometimes rather dormant) blog: theMooster.net

  8. The Following 4 Users Say Thank You to ThePythonicCow For This Post:

    Bill Ryan (29th January 2017), Johnny (19th March 2017), Karen (Geophyz) (15th December 2020), Lifebringer (29th January 2017)

  9. Link to Post #5
    Avalon Member Lifebringer's Avatar
    Join Date
    18th December 2010
    Posts
    4,393
    Thanks
    6,806
    Thanked 11,752 times in 3,536 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    Its starting and perhaps our peeps will adapt w/ebonics again, fershizzle.
    Ebonics evolve from generation to generation between age groups. Grapevines will be grown.

  10. The Following User Says Thank You to Lifebringer For This Post:

    Johnny (19th March 2017)

  11. Link to Post #6
    Avalon Member Lifebringer's Avatar
    Join Date
    18th December 2010
    Posts
    4,393
    Thanks
    6,806
    Thanked 11,752 times in 3,536 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    Careful, I've suspected a few alphabet soup here for weeks now. Shame they are chasing rainbows instead of real terrorist. smh
    They are after ideas, solutions, inventions or up to date seeking materials here. Maybe to mimic, perhaps just to patent.

    "write it down oldschool and date all inventions, careful about posting perhaps pm's on them, between skilled members of all trades.
    Holistic medicines w/no side effects are gonna increase 500% when people treat their bodies better.
    My avaast told me passwords are public, but I don't have the lootski to purchase password protection. Its their walls being penetrated, shouldn't they protect the customer?
    Last edited by Lifebringer; 29th January 2017 at 12:29.

  12. The Following User Says Thank You to Lifebringer For This Post:

    Johnny (19th March 2017)

  13. Link to Post #7
    Australia Avalon Member BMJ's Avatar
    Join Date
    4th May 2010
    Posts
    1,479
    Thanks
    39,774
    Thanked 7,614 times in 1,323 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    Had an auto update of the latest firefox software less than a week ago. Since, I have had no warnings or issues accessing Project Avalon here in Australia.

  14. The Following 5 Users Say Thank You to BMJ For This Post:

    Bill Ryan (29th January 2017), Foxie Loxie (29th January 2017), Hervé (29th January 2017), Johnny (19th March 2017), Karen (Geophyz) (15th December 2020)

  15. Link to Post #8
    Unsubscribed
    Join Date
    23rd June 2013
    Location
    North America
    Age
    69
    Posts
    6,884
    Thanks
    12,723
    Thanked 29,293 times in 6,140 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    Quote Posted by Paul (here)
    Members of this good forum are beginning to report to me that they are seeing a warning in their browser's address bar that ProjectAvalon.net is insecure.

    Chrome is either labeling our URL "Not secure" in the address bar, or starting to show this padlock:
    Firefox is starting to show this padlock:
    Not everyone will be seeing this "Insecure Padlock" yet. Chrome and Firefox are rolling out the change, over perhaps the next week or two.

    Presently Chrome and Firefox are only warning about sites (such as ProjectAvalon.net) that both (1) use HTTP, not HTTPS, and (2) have login or password forms displayed on the page (such as the User Name and Password "Log in" fields at the top of some PojectAvalon.net pages).

    Eventually, in some future month, Chrome and Firefox will warn about all HTTP webpages.

    I don't have an easy answer for this. When you login to ProjectAvalon.net, your password is encoded so that it cannot be easily seen in plain text by someone snooping your packets. But (1) Chrome and Firefox don't know this, and (2) the password encoding we use is not the sort of military grade encryption that you'd want to bet your life on.

    If it were easy to adapt our ProjectAvalon.net forum to use encrypted HTTPS, rather than plain text HTTP, we'd do that. The Security Certificates needed for this have been free for a while now, from https://letsencrypt.org/ However the way the forum software works on our server, this would not be an easy change.

    These new warnings, coming soon to any Chrome or Firefox browser near you, don't mean that the ProjectAvalon.net site is any less secure than it was last week. Rather it means that the standards for what Chrome and Firefox consider secure are being raised.

    If you see such a Security Padlock warning from your bank website, then you should worry. But ProjectAvalon.net is not involved with such highly sensitive data.

    Here are some articles that discuss this new security warning from Chrome and Firefox in more detail:
    I described my own tin-foil-hat conspiracy theory about this a few months ago, in the thread How the Elite Bastards will control the Wild Wild Web.

    Let us know if you have any further questions, comments, insights or information. Thanks!
    ToT has gone SSL

    http://www.fastcomet.com/tutorials/v...-configuration talks about how to setup vBulletin 4 for SSL

    also mentioned: https://clients.urljet.com/knowledge...tin-Forum.html

    some other data from their forum (which is SSL https) - see https://www.vbulletin.com/forum/foru...l-in-vbulletin

    Quote 1) Apply an SSL certificate to your domain and hosting package.
    2) Create an htaccess file to redirect http:// requests to https:// requests in your vBulletin forum directory. If you do not know how to do this, it falls under your Hosting Provider's Support.
    3) Update the Forum URL under Settings -> Options -> Site Name / URL / Contact Details to reflect https:// instead of http://

    You're forums are now running under SSL.
    There is a mention about icons, on setting such.. etc.

    Gee if ToT did it...

  16. Link to Post #9
    United States Avalon Member ThePythonicCow's Avatar
    Join Date
    4th January 2011
    Location
    North Texas
    Language
    English
    Age
    73
    Posts
    27,903
    Thanks
    29,143
    Thanked 131,404 times in 20,808 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    Quote Posted by Bob (here)
    Gee if ToT did it...
    ToT is running a new version of vBulletin, with fewer customizations, than Avalon.
    My (sometimes rather dormant) blog: theMooster.net

  17. The Following 3 Users Say Thank You to ThePythonicCow For This Post:

    Bob (19th March 2017), Johnny (19th March 2017), Karen (Geophyz) (15th December 2020)

  18. Link to Post #10
    Unsubscribed
    Join Date
    23rd June 2013
    Location
    North America
    Age
    69
    Posts
    6,884
    Thanks
    12,723
    Thanked 29,293 times in 6,140 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    Quote Posted by Paul (here)
    Quote Posted by Bob (here)
    Gee if ToT did it...
    ToT is running a new version of vBulletin, with fewer customizations, than Avalon.
    Maybe it is time to upgrade the software? Just askin.. And vBulletin it's own forum itself is SSL.. supposedly they have some tech sysop there at vBulletin who will help one go SSL ...

    vBulletin's note page for conversion: https://www.vbulletin.com/forum/arti...forum-to-https

    Force SSL suggestion from their forum:
    Issue - "we have mixed links, some are http:"
    Forum response ->

    "You can use a rewrite directive in your .htaccess file to convert incoming links to SSL. Something like this":

    Quote Code:
    ## Begin - Enforce SSL
    #
    RewriteCond %{SERVER_PORT} 80
    RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
    #
    ## End - Enforce SSL
    just askin - other forums are going for security and dealing with the issues in the OP #1
    Last edited by Bob; 19th March 2017 at 00:57.

  19. Link to Post #11
    United States Avalon Member ThePythonicCow's Avatar
    Join Date
    4th January 2011
    Location
    North Texas
    Language
    English
    Age
    73
    Posts
    27,903
    Thanks
    29,143
    Thanked 131,404 times in 20,808 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    .
    Google will be taking the next step in its mission to convert the web to https, as posted at security.googleblog.com, then reported here at venturebeat.com, which report was reposted at slashdot.org:

    ========
    Chrome will start marking HTTP sites in Incognito mode as non-secure in October 2017
    Emil Protalinski@EPro April 27, 2017 10:40 AM

    Google today announced the second step in its plan to mark all HTTP sites as non-secure in Chrome. Starting in October 2017, Chrome will mark HTTP sites with entered data and HTTP sites in Incognito mode as non-secure.

    HTTPS is a more secure version of the HTTP protocol used on the internet to connect users to websites. Secure connections are widely considered a necessary measure to decrease the risk of users being vulnerable to content injection (which can result in eavesdropping, man-in-the-middle attacks, and other data modification). Data is kept secure from third parties, and users can be more confident they are communicating with the correct website.

    With the release of Chrome 56 in January 2017, Google’s browser started marking HTTP pages that collect passwords or credit cards as “Not Secure” in the address bar. Since then, Google has seen a 23 percent reduction in the fraction of navigations to HTTP pages with password or credit card forms on Chrome for desktop. Chrome 62 (we’re currently on Chrome 58) will take this to the next level.

    Passwords and credit cards are naturally the most important data to keep private, but ideally no data that users type into websites should be accessible to others on the network. Chrome 62 will thus show the “Not secure” warning when users type data into HTTP sites.

    As for browsing in Incognito mode, Google believes users have “increased expectations of privacy.” But in this mode, HTTP browsing is potentially visible to others on the network just like in normal mode. Chrome 62 will thus warn users when visiting an HTTP page in Incognito mode.

    Google’s reasoning for highlighting HTTP sites as non-secure remains the same:
    Quote When you load a website over HTTP, someone else on the network can look at or modify the site before it gets to you. Studies show that users do not perceive the lack of a “secure” icon as a warning, but also that users become blind to warnings that occur too frequently. Our plan to label HTTP sites more clearly and accurately as non-secure will take place in gradual steps, based on increasingly stringent criteria.
    This is Google’s way of pushing the web towards HTTPS. As of November 2016, more than half of Chrome desktop page loads are served over HTTPS, but the company wants to push that as close to 100 percent as possible.

    Google still isn’t sharing exactly when Chrome will label all HTTP pages as non-secure. When it does, the HTTP security indicator will be changed to the red triangle that is currently used for broken HTTPS pages.
    ========

    As I (Paul) have posted in How the Elite Bastards will control the Wild Wild Web, I am developing serious doubts about this push by Google to convert the Web to https:
    1. Any web server relying only on https could be shutdown by the domain name registrars. These registrars are being increasingly made to comply to Google's mandates, so essentially that means that Google, long a suspected CIA partner, could shutdown https sites that it deems "bad".
    2. Any web user (you or me or whomever) could be locked out of all of the https dependent web, as I reported in detail in this post, when a misconfiguration of my own PC's https security certificates locked me out of all https websites. Google's and Microsoft's increasingly aggressive autoupdates would enable them to push a deliberate block to any selected user(s) they wanted to.

    This trend toward https worries me.
    My (sometimes rather dormant) blog: theMooster.net

  20. The Following 8 Users Say Thank You to ThePythonicCow For This Post:

    Bill Ryan (21st April 2018), BMJ (29th April 2017), Ewan (28th April 2017), Foxie Loxie (28th April 2017), Hervé (28th April 2017), KiwiElf (20th June 2018), Shannon (28th April 2017), Star Tsar (28th April 2017)

  21. Link to Post #12
    United States Avalon Member ThePythonicCow's Avatar
    Join Date
    4th January 2011
    Location
    North Texas
    Language
    English
    Age
    73
    Posts
    27,903
    Thanks
    29,143
    Thanked 131,404 times in 20,808 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    Now, not just Firefox and Chrome, but also Apple's browser, Safari, is increasing its "insecure" warnings for http websites:
    Starting in iOS 11.3 and macOS 10.13.4, Safari shows a "Website Not Secure" warning if a website that you're visiting isn't secure.
    My (sometimes rather dormant) blog: theMooster.net

  22. The Following 7 Users Say Thank You to ThePythonicCow For This Post:

    avid (21st April 2018), Bill Ryan (21st April 2018), dynamo (22nd April 2018), Foxie Loxie (20th June 2018), Franny (22nd April 2018), genevieve (22nd April 2018), KiwiElf (20th June 2018)

  23. Link to Post #13
    United States Avalon Member ThePythonicCow's Avatar
    Join Date
    4th January 2011
    Location
    North Texas
    Language
    English
    Age
    73
    Posts
    27,903
    Thanks
    29,143
    Thanked 131,404 times in 20,808 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    .
    Apparently the warning to Chrome browser users that http://projectavalon.net is insecure will start with Version 68 of Chrome, which is scheduled to be released next month, July 2018.

    I just now received this email from Google informing me of this:
    Quote
    Chrome will start showing security warnings on http://projectavalon.net/

    To owner of http://projectavalon.net/,

    On July 2018, Chrome (version 68) will start showing "NOT SECURE" warnings for all HTTP pages it opens.

    To prevent a “Not Secure” warning from appearing when Chrome users visit your site, you must serve your site over HTTPS. Migrate your site to HTTPS to avoid triggering the new warning on your site and to help protect users' data.
    This April 2018 article in PC World, Google's Chrome will soon start warning you more about HTTP pages, describes how this might look to the user of Project Avalon (or any other website using http to interact with users).

    According to this PC World article, the "Not secure" warning will appear in the browser's Address Bar, like this:
    We have no plans to migrate Project Avalon to https.

    I would strongly recommend that members of Project Avalon do NOT use the same password on ProjectAvalon.net as they use on a security sensitive site such as for
    • bank accounts,
    • email accounts,
    • shopping sites,
    • credit ranking sites,
    • medical providers,
    • government sites, or
    • any other site that knows much about you.
    Bank accounts have your money, email accounts can be used to reset passwords on bank accounts, and shopping sites have your credit card information. Medical, credit and government sites often know "too much" about you, that can be used in ways you don't want.

    When you log into ProjectAvalon.net, your password is obfuscated while being sent over the Internet, but this obfuscation does not use strong cryptography.

    In general:
    1. don't use the same password on multiple different websites, especially not on websites that know "too much" about you, and
    2. don't use easy to guess passwords (almost any password you can remember risks being "easy to guess" by computer programs that can try thousands or millions of possibilities per second.)
    Rather I recommend using a password manager, such as LastPass.
    My (sometimes rather dormant) blog: theMooster.net

  24. The Following 7 Users Say Thank You to ThePythonicCow For This Post:

    Foxie Loxie (20th June 2018), Hervé (20th June 2018), KiwiElf (20th June 2018), onawah (20th June 2018), onevoice (21st June 2018), RunningDeer (20th June 2018), Valerie Villars (20th June 2018)

  25. Link to Post #14
    United States Avalon Member onawah's Avatar
    Join Date
    28th March 2010
    Language
    English
    Posts
    15,735
    Thanks
    36,811
    Thanked 74,963 times in 14,211 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    I just tried signing up for the the free version of LastPass, but it appears it won't work since I am using Chrome.
    Quote Posted by Paul (here)
    Rather I recommend using a password manager, such as LastPass.
    Each breath a gift...
    _____________

  26. Link to Post #15
    United States Avalon Member ThePythonicCow's Avatar
    Join Date
    4th January 2011
    Location
    North Texas
    Language
    English
    Age
    73
    Posts
    27,903
    Thanks
    29,143
    Thanked 131,404 times in 20,808 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    Quote Posted by onawah (here)
    I just tried signing up for the the free version of LastPass, but it appears it won't work since I am using Chrome.
    It works for me, on Chrome.

    I just went to the LastPass website in my Chrome browser, clicked on the red Get LastPass Free button, upper right corner of that page, agreed to the "Add Extension" inquiry that popped up, and could now setup a free LastPass account in that browser, if I wanted to.

    I did not complete that LastPass signup, as I am using KeePassXC, rather than LastPass, but I'd recommend KeePassXC more for computer geeks, as it's still under more rapid development.

    Where did you effort to sign up for LastPass fail, onawah?
    My (sometimes rather dormant) blog: theMooster.net

  27. The Following User Says Thank You to ThePythonicCow For This Post:

    onawah (20th June 2018)

  28. Link to Post #16
    United States Avalon Member onawah's Avatar
    Join Date
    28th March 2010
    Language
    English
    Posts
    15,735
    Thanks
    36,811
    Thanked 74,963 times in 14,211 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    I clicked on the link you provided in your post here: https://projectavalon.net/forum4/show...=1#post1230855 which opened this page: https://www.lastpass.com/?lpInstall&installExperience=1 which opened a box for installing it, but when I tried to install it, I got the message that it wouldn't work in Chrome.

    Quote Posted by Paul (here)
    Quote Posted by onawah (here)
    I just tried signing up for the the free version of LastPass, but it appears it won't work since I am using Chrome.
    It works for me, on Chrome.

    I just went to the LastPass website in my Chrome browser, clicked on the red Get LastPass Free button, upper right corner of that page, agreed to the "Add Extension" inquiry that popped up, and could now setup a free LastPass account in that browser, if I wanted to.

    I did not complete that LastPass signup, as I am using KeePassXC, rather than LastPass, but I'd recommend KeePassXC more for computer geeks, as it's still under more rapid development.

    Where did you effort to sign up for LastPass fail, onawah?
    Each breath a gift...
    _____________

  29. Link to Post #17
    Avalon Member norman's Avatar
    Join Date
    25th March 2010
    Location
    too close to the hot air exhaust
    Age
    65
    Posts
    6,164
    Thanks
    8,532
    Thanked 33,334 times in 5,479 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    But, for the record, I've revently been experimenting with using an ancient Windows OS, Windows 98SE.

    I managed to get version 9.nn of Opera browser to work with it. Firefox won't play nice at all beyond version 2.nn.

    Anyway, long story short, after finding that websites don't display much content or any of the clever stuff like non-bot verification boxes etc, I discovered that the Avalon forum plays really nice with such a basic setup. The 'human test' before allowing a non logged in user to do a search doesn't show anything I can click on, tho'.

    I haven't pushed my luck and actually tried to make a post using Opera on Win98, but I can certainly navigate around ok and read anything and everything.

    So, Paul, you are certainly doing something right, in my book. . .
    ..................................................my first language is TYPO..............................................

  30. Link to Post #18
    United States Avalon Member onawah's Avatar
    Join Date
    28th March 2010
    Language
    English
    Posts
    15,735
    Thanks
    36,811
    Thanked 74,963 times in 14,211 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    So I tried opening LastPass in Chrome and clicked on the button for Free LastPass, which opened this window: https://www.lastpass.com/?lpInstall&installExperience=1 where it says:
    "You're almost done.
    Next, click the LastPass browser button above to create your account or log in."
    But the button doesn't work at all.

    Add to browser
    Quote Posted by Paul (here)
    Quote Posted by onawah (here)
    I just tried signing up for the the free version of LastPass, but it appears it won't work since I am using Chrome.
    It works for me, on Chrome.

    I just went to the LastPass website in my Chrome browser, clicked on the red Get LastPass Free button, upper right corner of that page, agreed to the "Add Extension" inquiry that popped up, and could now setup a free LastPass account in that browser, if I wanted to.

    I did not complete that LastPass signup, as I am using KeePassXC, rather than LastPass, but I'd recommend KeePassXC more for computer geeks, as it's still under more rapid development.

    Where did you effort to sign up for LastPass fail, onawah?
    Each breath a gift...
    _____________

  31. Link to Post #19
    United States Avalon Member ThePythonicCow's Avatar
    Join Date
    4th January 2011
    Location
    North Texas
    Language
    English
    Age
    73
    Posts
    27,903
    Thanks
    29,143
    Thanked 131,404 times in 20,808 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    Quote Posted by onawah (here)
    I got the message that it wouldn't work in Chrome.
    Hmmm ... strange.

    Ah - perhaps this is Google forcing you to use the Chrome Web Store.

    Try clicking on the LastPass icon (one of the top listed apps) on the Chrome Web Store. website: https://chrome.google.com/webstore/category/extensions

    Maybe Chrome will let you install the app that way.
    My (sometimes rather dormant) blog: theMooster.net

  32. Link to Post #20
    United States Avalon Member ThePythonicCow's Avatar
    Join Date
    4th January 2011
    Location
    North Texas
    Language
    English
    Age
    73
    Posts
    27,903
    Thanks
    29,143
    Thanked 131,404 times in 20,808 posts

    Default Re: [FIXED] Browser warnings that "Avalon is insecure"

    Quote Posted by onawah (here)
    Next, click the LastPass browser button above to create your account or log in."
    But the button doesn't work at all.
    Double strange ...

    LastPass is one of the biggest, most heavily used, add-on's, available in all the major browsers.

    Since I am running Chromium (the open source little brother of Chrome) rather than Chrome, and since I am on Linux, rather than on Windows or Mac, and since I have geeky fingers (like a "green thumb" but for bits rather than green things), I am not surprised that I cannot reproduce the problem you're seeing.
    My (sometimes rather dormant) blog: theMooster.net

  33. The Following User Says Thank You to ThePythonicCow For This Post:

    onawah (21st June 2018)

+ Reply to Thread
Page 1 of 5 1 5 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts