Profile cover photo
Profile photo
Marius Dalacu
About
Marius's interests
View all
Marius's posts

Why gnome-disk-utilty lost the ability to work with mdadm? It was such an useful tool and was a big hit when it was added in 2012 (mdadm support)...

From their changelog:
-------------------------
gnome-disk-utility 3.11.0
-------------------------

The gnome-disk-utility project provides the Disks and Disk Image
Mounter applications for dealing with storage devices and a
gnome-settings-daemon plug-in for notifying the user about problems
with storage devices.

Changes since gnome-disk-utility 3.10.0:

David Zeuthen (15):
Post-release version bump to 3.11.0
Use GtkHeaderBar and CSD
Remove MD-RAID support
Use flat list in device tree
Use media icon, if available
libgdu: Fix deprecation warnings
disk-image-mounter: Fix deprecation and other warnings
notify: Fix deprecation and other warnings
disks: Fix deprecation and other warnings
Bump required GTK+ version to 3.10.0
Include UI files in application binary via gresource(1)
Update "Edit GPT Partition" dialog
Only show "Power Off" menu item if the drive can power off
Fix warning in "Restore Disk Image" dialog
Update NEWS for release

Matthias Clasen (3):
Be more careful with XIDs
Make dialog work with --xid again
Forgotten header update

Michael Catanzaro (2):
app menu: standardize Help/About/Quit
Capitalize title of the restore image file chooser

Updated translations.

David Zeuthen,
February 14, 2014

Post has attachment
I am trying to build a snap....but i ran into this...fonts are rendered as squares...
#dmMediaConverter  
Any help?
Thanks a lot.
Photo

Post has attachment
Hi, i am trying to build a snap package for my app, #dmmediaconverter  .I don't even know if it is even possible with the latest snapcraft.
This is the error i am getting when i try to sideload my snap on Ubuntu Desktop16.04 x64 with X.
Why is it trying to download ubuntu-core?
Is something i need to put in yaml file to say that it is a desktop app?
Thanks.
Photo

Post has attachment
Complete this google account checkup and you will get 2GB free GDrive storrage. The same as last year. 😄

Post has shared content
#dmMediaConverter
http://dmsimpleapps.blogspot.ro/2014/04/dmmediaconverter.html
Version 1.8.0 is up ;)

- Watermark. Double click on image to quickly position the logo.
- First Mac OSX native build. Soon available on Amazon for 5$.
- Small UI fixes and refinements.
- Small bugs fixes.
- Updated FFMpeg binary with latest version.

Post has shared content
#dmMediaConverter
http://dmsimpleapps.blogspot.ro/2014/04/dmmediaconverter.html
Version 1.8.0 is up ;)

- Watermark. Double click on image to quickly position the logo.
- First Mac OSX native build. Soon available on Amazon for 5$.
- Small UI fixes and refinements.
- Small bugs fixes.
- Updated FFMpeg binary with latest version.

Post has shared content
#dmMediaConverter
http://dmsimpleapps.blogspot.ro/2014/04/dmmediaconverter.html
Version 1.8.0 is up ;)

- Watermark. Double click on image to quickly position the logo.
- First Mac OSX native build. Soon available on Amazon for 5$.
- Small UI fixes and refinements.
- Small bugs fixes.
- Updated FFMpeg binary with latest version.

Post has attachment
#dmMediaConverter
http://dmsimpleapps.blogspot.ro/2014/04/dmmediaconverter.html
Version 1.8.0 is up ;)

- Watermark. Double click on image to quickly position the logo.
- First Mac OSX native build. Soon available on Amazon for 5$.
- Small UI fixes and refinements.
- Small bugs fixes.
- Updated FFMpeg binary with latest version.

Post has shared content
Bad time are coming...
Linux UEFI TPM 2.0 security impacts

The "security chain" begins with one or more TPM 2.0 "Endorsement Keys" (EK), that are stored on the motherboard and that cannot be overwritten without "allowance" by either the owner (hardware manufacturer) or somebody, that is "higher" in key hierarchy, such as Microsoft or U.S. government authorities.

Key Exchange Keys (KEK) establish a trust relationship between the operating system and the platform firmware. Each operating system (and potentially each 3rd party application, that needs to communicate with platform firmware) enrolls a public key (KEKpub) into the platform firmware.

When your hardware comes "Windows Certified", the "Endorsement Key" already is initialized, is signed by Microsoft and U.S. authorities.

"Windows certified" here automatically means "NSA backdoor" included and activated in all encryption modules.

