Language Selection

English French German Italian Portuguese Spanish

PinePhone ‘Brave Heart’ Starts Shipping, Here’s What to Expect

Filed under
GNU
Linux
Gadgets

If you were plucky enough to pre-order a PinePhone Brave Heart edition last month you may be interested to know that devices start shipping from January 17, 2020.

Yes, this week!

Pine64’s Lukasz Erecinski shares the date in the company’s latest monthly update, explaining: “We’re now ready […] to confirm that PinePhones will begin shipping …on January 17th 2020. The dispatch process will take a couple of days, however, so your unit may ship on the 20th or 25th. At any rate, you’ll have your PinePhone soon”.

The handsets are being shipped through a company called Asendia who, Erecinski says, offer a good balance of shipping times (important to buyers) and cost (important to Pine64, who don’t exactly make huge profits all on this tech).

Read more

PinePhone Braveheart Linux smartphone begins shipping January 17

  • PinePhone Braveheart Linux smartphone begins shipping January 17th

    The PinePhone is an inexpensive smartphone designed to run Linux-based operating systems. Developed by the folks at Pine64, the $150 smartphone was first announced about a year ago — and this week the first units will ship.

    Pine64 says it will begin shipping the PinePhone Braveheart Edition on January 17th — although it could take a few weeks for customers to receive their phones.

    [...]

    All of those operating systems are still very much a work in progress, with new builds rolling out all the time, so it’s recommended you load the operating systems onto an SD card rather than built-in storage.

    But that’s one of the key things that really sets the PinePhone apart from other handsets. Not only is it designed to run free and open source, GNU/Linux-based operating systems. But you can boot from internal storage or an SD card. There’s no bootloader lock that keeps you from running the software you want to use on the phone.

    It also has a headphone jack and a removable battery, unlike most modern phones. And there are hardware killswitches for disabling wireless capabilities, the camera, or other hardware.

    Pine64 also included 6 pogo pins on the back of the phone that could eventually be used to connect custom hardware modules.

    Not bad for a $150 phone.

PinePhone Linux phone starts shipping Friday for the brave...

  • PinePhone Linux phone starts shipping Friday for the brave of heart

    The dream of a truly free as in speech, open source smartphone running Linux has never truly died. It just took on various forms and suffered numerous setbacks along the way. Last year, however, it seemed that the dream is finally close to becoming reality, with both the Purism Librem 5 and the PINE64 PinePhone declaring shipping dates. The Librem 5 had a rocky head start and now it’s the PinePhone BraveHeart edition’s turn to try convincing the world that a Linux phone for consumers is not such a bad idea after all.

PinePhone Linux Smartphone Shipment Finally Begins

  • PinePhone Linux Smartphone Shipment Finally Begins (Slashdot)
  • PinePhone Linux Smartphone Shipment Finally Begins

    In November last year, pre-orders for PinePhone Braveheart Edition commenced for everyone. But due to manufacturing issues coming in the way, the shipment date slipped for weeks, which was scheduled in December last year.

    PinePhone Braveheart Edition is an affordable, open source Linux-based operating system smartphone preloaded with factory test image running on Linux OS (postmarketOS) on inbuilt storage.

    You can check on PinePhone Wiki to find the PinePhone compatible operating system such as Ubuntu Touch, postmarketOS, or Sailfish OS, which you can boot either from internal storage or an SD card.

The PinePhone starts shipping—Linux-powered smartphone for $150

  • The PinePhone starts shipping—a Linux-powered smartphone for $150

    Pine64 has announced that it is finally shipping the PinePhone, a smartphone that takes the rare step outside the Android/iOS duopoly and is designed to run mainline Linux distributions. The PinePhone starts shipping January 17 in the "Braveheart" developer edition.

    This initial "Braveheart" batch of devices is meant for "developer and early adopter" users, according to the Pine64 Store. The phone doesn't come with an end-user OS pre-installed and instead only comes with a factory test image that allows for easy verification that the hardware works. Users are expected to flash their own OS to the device. There are several available, from Ubuntu Touch to Sailfish OS, but they are all currently in an unfinished alpha state. Pine64 says that only enthusiasts with "extensive Linux experience" are the intended customers here—this isn't (yet?) a mainstream product.

