Opera flags

Author: p | 2025-04-24

★★★★☆ (4.1 / 2559 reviews)

iggy azalea backgrounds

If not or if that doesn't work properly, in Opera, goto the URL opera://flags/PasswordImport, enable the flag, restart Opera, goto the URL On Desktop Opera GX and regular Opera, you can goto the URL opera://flags/password-import, enable the import flag, and restart Opera.

Download sleipnir browser 6.3.2

No flags in opera://flags - Opera forums

Opera. It is interesting to look at the test result on your system. andrew84 @Guest last edited by andrew84 @johnd78 with the enabled flag I have the same random result in O58 too, depending oh how many 'caches' were processed. A Former User @andrew84 last edited by @andrew84 Ok, got it. Then try to disable the flag opera://flags/#enable-webassembly-threads in the 68th Opera. To pass the test, this should be enough. andrew84 @Guest last edited by andrew84 @johnd78 said in Meltdown & Spectre the last Opera 68.0.3618.104 vulnerability:opera://flags/#enable-webassembly-threadsI disabled it, but in my case the result is still random (Portable 68.0.3618.104) A Former User @andrew84 last edited by @andrew84 For me with the opera://flags/#enable-webassembly-threads flag Disabled in the 68th it turns out like with the opera://flags/#shared-array-buffer flag Disabled in the 58th. andrew84 @Guest last edited by andrew84 @johnd78 I can't comment here, I also tried it in 69 (which is not portable) and all is the same..Maybe the test itself is not stable. And my processors can't be called as 'modern' like it is said in the blog post's explanation. donq @andrew84 last edited by donq @andrew84 said in Meltdown & Spectre the last Opera 68.0.3618.104 vulnerability:Maybe the test itself is not stable. And my processors can't be called as 'modern' like it is said in the blog post's explanation.The vulnerability itself is not 'stable' Code in test script is a bit over my understanding, but it could be unstable either.To read protected memory areas CPU cache is cleared, code is tricked to execute speculative read from protected area (which is discarded and thus not giving error - but data is already loaded into cache) and then some other memory addresses are read - read timing depends on cache containig specific data. Some information can be leaked even using somewhat random timing - I think this is exactly what you experience. leocg Moderator Volunteer @Guest last edited by @johnd78 That flag used to make sense three years ago, when the post was published. leocg Moderator Volunteer @Guest last edited by @johnd78 I have that flag enabled (by default) here and the test says that Opera i snot vulnerable. A Former User @andrew84 last edited by @andrew84 Sorry, my mistake, I forgot something. Try to disable the flag opera://flags/#enable-webassembly-threads and start the browser with the key --disable-features=SharedArrayBuffer. Then it should work. Checked in the 68th and 69th Opera. anastasia-mx @Guest last edited by @johnd78 I used the "WebAssembly threads support" = "disabled" flag and started the program opera with the key --disable-features=SharedArrayBuffer as a result, the problem is resolved and the browser is no longer vulnerable.can you explain what these parameters are and why they were enabled if this leads to a. If not or if that doesn't work properly, in Opera, goto the URL opera://flags/PasswordImport, enable the flag, restart Opera, goto the URL On Desktop Opera GX and regular Opera, you can goto the URL opera://flags/password-import, enable the import flag, and restart Opera. In Chromium-based Opera, settings are at the URL opera://settings and experimental flags (Chromium and Opera-specific ones) are at the URL opera://flags. Sections in settings have Opera removed the flag because the feature was unfinished and the flag was never enabled by default. I've mentioned to Opera that a lot of users were using the flag as a @mitchfr opera://flags/temporary-unexpire-flags-m92 is available from Chromium 93, that is the base for Opera 79. On precision timing in javascript and mitigation was done by randomizing JS timing errors - all such behavior is seated deep inside JS engine and should not be related to broken profile. Well, there likely are some JS flags, which may alter engine behavior - and you may search or ask on chrome/chromium forums, have they changed anything related to spectre or JS timings.I have not heard about (widespread) real-word exploits, based on spectre (or meltdown). I would think such kind of vulnerabilites can be used for targeted attaks, where every bit of information can be valuable; for generic attakcs (to take PC over) this is a bit hard and unpredictable to use - of course I may be wrong here. leocg Moderator Volunteer @Guest last edited by @johnd78 You posted the link to the blog post and not to the comment. andrew84 @leocg last edited by @leocg so read the blog post, there's an explanation. And there's 0 comments (because all the 'disqus' comments were removed) A Former User @leocg last edited by @leocg I meant the developers' blog comments on this issue. As far as I remember, when a problem with this vulnerability appeared, the developers forcedly disabled opera://flags/#shared-array-buffer flag. Now this flag is gone. A Former User @andrew84 last edited by A Former User @andrew84 Please, try enabling the flag opera://flags/#shared-array-buffer in the 58th Opera. It is interesting to look at the test result on your system. andrew84 @Guest last edited by andrew84 @johnd78 with the enabled flag I have the same random result in O58 too, depending oh how many 'caches' were processed. A Former User @andrew84 last edited by @andrew84 Ok, got it. Then try to disable the flag opera://flags/#enable-webassembly-threads in the 68th Opera. To pass the test, this should be enough. andrew84 @Guest last

Comments

User9012