Hardware encryption on newer INTEL Xeon machines, at boot, load those key rings from UEFI tables into processor buffer. From then on, the CPU hardware encrypts everything with Microsoft and U.S. authorities keys being enclosed in the key ring, independent of used operating system!

And surprisingly, it depends on your compiler settings, if your software then uses "hardware accelerated encryption" (fast, but unsafe, since NSA key ring is enclosed) or pure (slower, but NSA safe!) "software encryption". But you have to make sure, that your software encryption libraries do not load Endorsement Keys from UEFI tables. In Red Hat Linux, they do. Red Hat binaries are closed source, can not be rebuilt from src.rpm files.

So everything, that is encrypted on your Windows or Red Hat Linux machine, has a backdoor for U.S. authorities. SSLv2, SSLv3 data, OpenVPN transfers included. On Debian / UBUNTU / FreeBSD / OpenBSD it depends on compiler settings and CPU type used.

On modern INTEL Xeon processors, using "hardware acceleration" at compile time, it automatically generates U.S. backdoors in all kinds of encryption. Note: Independent of OS used!!!

Using software encryption sometimes does not help, since a "secure tunnel" (e.g. to your bank) is build up with help of your own key ring and the bank's key ring.
Since your bank's key ring always is "signed" by U.S. authorities, they automatically can decode all your SSL traffic.

Note: SSL traffic between two partners can be decoded, when key from only one side is known!

Cisco routers, Akamai silent proxies - globally - do a "full take" of all traffic around the world that finally is stored and automatically decoded, read by N.S.A.

There simply is no secrecy/privacy any longer. Even THREEMA isn't safe any longer, because now hardware encryption processor instructions in INTEL XEON processors automatically include the NSA key.

Pretending to "fight terrorism", U.S.A. is spying everywhere to gain strategical advantage over markets, industries, economies, banks, countries, foreign politicians. See Erdogan / J. Tymoshenko phone disclosures, "Edathy case", Merkel mobile spying, Snowden reports about CIA and a swiss banker or BNP Paribas 9 billion "punishment":

http://www.businessinsider.com/edward-snowden-describes-cia-tricks-2013-6

http://www.disclose.tv/action/viewvideo/169947/Tymoshenko_tape_leak_Time_to_grab_guns_and_kill_damn_Russians_RT/

http://www.reuters.com/article/2015/05/01/us-bnp-paribas-settlement-sentencing-idUSKBN0NM41K20150501

http://www.bbc.com/news/world-europe-26336354

http://www.telegraph.co.uk/news/worldnews/europe/germany/10407282/Barack-Obama-approved-tapping-Angela-Merkels-phone-3-years-ago.html

With Linux kernel 4.2, around 100 UEFI / encryption / key signing / key revocation functions have been added, that give U.S. authorities absolute control over "secure boot" - Linux kernel and drivers, all hardware (in processor) encryption and also about what (signed) software is allowed to run on your machine.

In Red Hat Linux that is already included! See: https://access.redhat.com/documentation/en-US/Red_Hat_Certificate_System/8.0/html/Deployment_Guide/SubsystemOverview.html

Also see EDKII specifications: http://tianocore.sourceforge.net/wiki/EDK_II_Specifications

Finally, they will charge you even for free and open source software, that only can be installed and started when "U.S. certificate" tax ($99 per software version) is properly paid to Verisign / Microsoft / Symantec owners.

So, "uncertified" Linux kernels won't run on on "Windows certified" UEFI hardware any longer. And Microsoft / Verisign, in future, simply won't sign Linux kernels or drivers without having TPM 2.0 and hardware encryption included and activated!!!

It's time for a "Windows / NSA uncertified" label! Get rid of UEFI, TPM 2.0, use LinuxBIOS (aka Coreboot aka SeaBIOS), exclusively, that automatically comes with Google Chromebooks, Chromeboxes.

Btw: Docker is based on QEMU: http://wiki.qemu.org/Features/TPM

Don't use new INTEL XEON processors!!! They're coming with NSA keys included in their hardware encryption module!!!

If unsure, use own, pure software encryption!

List of hardware supporting Coreboot is available here: http://www.coreboot.org/Supported_Motherboards

Interestingly, UEFI "secure boot" doesn't make computers more secure. They are still vulnerable to runtime attacks, e.g. buffer overflows, stack/heap overflows. These mechanisms only prevent, that "U.S. uncertified" ($99 per certificate!) software cannot be started any longer.

Thanks for understanding!
Animated Photo

Post has shared content
Win 10 concerns. 😲
If after reading this you still intend to use W10, please be kind and leave your name so I know who you are .
Wait while more posts are being loaded