The PinePhone begins delivery

  • The PinePhone begins delivery—a Linux-powered smartphone for $150

    The PinePhone is powered through an Allwinner A64 SoC, which options 4 Cortex A53 CPUs at 1.2GHz, constructed on an attractive historical 40nm procedure. This is similar chip the corporate makes use of at the PINE A64 unmarried board pc, a Raspberry Pi competitor. There are 2GB of RAM, a Mali-400 GPU, 16GB of garage, and a 2750mAh battery. The rear digicam is 5MP, the entrance digicam is 2MP, the show is a 1440×720 IPS LCD, and the battery is detachable. There is a headphone jack, a USB-C port, and strengthen for a MicroSD slot, which you’ll if truth be told boot running techniques off of. The mobile modem is a big separate chip this is soldered onto the motherboard: a Quectel EG25-G.

PinePhone's Linux and privacy-centric $150 smartphone

  • PinePhone's Linux and privacy-centric $150 smartphone begins shipping to early adopters

    PINE64, a company that embraces an open and community-driven platform for hardware and software, has begun shipping its first batch of PinePhones, the $150 "BraveHeart" editions. The PinePhone is a Linux-based and developer-focused smartphone, and the BraveHeart in particular is an early-adopter model for the most dedicated of Linux and open-platform users.

    The PinePhone arrives without any software preloaded, and users are expected to flash their OS of choice to the device. The Linux community has a wide swath of OS options that are all in various stages of development, so this blank slate of a phone will be an excellent testbed for their future releases. The components are definitely geared toward testing instead of performance, as it comes with a 5.95" LCD screen, a quad-core 1.2GHz ARM Cortex A-53 processor, 16GB of memory, 2GB of RAM, a rear 5MP camera, and a 2MP front-facing shooter. A 3000 mAh battery powers it all and the phone supports USB-C charging at up to 15W - 5V 3A, a surprising addition given the rest of the mediocre specs. The order page even has a prominent warning that small amounts of dead pixels and other imperfections are to be expected due to the low cost and development-minded nature of the device.

PinePhone, the $149 Linux Phone, Has Started Shipping

  • PinePhone, the $149 Linux Phone, Has Started Shipping for the Brave of Heart

    The long-anticipated PinePhone Linux-powered smartphone has finally started shipping to customers who were brave enough to purchase the first batch.

    The PinePhone Linux phone has been available for pre-order since mid-November 2019, and those who bought one paid as low as $149 USD for the device, which doesn't ship with an operating system preinstalled. After a bit of delay, the PinePhone is now finally shipping to customers, starting today, January 17th.

    "We’re now ready and I am happy to confirm that PinePhones will begin shipping on January 17th, 2020," said PINE64's Lukasz Erecinski. "The dispatch process will take a couple of days, however, so your unit may ship anytime between the 17th and 25th. At any rate, you’ll have your PinePhone soon."

This Linux smartphone is now shipping for $150

  • This Linux smartphone is now shipping for $150

    Computer and developer-board maker Pine64 has started shipping the first edition of its much-anticipated – at least in the open-source community – PinePhone, after pre-orders sold out. Dubbed "Brave Heart", the device is indeed designed only for the keener hobbyists.

    Shipping at only $149.99, Brave Heart is a fully open-source smartphone running Linux, which the company claims was developed "with the community for the community", which means with developers and early adopters, and for developers and early adopters; and in this case, preferably for those who have extensive Linux experience.

    In a departure from Android and iOS, Pine's new project provides a platform for customers to develop Linux-on-phone projects. It does not come with a pre-installed OS, but supports all major Linux phone projects such as Ubuntu Touch, Sailfish OS and Plasma Mobile.

    Although buyers get to choose their OS, therefore, it will be up to them to upload the platform to the Pine Phone – meaning the device is not designed for the average Joe.

The $150 PinePhone feels like it's from an alternate universe

  • The $150 PinePhone feels like it's from an alternate universe

    In our current mobile world, there are essentially two worlds: Android and iOS. But for the oddballs who aren’t satisfied with either option, Pine64 has started shipping the PinePhone, a Linux-based, kinda-DIY smartphone that sells for just $150.

    Originally a crowdsourced startup, Pine64 has made single-board computers and the PineBook laptop in the past, so it isn’t new to developing alternative hardware for Linux. As ArsTechnica wrote, the company’s efforts are not an attempt to create a third mainstream category for smartphones, but the PinePhone still looks to be an interesting concept.

