<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/seb/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/seb/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 05 Jul 2021 11:34:53 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/seb/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>IMPORTANT: SourceForge now read-only, support &amp; discussion moved to GitHub!</title><link>https://sourceforge.net/p/seb/feature-requests/72/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;&lt;strong&gt;IMPORTANT: Please note that we no longer maintain bug reports, discussions and support requests on SourceForge!&lt;/strong&gt; The forums will remain online as reference, but posting new content is not possible anymore. Please use the dedicated repositories on &lt;a class="" href="https://github.com/SafeExamBrowser" rel="nofollow"&gt;GitHub&lt;/a&gt; to report a bug, request a new feature, discuss topics related to SEB or ask for help:&lt;/p&gt;
&lt;h5 id="seb-for-windows"&gt;SEB for Windows&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;Bug reports &amp;amp; feature requests: &lt;a href="https://github.com/SafeExamBrowser/seb-win-refactoring/issues" rel="nofollow"&gt;https://github.com/SafeExamBrowser/seb-win-refactoring/issues&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Discussion &amp;amp; support: &lt;a href="https://github.com/SafeExamBrowser/seb-win-refactoring/discussions" rel="nofollow"&gt;https://github.com/SafeExamBrowser/seb-win-refactoring/discussions&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h5 id="seb-for-macosios"&gt;SEB for macOS/iOS&lt;/h5&gt;
&lt;ul&gt;
&lt;li&gt;Bug reports &amp;amp; feature requests: &lt;a href="https://github.com/SafeExamBrowser/seb-mac/issues" rel="nofollow"&gt;https://github.com/SafeExamBrowser/seb-mac/issues&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Discussion &amp;amp; support: &lt;a href="https://github.com/SafeExamBrowser/seb-mac/discussions" rel="nofollow"&gt;https://github.com/SafeExamBrowser/seb-mac/discussions&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Damian Büchel</dc:creator><pubDate>Mon, 05 Jul 2021 11:34:53 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net7dcce46aa7c7678bb49fd7ecb11bfad11bcd4980</guid></item><item><title>#71 Desktop capture via getDisplayMedia</title><link>https://sourceforge.net/p/seb/feature-requests/71/?limit=25#3e7d</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It might be that we missed something. Feel free to create an issue with the information you posted above on GitHub, which is where we track our work. Then we'll have a another look at it once we have the time.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Damian Büchel</dc:creator><pubDate>Mon, 21 Jun 2021 09:53:14 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netd6a78fe701e963162ee1d56225d5468d20457ded</guid></item><item><title>#71 Desktop capture via getDisplayMedia</title><link>https://sourceforge.net/p/seb/feature-requests/71/?limit=25#611f</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I had a very quick look and this seems at least in principle possible. Not sure how difficult though...&lt;/p&gt;
&lt;p&gt;&lt;a href="https://bitbucket.org/chromiumembedded/cef/issues/2993/webrtc-based-screen-sharing-capturing-not" rel="nofollow"&gt;https://bitbucket.org/chromiumembedded/cef/issues/2993/webrtc-based-screen-sharing-capturing-not&lt;/a&gt;&lt;br/&gt;
&lt;a href="https://bitbucket.org/chromiumembedded/cef/issues/1065/add-support-for-webrtc-based-screen" rel="nofollow"&gt;https://bitbucket.org/chromiumembedded/cef/issues/1065/add-support-for-webrtc-based-screen&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Will try to post something myself as well&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Antonio Pisano</dc:creator><pubDate>Mon, 21 Jun 2021 09:34:42 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netca1297d4c978c56fe87297174625dc328fa52c19</guid></item><item><title>#71 Desktop capture via getDisplayMedia</title><link>https://sourceforge.net/p/seb/feature-requests/71/?limit=25#8945</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;That is something you'd most likely need to ask in the CEF (Chromium Embedded Framework) forum. We simply enabled WebRTC via a configuration flag of the engine, and apparently this does not entail desktop sharing.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Damian Büchel</dc:creator><pubDate>Mon, 21 Jun 2021 09:20:34 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netd9ed242b54715602db744b08ef276cb81569b6e0</guid></item><item><title>#71 Desktop capture via getDisplayMedia</title><link>https://sourceforge.net/p/seb/feature-requests/71/?limit=25#5942</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Thanks for your answer!  Setting aside the effort needed to move to a different browser engine, do you see any contraindication with supporting browser's desktop sharing? What I mean is: was it on purpose or it just happens to not be supported right now?&lt;/p&gt;
&lt;p&gt;Antonio&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Antonio Pisano</dc:creator><pubDate>Mon, 21 Jun 2021 09:15:35 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net96b4037df6eb95d115b7d252905f9d31745bbf44</guid></item><item><title>#71 Desktop capture via getDisplayMedia</title><link>https://sourceforge.net/p/seb/feature-requests/71/?limit=25#bc33</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Yes, that is correct. The browser engine we currently use does not support desktop sharing. There is however a feature planned for the SEB-Server integration which will provide screenshots (maybe even recordings) of the user's desktop.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Damian Büchel</dc:creator><pubDate>Sat, 19 Jun 2021 15:09:46 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net72ab33c64fe325c6e3287c1239b6d8fce5c0b621</guid></item><item><title>Desktop capture via getDisplayMedia</title><link>https://sourceforge.net/p/seb/feature-requests/71/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Dear developers,&lt;/p&gt;
&lt;p&gt;at the university where I work, we have implemented proctoring of student exams via desktop and camera snaphots taken at random intervals using the browser's getDisplayMedia and getUserMedia APIs.&lt;/p&gt;
&lt;p&gt;We plan to harden the security of our exams by introducing your great Safe Exam Browser. However, we are struggling with capturing the desktop, as it does not seem to be possible via getDisplayMedia. Capturing audio and camera instead works perfectly.&lt;/p&gt;
&lt;p&gt;Can you confirm that this is the case? We could so far not find a configuration to help with this. In case this was currently not possible, would you consider adding this feature to the todo list?&lt;/p&gt;
&lt;p&gt;My best regards and thanks for a very useful product.&lt;/p&gt;
&lt;p&gt;Antonio&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Antonio Pisano</dc:creator><pubDate>Fri, 18 Jun 2021 13:28:46 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net80a3788ced933cc151e62f3673b20a213022964f</guid></item><item><title>#59 SEB mac 2.1.3/2.1.4  Battery feature request.</title><link>https://sourceforge.net/p/seb/feature-requests/59/?limit=25#bb93</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi SEB Team&lt;br/&gt;
When we can expect the &lt;strong&gt;SEB 3.0 for macOS&lt;/strong&gt;.  We are developing Proctoring solutions., Mac is not supported now., As per your Roadmap it will be release around Q2 2021. &lt;/p&gt;
&lt;p&gt;May i know when is the Release date of &lt;strong&gt;SEB 3.0 for macOS&lt;/strong&gt;.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ashokkumar R</dc:creator><pubDate>Wed, 26 May 2021 11:27:30 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net7b7d48f7e538d74955a9badcd795f7f591b7a8d3</guid></item><item><title>#70 Check SEB integrity</title><link>https://sourceforge.net/p/seb/feature-requests/70/?limit=25#9e85</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I was thinking that, for instance, with Moodle integration, Moodle itself could some how confirm the seb binary integrity. However, this approach would work only in this kind of environment.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Hugo Costelha</dc:creator><pubDate>Fri, 05 Feb 2021 19:07:02 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net97e062de4f80d6f3be29707631f89554fe0f328a</guid></item><item><title>#70 Check SEB integrity</title><link>https://sourceforge.net/p/seb/feature-requests/70/?limit=25#1da3</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Btw. SEB and an exam system/LMS like Moodle can also check the integrity of the SEB binary, when using the Browser Exam Key. But of course the SEB binary could be manipulated as mentioned in the article you referred, to still send the correct Browser Exam Key even though being hacked. On infrastructre which isn't managed and proctected by the institution (like their own, properly secured computers), you can never be 100% sure about the integrity of the software on it. Obviously when doing BYOD remote exams, you can never provide perfect security by technological means (if any proctoring company promisses that, that's marketing nonsense). &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">SEB Support</dc:creator><pubDate>Fri, 05 Feb 2021 18:21:19 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net9938f04e631bb2fe3230f62f9c0a6a074a5034cf</guid></item></channel></rss>