Replicant: Issueshttps://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062016-04-26T21:17:26ZReplicant
Redmine Replicant - Issue #1683 (Closed): All Replicant versions from 4.0.3 to 4.4.4 are vulnerable to th...https://redmine.replicant.us/issues/16832016-04-26T21:17:26Zinge gnueingegnue@riseup.net
<p><a class="external" href="https://www.bluecoat.com/security-blog/2016-04-25/android-exploit-delivers-dogspectus-ransomware">https://www.bluecoat.com/security-blog/2016-04-25/android-exploit-delivers-dogspectus-ransomware</a></p>
<p>"Android device in a lab environment was hit with the ransomware when an advertisement containing hostile Javascript loaded from a Web page."</p> Replicant - Issue #1623 (Rejected): Check extensively if f-droid repositories still respects the ...https://redmine.replicant.us/issues/16232016-02-04T13:18:44ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<p>The guidelines are here: <a class="external" href="https://www.gnu.org/distros/free-system-distribution-guidelines.html">https://www.gnu.org/distros/free-system-distribution-guidelines.html</a></p>
<p>While I didn't find a smoking gun yet, the following page raises some concern:<br /><a class="external" href="https://f-droid.org/wiki/page/Antifeatures">https://f-droid.org/wiki/page/Antifeatures</a></p>
<p>To check:</p>
<p>1) What, practically speaking, each anti-feature really is.<br /> For instance the description of the advertizing anti-feature says that no applications is known to have it,<br /> but the list of application with that anti-feature is not empty.<br /> We should check with upstream and fix the descriptions if we can.<br />2) Look if Replicant is affected<br /> For instance Firefox exist in f-droid but it's not possible to run on Replicant.<br /> Still, Firefox should not be possible to install on Replicant because it can suggest non-free add ons.<br />3) List and check well known suspicious applications such as firefox.<br />4) List and check emulators, Parabola has a good reference on it here:<br /> <a class="external" href="https://wiki.parabola.nu/Emulator_licensing_issues">https://wiki.parabola.nu/Emulator_licensing_issues</a></p>
<p>If no issues are to be found, Documentation should be made more clear.</p>
<p>If issues are to be found, F-droid will have to be fixed upstream, not to show any application with anti-features to Replicant users.<br />We should also look which implementations would satisfy the guidelines requirements:</p>
<p><del>> Should the filter be made automatic and not possible to disable.<br /></del>> Can the filter be a setting, and be enabled by default on Replicant.<br />-> Can upstream simply remove applications with anti-features?<br />Having F-droid fixed upstream is desirable not to have to maintain a fork.</p> Replicant - Issue #1617 (Rejected): Check extensively if f-droid repositories still respects the ...https://redmine.replicant.us/issues/16172016-02-04T13:17:26ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<p>The guidelines are here: <a class="external" href="https://www.gnu.org/distros/free-system-distribution-guidelines.html">https://www.gnu.org/distros/free-system-distribution-guidelines.html</a></p>
<p>While I didn't find a smoking gun yet, the following page raises some concern:<br /><a class="external" href="https://f-droid.org/wiki/page/Antifeatures">https://f-droid.org/wiki/page/Antifeatures</a></p>
<p>To check:</p>
<p>1) What, practically speaking, each anti-feature really is.<br /> For instance the description of the advertizing anti-feature says that no applications is known to have it,<br /> but the list of application with that anti-feature is not empty.<br /> We should check with upstream and fix the descriptions if we can.<br />2) Look if Replicant is affected<br /> For instance Firefox exist in f-droid but it's not possible to run on Replicant.<br /> Still, Firefox should not be possible to install on Replicant because it can suggest non-free add ons.<br />3) List and check well known suspicious applications such as firefox.<br />4) List and check emulators, Parabola has a good reference on it here:<br /> <a class="external" href="https://wiki.parabola.nu/Emulator_licensing_issues">https://wiki.parabola.nu/Emulator_licensing_issues</a></p>
<p>If no issues are to be found, Documentation should be made more clear.</p>
<p>If issues are to be found, F-droid will have to be fixed upstream, not to show any application with anti-features to Replicant users.<br />We should also look which implementations would satisfy the guidelines requirements:<br /><del>> Should the filter be made automatic and not possible to disable.<br /></del>> Can the filter be a setting, and be enabled by default on Replicant.<br />-> Can upstream simply remove applications with anti-features?<br />Having F-droid fixed upstream is desirable not to have to maintain a fork.</p> Replicant - Issue #1611 (Rejected): repo don't buildhttps://redmine.replicant.us/issues/16112016-02-01T16:59:32ZIgor Kubinski
<p>source build/envsetup.sh<br />lunch replicant_i9100-userdebug<br />make bacon</p>
<p>make: *** No rule to make target `vendor/replicant/prebuilt/common/apps/FDroid.apk', needed by `/mnt/repli/replicant-4.2/out/target/product/i9100/system/app/FDroid.apk'. Stop.</p>
<ol>
<li>export<br />declare -x ANDROID_BUILD_PATHS="/mnt/repli/replicant-4.2/out/host/linux-x86/bin:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin:/mnt/repli/repli<br />cant-4.2/prebuilts/gcc/linux-x86/mips/mipsel-linux-android-4.6/bin:/mnt/repli/replicant-4.2/development/emulator/qtools:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-li<br />nux-androideabi-4.6/bin:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin:/mnt/repli/replicant-4.2/development/scripts:" <br />declare -x ANDROID_BUILD_TOP="/mnt/repli/replicant-4.2" <br />declare -x ANDROID_DEV_SCRIPTS="/mnt/repli/replicant-4.2/development/scripts" <br />declare -x ANDROID_EABI_TOOLCHAIN="/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin" <br />declare -x ANDROID_HOST_OUT="/mnt/repli/replicant-4.2/out/host/linux-x86" <br />declare -x ANDROID_JAVA_TOOLCHAIN="/usr/lib/jvm/java-6-sun/bin" <br />declare -x ANDROID_PRE_BUILD_PATHS="/usr/lib/jvm/java-6-sun/bin:" <br />declare -x ANDROID_PRODUCT_OUT="/mnt/repli/replicant-4.2/out/target/product/i9100" <br />declare -x ANDROID_PROMPT_PREFIX="[arm-replicant_i9100-userdebug]" <br />declare -x ANDROID_QTOOLS="/mnt/repli/replicant-4.2/development/emulator/qtools" <br />declare -x ANDROID_TOOLCHAIN="/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin" <br />declare -x ARM_EABI_TOOLCHAIN="/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin" <br />declare -x BUILD_ENV_SEQUENCE_NUMBER="10" <br />declare -x CM_BUILD="i9100" <br />declare -x HOME="/home/guest" <br />declare -x JAVA_HOME="/usr/lib/jvm/java-6-sun" <br />declare -x OPROFILE_EVENTS_DIR="/mnt/repli/replicant-4.2/external/oprofile/events" <br />declare -x OUT="/mnt/repli/replicant-4.2/out/target/product/i9100" <br />declare -x PATH="/usr/lib/jvm/java-6-sun/bin:/mnt/repli/replicant-4.2/out/host/linux-x86/bin:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/mips/mipsel-linux-android-4.6/bin:/mnt/repli/replicant-4.2/development/emulator/qtools:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin:/mnt/repli/replicant-4.2/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin:/mnt/repli/replicant-4.2/development/scripts:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games" <br />declare -x TARGET_BUILD_APPS="" <br />declare -x TARGET_BUILD_TYPE="release" <br />declare -x TARGET_BUILD_VARIANT="userdebug" <br />declare -x TARGET_PRODUCT="replicant_i9100"</li>
</ol>
<p>There is no git entry for fdroid in default.xml</p> Replicant - Issue #1593 (Closed): Timeouts when attempting to get manifesthttps://redmine.replicant.us/issues/15932015-12-26T23:14:24ZKoz Rosskoz.ross@runbox.com
<p>I'm following the compilation guide, which asks me to do this:</p>
<p><code>../tools/repo init -u git://git.replicant.us/manifest.git -b replicant-4.2</code></p>
<p>When I attempt this, I get the following:</p>
<p>@[koz@Emi replicant-4.2]$ ../tools/repo init -u git://git.replicant.us/manifest.git -b replicant-4.2<br />gpg: keybox '/home/koz/.repoconfig/gnupg/pubring.kbx' created<br />gpg: /home/koz/.repoconfig/gnupg/trustdb.gpg: trustdb created<br />gpg: key 920F5C65: public key "Repo Maintainer <<a class="email" href="mailto:repo@android.kernel.org">repo@android.kernel.org</a>>" imported<br />gpg: key 692B382C: public key "Conley Owens <<a class="email" href="mailto:cco3@android.com">cco3@android.com</a>>" imported<br />gpg: Total number processed: 2<br />gpg: imported: 2</p>
<p>Get <a class="external" href="https://gerrit.googlesource.com/git-repo/clone.bundle">https://gerrit.googlesource.com/git-repo/clone.bundle</a><br />Get <a class="external" href="https://gerrit.googlesource.com/git-repo">https://gerrit.googlesource.com/git-repo</a><br />Get git://git.replicant.us/manifest.git<br />fatal: unable to connect to git.replicant.us:<br />git.replicant.us[0: 18.4.89.63]: errno=Connection timed out</p>
<p>fatal: unable to connect to git.replicant.us:<br />git.replicant.us[0: 18.4.89.63]: errno=Connection timed out</p>
<p>fatal: cannot obtain manifest git://git.replicant.us/manifest.git@</p>
<p>This repeats itself (minus key imports) when I try again.</p> Replicant - Issue #1503 (Closed): Webview vulnerabilityhttps://redmine.replicant.us/issues/15032015-12-11T13:26:33ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.orgReplicant - Issue #735 (Closed): emmc secure erase bughttps://redmine.replicant.us/issues/7352013-12-12T19:20:56ZAndrew Engelbrechtandrew.e.7327@gmail.com
<p>ok, the following issue does apply to replicant:</p>
<p><a class="external" href="http://wiki.cyanogenmod.org/w/EMMC_Bugs#Samsung_eMMC_secure_erase_bug">http://wiki.cyanogenmod.org/w/EMMC_Bugs#Samsung_eMMC_secure_erase_bug</a></p>
<p>the mentioned kernel patch has not been applied in replicant. (compare:)</p>
<p><a class="external" href="https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3550ccd">https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3550ccd</a><br /><a class="external" href="https://gitorious.org/replicant/kernel_samsung_smdk4210/source/e246554a76666c3b1e521f15e224b86f5917daed:drivers/mmc/card/block.c">https://gitorious.org/replicant/kernel_samsung_smdk4210/source/e246554a76666c3b1e521f15e224b86f5917daed:drivers/mmc/card/block.c</a></p>
<p>if you'd like, i could create a brief warning on the install page, like the one at the top, here: <a class="external" href="http://wiki.cyanogenmod.org/w/I9100_Info">http://wiki.cyanogenmod.org/w/I9100_Info</a> <- this is my offer to help.</p>
<p>my phone's flash chip is an affected model. i'm nearly positive that my flash chip is partly corrupted. (reading sequential 1 MB blocks from my flash chip with dd gives about 6.8 thousand errors. somehow, the affected areas doesn't prevent my phone from booting, or show obvious data corruption during day-to-day use. it's an absolute paradox, but the issue remains that the kernels shipped with replicant are <strong>not</strong> patched to work around this dangerous firmware bug.)</p>
<p>this bug also affects some galaxy s3 phones. there is a work-around available for them too. see: <a class="external" href="http://wiki.cyanogenmod.org/w/EMMC_Bugs">http://wiki.cyanogenmod.org/w/EMMC_Bugs</a></p>
<p>sorry for taking a while to open a new bug report about this.</p> Replicant - Issue #729 (Rejected): have you applied the patch for the emmc secure erase bug, aka ...https://redmine.replicant.us/issues/7292013-12-08T05:03:13ZAndrew Engelbrechtandrew.e.7327@gmail.com
<p>my phone has a chip potentially effected by this:</p>
<p><a class="external" href="http://wiki.cyanogenmod.org/w/EMMC_Bugs#Samsung_eMMC_secure_erase_bug">http://wiki.cyanogenmod.org/w/EMMC_Bugs#Samsung_eMMC_secure_erase_bug</a></p>
<p>has the kernel patch been applied in replicant? for which version?</p>
<p>if you'd like, i could create a brief warning on the install page, like the one at the top, here: <a class="external" href="http://wiki.cyanogenmod.org/w/I9100_Info">http://wiki.cyanogenmod.org/w/I9100_Info</a></p>
<p>i'm currently investigating whether i'm having issues related to this... (i'm not currently using replicant, but i used to.) thanks!</p> Replicant - Issue #711 (Closed): GalaxyS I9000: No SIM card access after changing batteryhttps://redmine.replicant.us/issues/7112013-11-12T22:48:20ZFlo Debiandebianflo@gmx.at
<p>I have installed Replicant 4.0 0005. Finally it's working so far.</p>
<p>But if I change batteries, I cannot access the SIM card anymore. If I<br />enter the PIN, it is always incorrect. Even if I deactivate the PIN<br />request it cannot connect to a mobile network.</p>
<p>In order to make it working again I have to flash clockworkmod (I am<br />using cm-10.2-20131104-NIGHTLY-galaxysmtd) again and then flash the<br />replicant image.</p>
<p>Just restoring a Replicant backup does not help in any ways.</p>
<p>Remark: Flashing with Semaphore_2.7.4 did not work for me, it can't<br />mount /sdcard etc when I boot into recovery mode. I used the described<br />work around to install the replicant recovery.img already at the<br />clockworkmod installation.</p>
<p>The logfiles are added, I used in the terminal as root: logcat -b radio -f /emmc/xx.txt -d -v raw<br />I deactivated the PIN not to get stuck at the PIN request.</p> Replicant - Issue #369 (Rejected): Not able to turn ON Wi-Fi Direct after power ON/OFF the device.https://redmine.replicant.us/issues/3692013-01-04T09:56:30ZAnonymous
<p>Line 3002: 01-02 10:43:51.691 1940 1940 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 3002: 01-02 10:43:51.691 1940 1940 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 3607: 01-02 10:43:55.345 1940 1940 I wpa_supplicant: rfkill: Cannot open RFKILL control device<br />Line 3765: 01-02 10:43:56.035 1940 1940 E wpa_supplicant: Could not set interface wlan0 flags: Operation not permitted<br />Line 3766: 01-02 10:43:56.035 1940 1940 E wpa_supplicant: nl80211: Could not set interface 'wlan0' UP<br />Line 3767: 01-02 10:43:56.035 1940 1940 E wpa_supplicant: wlan0: Failed to initialize driver interface<br />Line 5230: 01-02 10:44:11.851 2445 2445 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 5230: 01-02 10:44:11.851 2445 2445 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 5266: 01-02 10:44:13.112 2445 2445 I wpa_supplicant: rfkill: Cannot open RFKILL control device<br />Line 5280: 01-02 10:44:13.382 2445 2445 E wpa_supplicant: Could not set interface wlan0 flags: Operation not permitted<br />Line 5281: 01-02 10:44:13.382 2445 2445 E wpa_supplicant: nl80211: Could not set interface 'wlan0' UP<br />Line 5282: 01-02 10:44:13.382 2445 2445 E wpa_supplicant: wlan0: Failed to initialize driver interface<br />Line 6540: 01-02 10:44:32.071 2929 2929 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 6540: 01-02 10:44:32.071 2929 2929 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 6541: 01-02 10:44:32.721 2929 2929 I wpa_supplicant: rfkill: Cannot open RFKILL control device<br />Line 6542: 01-02 10:44:32.901 2929 2929 E wpa_supplicant: Could not set interface wlan0 flags: Operation not permitted<br />Line 6543: 01-02 10:44:32.901 2929 2929 E wpa_supplicant: nl80211: Could not set interface 'wlan0' UP<br />Line 6544: 01-02 10:44:32.901 2929 2929 E wpa_supplicant: wlan0: Failed to initialize driver interface<br />Line 6720: 01-02 10:44:52.150 2941 2941 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 6720: 01-02 10:44:52.150 2941 2941 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 6721: 01-02 10:44:52.811 2941 2941 I wpa_supplicant: rfkill: Cannot open RFKILL control device<br />Line 6722: 01-02 10:44:52.971 2941 2941 E wpa_supplicant: Could not set interface wlan0 flags: Operation not permitted<br />Line 6723: 01-02 10:44:52.971 2941 2941 E wpa_supplicant: nl80211: Could not set interface 'wlan0' UP<br />Line 6724: 01-02 10:44:52.971 2941 2941 E wpa_supplicant: wlan0: Failed to initialize driver interface<br />Line 6884: 01-02 10:45:12.190 2947 2947 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 6884: 01-02 10:45:12.190 2947 2947 I wpa_supplicant: wpa_supplicant v0.8.x 0.1 2012-12-20/21:33:43<br />Line 6885: 01-02 10:45:12.870 2947 2947 I wpa_supplicant: rfkill: Cannot open RFKILL control device<br />Line 6886: 01-02 10:45:13.041 2947 2947 E wpa_supplicant: Could not set interface wlan0 flags: Operation not permitted<br />Line 6887: 01-02 10:45:13.041 2947 2947 E wpa_supplicant: nl80211: Could not set interface 'wlan0' UP<br />Line 6888: 01-02 10:45:13.041 2947 2947 E wpa_supplicant: wlan0: Failed to initialize driver interface<br />Line 17114: [init.svc.wpa_supplicant]: [stopped]<br />Line 37698: Proc wpa_supplicant:</p>