Non-techies, this new phone is not for you

  • Non-techies, this new phone is not for you

    When it comes to smartphones, people mostly talk about operating systems like Android or iOS. But here is a phone which runs Linux and is meant only for developers. If you are not a techie, you simply can’t use this phone. Dubbed as the PinePhone BraveHeart, this phone is made by a company called Pine64 which focuses on open software. The first batch of the devices have already started to ship.

    The company categorically states that this phone is meant only for developers. “Only intend for these units to find their way into the hands of users with extensive Linux experience and an interest in Linux-on-phone,” it said. The device doesn’t come with any pre-installed operating system and you are required to install your own Linux build.
    Priced at $150 or around Rs 11,000, if you are a Linux enthusiast and someone who likes to tinker around your own projects then this phone might interest you.

PinePhone WIth … Linux Onboard Announced at $150

  • PinePhone WIth … Linux Onboard Announced at $150

    f you want to switch to another phone, the first thing you should choose is the operating system – Android and iOS. However, recently, a smartphone called PinePhone was announced with the Linux system. Honestly, we don’t believe this OS can succeed in the smartphone market (it even can’t fight against Windows and macOS), but this is a good choice who doesn’t like any of those OS.

Coverage at OS News

  • The PinePhone starts shipping – a Linux-powered smartphone for $150

    An interesting device for sure, and the dip switches on the motherboard that act has hardware kill switches for things like the microphone and camera are pretty neat. I do take issue with the “Linux-powered” as if that’s some unique quality or anything. Save for the odd iPhone, every single smartphone in the world runs Linux.

    Maybe not in a form that adheres to your no true Scotsman idea of Linux, but 100% Linux nonetheless.

PinePhone $149 Linux smartphone starts shipping

  • PinePhone $149 Linux smartphone starts shipping

    After a slight delay the $149 PinePhone Linux smartphone has now started shipping to customers who have been pre-ordering the unique smartphone since it was made available back in November 2019. PINE64’s Lukasz Erecinski explained in an update, “we’re now ready and I am happy to confirm that PinePhones will begin shipping on January 17th, 2020,” – “The dispatch process will take a couple of days, however, so your unit may ship anytime between the 17th and 25th. At any rate, you’ll have your PinePhone soon.”

PinePhone Announces Affordable Phone Running Linux Operating

  • PinePhone Announces Affordable Phone Running Linux Operating System

    The smartphone industry is under the auspices of iOS and Android operating systems today. Nor can we say that there is a new and powerful phone using another operating system on the market. But now, a smartphone released by Pine64 is running on the Linux operating system and hopes to start a new competition on an operating system basis.

    To be honest, the smartphone called “PinePhone” has little opportunity to compete with other devices in the industry. Because this phone is inadequate both in terms of hardware features, operating system and the applications it supports. However, the affordable price of the phone may attract the attention of consumers who are bored with both operating systems.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

GNU: GDB (Debugger), Project's History, and GCC (Compiler)

  • GDB Debugger Adds Support For Debuginfod Web Server

    Debuginfod is the Red Hat led debug information HTTP web server distributed as part of elfutils and able to supply on-demand source code and ELF/DWARF debug files to debuggers / IDEs / other compiler tooling. The GDB debugger can now tap debuginfod for on-demand source files and debug information that isn't present on the local system. The motivation with debuginfod is to carry less developer "baggage" on local systems when it comes to debug files and potentially even source files. Particularly for organizations or cases like Linux distributions, a centralized debuginfod server could in turn supply the needed files to clients based upon the requested build ID. Red Hat has been working to expand the debuginfod support both for the GNU toolchain and also LLVM, among other possible users.

  • When is GOTS not in the national interest?

    The modern open-source software (OSS) movement can be traced back to the early 1980s with the birth of Richard Stallman’s GNU Project and the Free Software Foundation. [...] However, cost is a red herring for the real challenge presented by GOTS software solutions. On the surface, GOTS seems very similar to OSS which implies that it has the larger structural advantages of OSS. If handled cautiously, it can have those advantages, but care needs to be taken about what sort of existing software is being commoditized. The U.S. has a national interest in maintaining a strong software development capability. We are fortunate to be the dominant software-building country in the world. According to the Forbes 2000 list, the total market capitalization of U.S. internet, software, and computer services companies is close to $4.7 trillion — more than twice the rest of the world combined. Software tech is an enormous comparative advantage for the U.S. As a result, it is clearly in the national interest to have the government avoid directly competing against and potentially weakening the U.S. private sector.

  • New compiler added to popular studio for ARM and Cortex-M IDE

    The studio for ARM/Cortex-M is now supplied with three different compilers: GCC, Clang and the company's own compiler. The new compiler outperforms GCC and regular Clang on most benchmarks, decreasing both size of generated code as well as its execution speed.