Opera. It is interesting to look at the test result on your system. andrew84 @Guest last edited by andrew84 @johnd78 with the enabled flag I have the same random result in O58 too, depending oh how many 'caches' were processed. A Former User @andrew84 last edited by @andrew84 Ok, got it. Then try to disable the flag opera://flags/#enable-webassembly-threads in the 68th Opera. To pass the test, this should be enough. andrew84 @Guest last edited by andrew84 @johnd78 said in Meltdown & Spectre the last Opera 68.0.3618.104 vulnerability:opera://flags/#enable-webassembly-threadsI disabled it, but in my case the result is still random (Portable 68.0.3618.104) A Former User @andrew84 last edited by @andrew84 For me with the opera://flags/#enable-webassembly-threads flag Disabled in the 68th it turns out like with the opera://flags/#shared-array-buffer flag Disabled in the 58th. andrew84 @Guest last edited by andrew84 @johnd78 I can't comment here, I also tried it in 69 (which is not portable) and all is the same..Maybe the test itself is not stable. And my processors can't be called as 'modern' like it is said in the blog post's explanation. donq @andrew84 last edited by donq @andrew84 said in Meltdown & Spectre the last Opera 68.0.3618.104 vulnerability:Maybe the test itself is not stable. And my processors can't be called as 'modern' like it is said in the blog post's explanation.The vulnerability itself is not 'stable' Code in test script is a bit over my understanding, but it could be unstable either.To read protected memory areas CPU cache is cleared, code is tricked to execute speculative read from protected area (which is discarded and thus not giving error - but data is already loaded into cache) and then some other memory addresses are read - read timing depends on cache containig specific data. Some information can be leaked even using somewhat random timing - I think this is exactly what you experience. leocg Moderator Volunteer @Guest last edited by @johnd78 That flag used to make sense three years ago, when the post was published. leocg Moderator Volunteer @Guest last edited by @johnd78 I have that flag enabled (by default) here and the test says that Opera i snot vulnerable. A Former User @andrew84 last edited by @andrew84 Sorry, my mistake, I forgot something. Try to disable the flag opera://flags/#enable-webassembly-threads and start the browser with the key --disable-features=SharedArrayBuffer. Then it should work. Checked in the 68th and 69th Opera. anastasia-mx @Guest last edited by @johnd78 I used the "WebAssembly threads support" = "disabled" flag and started the program opera with the key --disable-features=SharedArrayBuffer as a result, the problem is resolved and the browser is no longer vulnerable.can you explain what these parameters are and why they were enabled if this leads to a

2025-03-31
User8567

On precision timing in javascript and mitigation was done by randomizing JS timing errors - all such behavior is seated deep inside JS engine and should not be related to broken profile. Well, there likely are some JS flags, which may alter engine behavior - and you may search or ask on chrome/chromium forums, have they changed anything related to spectre or JS timings.I have not heard about (widespread) real-word exploits, based on spectre (or meltdown). I would think such kind of vulnerabilites can be used for targeted attaks, where every bit of information can be valuable; for generic attakcs (to take PC over) this is a bit hard and unpredictable to use - of course I may be wrong here. leocg Moderator Volunteer @Guest last edited by @johnd78 You posted the link to the blog post and not to the comment. andrew84 @leocg last edited by @leocg so read the blog post, there's an explanation. And there's 0 comments (because all the 'disqus' comments were removed) A Former User @leocg last edited by @leocg I meant the developers' blog comments on this issue. As far as I remember, when a problem with this vulnerability appeared, the developers forcedly disabled opera://flags/#shared-array-buffer flag. Now this flag is gone. A Former User @andrew84 last edited by A Former User @andrew84 Please, try enabling the flag opera://flags/#shared-array-buffer in the 58th Opera. It is interesting to look at the test result on your system. andrew84 @Guest last edited by andrew84 @johnd78 with the enabled flag I have the same random result in O58 too, depending oh how many 'caches' were processed. A Former User @andrew84 last edited by @andrew84 Ok, got it. Then try to disable the flag opera://flags/#enable-webassembly-threads in the 68th Opera. To pass the test, this should be enough. andrew84 @Guest last

2025-04-24
User8934

Do more on the web, with a fast and secure browser! Download Opera browser with: built-in ad blocker battery saver free VPN Download Opera This topic has been deleted. Only users with topic management privileges can see it. last edited by @leocg I've tried using both the flags and the normal import function but it only seems to import my bookmarks and history from chrome. I haven't used any external programs. I've used both the flags and the--enable-features=PasswordImportway of trying to activate the feature but to no avail. I have the passwords on hand as a csv file but I cannot see an option to import them that way. leocg Moderator Volunteer @Guest last edited by @daschmitt I've enabled the flag and could see the option at opera://settings/passwords saja-369 @Guest last edited by @daschmitt @yo19 Go to opera://flags and type "Password import" in search and then click enable Bacon4Life last edited by For some reason, none of these are working for me. I still am unable to import the passwords. Natx @leocg last edited by @leocg thanks, it helped a lot megakrocks @leocg last edited by @leocg Thanks this was very helpful! CG-Locks last edited by worked thank you Toongamer1337 last edited by I cannot find the option to turn on "Password import" could someone help me? leocg Moderator Volunteer @Toongamer1337 last edited by @toongamer1337 Enable the flag to unexpire m92 flags. Kels554 @leocg last edited by @leocg Dude thank you so much Bus last edited by I want import password in opera,but i have vcs file and i dont`t see button "Import" SlyCopper9821 @leocg last edited by @leocg So I do not see the 3 dots anywhere in the password section and I did enable the "unexpire m92" flag but if there are more I don't see those. Am

2025-04-02

Add Comment