Kernel: LWN and Phoronix Articles About Latest Discussions and Linux Developments

  • Filesystem UID mapping for user namespaces: yet another shiftfs

    The idea of an ID-shifting virtual filesystem that would remap user and group IDs before passing requests through to an underlying real filesystem has been around for a few years but has never made it into the mainline. Implementations have taken the form of shiftfs and shifting bind mounts. Now there is yet another approach to the problem under consideration; this one involves a theoretically simpler approach that makes almost no changes to the kernel's filesystem layer at all. ID-shifting filesystems are meant to be used with user namespaces, which have a number of interesting characteristics; one of those is that there is a mapping between user IDs within the namespace and those outside of it. Normally this mapping is set up so that processes can run as root within the namespace without giving them root access on the system as a whole. A user namespace could be configured so that ID zero inside maps to ID 10000 outside, for example; ranges of IDs can be set up in this way, so that ID 20 inside would be 10020 outside. User namespaces thus perform a type of ID shifting now. In systems where user namespaces are in use, it is common to set them up to use non-overlapping ranges of IDs as a way of providing isolation between containers. But often complete isolation is not desired. James Bottomley's motivation for creating shiftfs was to allow processes within a user namespace to have root access to a specific filesystem. With the current patch set, instead, author Christian Brauner describes a use case where multiple containers have access to a shared filesystem and need to be able to access that filesystem with the same user and group IDs. Either way, the point is to be able to set up a mapping for user and group IDs that differs from the mapping established in the namespace itself.

  • Keeping secrets in memfd areas

    Back in November 2019, Mike Rapoport made the case that there is too much address-space sharing in Linux systems. This sharing can be convenient and good for performance, but in an era of advanced attacks and hardware vulnerabilities it also facilitates security problems. At that time, he proposed a number of possible changes in general terms; he has now come back with a patch implementing a couple of address-space isolation options for the memfd mechanism. This work demonstrates the sort of features we may be seeing, but some of the hard work has been left for the future. Sharing of address spaces comes about in a number of ways. Linux has traditionally mapped the kernel's address space into every user-space process; doing so improves performance in a number of ways. This sharing was thought to be secure for years, since the mapping doesn't allow user space to actually access that memory. The Meltdown and Spectre hardware bugs, though, rendered this sharing insecure; thus kernel page-table isolation was merged to break that sharing. Another form of sharing takes place in the processor's memory caches; once again, hardware vulnerabilities can expose data cached in this shared area. Then there is the matter of the kernel's direct map: a large mapping (in kernel space) that contains all of physical memory. This mapping makes life easy for the kernel, but it also means that all user-space memory is shared with the kernel. In other words, an attacker with even a limited ability to run code in the kernel context may have easy access to all memory in the system. Once again, in an era of speculative-execution bugs, that is not necessarily a good thing.

  • Revisiting stable-kernel regressions

    Stable-kernel updates are, unsurprisingly, supposed to be stable; that is why the first of the rules for stable-kernel patches requires them to be "obviously correct and tested". Even so, for nearly as long as the kernel community has been producing stable update releases, said community has also been complaining about regressions that make their way into those releases. Back in 2016, LWN did some analysis that showed the presence of regressions in stable releases, though at a rate that many saw as being low enough. Since then, the volume of patches showing up in stable releases has grown considerably, so perhaps the time has come to see what the situation with regressions is with current stable kernels. As an example of the number of patches going into the stable kernel updates, consider that, as of 4.9.213, 15,648 patches have been added to the original 4.9 release — that is an entire development cycle worth of patches added to a "stable" kernel. Reviewing all of those to see whether each contains a regression is not practical, even for the maintainers of the stable updates. But there is an automated way to get a sense for how many of those stable-update patches bring regressions with them. The convention in the kernel community is to add a Fixes tag to any patch fixing a bug introduced by another patch; that tag includes the commit ID for the original, buggy patch. Since stable kernel releases are supposed to be limited to fixes, one would expect that almost every patch would carry such a tag. In the real world, about 40-60% of the commits to a stable series carry Fixes tags; the proportion appears to be increasing over time as the discipline of adding those tags improves.

  • Finer-grained kernel address-space layout randomization

    The idea behind kernel address-space layout randomization (KASLR) is to make it harder for attackers to find code and data of interest to use in their attacks by loading the kernel at a random location. But a single random offset is used for the placement of the kernel text, which presents a weakness: if the offset can be determined for anything within the kernel, the addresses of other parts of the kernel are readily calculable. A new "finer-grained" KASLR patch set seeks to remedy that weakness for the text section of the kernel by randomly reordering the functions within the kernel code at boot time.

  • Debian discusses how to handle 2038

    At this point, most of the kernel work to avoid the year-2038 apocalypse has been completed. Said apocalypse could occur when time counted in seconds since 1970 overflows a 32-bit signed value (i.e. time_t). Work in the GNU C Library (glibc) and other C libraries is well underway as well. But the "fun" is just beginning for distributions, especially those that support 32-bit architectures, as a recent Debian discussion reveals. One of the questions is: how much effort should be made to support 32-bit architectures as they fade from use and 2038 draws nearer? Steve McIntyre started the conversation with a post to the debian-devel mailing list. In it, he noted that Arnd Bergmann, who was copied on the email, had been doing a lot of the work on the kernel side of the problem, but that it is mostly a solved problem for the kernel at this point. McIntyre and Bergmann (not to mention Debian as a whole) are now interested in what is needed to update a complete Linux system, such as Debian, to work with a 64-bit time_t. McIntyre said that glibc has been working on an approach that splits the problem up based on the architecture targeted. Those that already have a 64-bit time_t will simply have a glibc that works with that ABI. Others that are transitioning from a 32-bit time_t to the new ABI will continue to use the 32-bit version by default in glibc. Applications on the latter architectures can request the 64-bit time_t support from glibc, but then they (and any other libraries they use) will only get the 64-bit versions of the ABI. One thing that glibc will not be doing is bumping its SONAME (major version, essentially); doing so would make it easier to distinguish versions with and without the 64-bit support for 32-bit architectures. The glibc developers do not consider the change to be an ABI break, because applications have to opt into the change. It would be difficult and messy for Debian to change the SONAME for glibc on its own.

  • UEFI Boot Support Published For RISC-V On Linux

    As we've been expecting to happen with the Linux EFI code being cleaned up before the introduction of a new architecture, the RISC-V patches have been posted for bringing up UEFI boot support. Western Digital's Atish Patra sent out the patch series on Tuesday for adding UEFI support for the RISC-V architecture. This initial UEFI Linux bring-up is for supporting boot time services while the UEFI runtime service support is still being worked on. This RISC-V UEFI support can work in conjunction with the U-Boot bootloader and depends upon other recent Linux kernel work around RISC-V's Supervisor Binary Interface (SBI).

  • Linux Kernel Seeing Patches For NVIDIA's Proprietary Tegra Partition Table

    As an obstacle for upstreaming some particularly older NVIDIA Tegra devices (namely those running Android) is that they have GPT entry at the wrong location or lacking at all for boot support. That missing or botched GPT support is because those older devices make use of a NVIDIA proprietary/closed-source table format. As such, support for this proprietary NVIDIA Tegra Partition Table is being worked on for the Linux kernel to provide better upstream kernel support on these consumer devices. NVIDIA Tegra devices primarily rely on a special partition table format for their internal storage while some also support traditional GPT partitions. Those devices with non-flakey GPT support can boot fine but TegraPT support is being worked on for handling the upstream Linux kernel with the other devices lacking GPT support or where it's at the wrong sector. This issue primarily plagues Tegra 2 and Tegra 3 era hardware like some Google Nexus products (e.g. Nexus 7) while fortunately newer Tegra devices properly support GPT.

  • Intel Continues Bring-Up Of New Gateway SoC Architecture On Linux, ComboPHY Driver

    Besides all the usual hardware enablement activities with the usual names by Intel's massive open-source team working on the Linux kernel, one of the more peculiar bring-ups recently has been around the "Intel Gateway SoC" with more work abound for Linux 5.7. The Intel Gateway SoC is a seemingly yet-to-be-released product for high-speed network packet processing. The Gateway SoC supports the Intel Gateway Datapath Architecture (GWDPA) and is designed for very fast and efficient network processing. Outside of Linux kernel patches we haven't seen many Intel "Gateway" references to date. Gateway appears to be (or based on) the Intel "Lightning Mountain" SoC we were first to notice and bring attention to last summer when patches began appearing for that previously unknown codename.

Security: Updates, DNS Features in IPFire, Shodan and Canonical's Role in Robot Operating System (ROS 2)

  • Security updates for Wednesday

    Security updates have been issued by Debian (python-pysaml2), Mageia (clamav, graphicsmagick, opencontainers-runc, squid, and xmlsec1), Oracle (kernel, ksh, python-pillow, systemd, and thunderbird), Red Hat (rh-nodejs12-nodejs), Scientific Linux (ksh, python-pillow, and thunderbird), and SUSE (nodejs6, openssl, ppp, and squid).

  • What you can do with the new DNS features in IPFire

    Every time you try to access a website - for example ipfire.org - you will ask a DNS server for the IP address to connect to. They won't see anything past "the slash" in the URL, but that is not necessary to know what you probably have in mind to do. That DNS server now knows which bank you are with, where you work, where you do your online shopping, who is hosting your emails and many things more... Although this data is not too interesting about one individual, it becomes very relevant when you are looking at many profiles. People who shop at a certain place or are with a certain bank might be high earners. People who shop at another place might have trouble to stay afloat financially. Now I know what advertisements I need to show to which group so that they will become my customers. In short, your whole browser history tells a lot about you and you might be giving it away for free to the advertising industry or other parties who will use your data against you.

  • How Shodan Has Been Improved to Help Protect Energy Utilities

    Shodan is a well-known security hacking tool that has even been showcased on the popular Mr. Robot TV show. While Shodan can potentially be used by hackers, it can also be used for good to help protect critical infrastructure, including energy utilities. At the RSA Conference in San Francisco, Michael Mylrea, Director of Cybersecurity R&D (ICS, IoT, IIoT) at GE Global Research, led a session titled "Shodan 2.0: The World’s Most Dangerous Search Engine Goes on the Defensive," where he outlined how Shodan has been enabled to help utilities identify risks in critical energy infrastructure. Shodan, to the uninitiated, is a publicly available search engine tool that crawls the internet looking for publicly exposed devices. Mylrea explained that utilities are often resource constrained when it comes to cybersecurity and are typically unaware of their risk. In recent years, there have been a number of publicly disclosed incidents involving utilities. To help solve that challenge, Mylrea proposed a project to the US Department of Energy (DoE) to enhance Shodan for utilities so they could use the tool to find risks quickly.

  • Canonical takes leadership role in security for ROS

    Canonical is committed to the future of robotics, as proven a short time ago when we joined the Technical Steering Committee of the second version of the Robot Operating System (ROS 2). We’re also dedicated to building a foundation of enterprise-grade, industry leading security practices within Ubuntu, so we’re excited to join both of these strengths with our own Joe McManus taking the helm of the ROS 2 Security Working Group. We believe robots based on Linux are cheaper to develop, more flexible, faster to market, easier to manage, and more secure. While ROS began as an academic project over a decade ago, it has grown to become the most popular middleware for creating Linux-powered robots. It has harnessed the power of open source, allowing for many of the complex problems faced by robotics to be solved through collaboration. The ROS developer community has continued to grow, and ROS now enjoys an increasing amount of commercial use and supported robots. In response, the ROS community has completely overhauled the ROS codebase and started distributing ROS 2.

Audiocasts/Shows/Screencasts: The Linux Link Tech Show, FLOSS Weekly, Linux Headlines and Arch/Manjaro

  • The Linux Link Tech Show Episode 846

    nodejs 12, raspberry pi, 3d printing, air frying

  • FLOSS Weekly 567: DeepCode

    DeepCode alerts you about critical vulnerabilities you need to solve in your code. DeepCode finds critical vulnerabilities that other automated code reviews don't, such as Cross-Site Scripting, Path Traversal or SQL injection. DeepCode finds critical vulnerabilities that other automated code reviews don't, such as Cross-Site Scripting, Path Traversal or SQL injection with 90% precision.

  • 2020-02-26 | Linux Headlines

    Brave joins forces with the Wayback Machine, the Linux Foundation teams up with IBM to fight climate change, and The Document Foundation puts out a call to the community.

  • Linux Apps I Use At Work

    Linux Apps I Use At Work This video will go over all the applications I use on my Work PC. I go over my email, file browser, and many other features. As a life long Windows user, I was able to optimize my workflow once I moved to Linux and pick up a lot of productivity.

  • Manjaro 19.0 KDE Plasma Edition overview | #FREE OPERATING SYSTEM.

    In this video, I am going to show an overview of Manjaro Linux 19.0 KDE Plasma Edition and some of the applications pre-installed.

  • Manjaro 19.0 XFCE Run Through

    In this video, we are looking at Manjaro 19.0 XFCE.