Proper sources list from Jessie > Stretch

[Fjfj109]

Hi - wondering if with a standard sources list in Jessie (or any stable):

deb
http://deb.debian.org/debian
jessie main
deb-src
http://deb.debian.org/debian
jessie main

deb
http://deb.debian.org/debian
jessie-updates main
deb-src
http://deb.debian.org/debian
jessie-updates main

deb
http://security.debian.org/
jessie/updates main
deb-src
http://security.debian.org/
jessie/updates main

Whether it's enough to simply change jessie to stretch (or testing, or 
sid/unstable, whatever) and everything is fine?

codecrypt

[polymax]

strech 9 / sid (annealmail ?) :
- have you tried it yet ?
- what is your opinion about it ?
thx.

For dealing with this situation, I have always recommended a good pair of 
running shoes.

drive names and UUIDs, was Re: Intresting dd fsck grub uuid fstab action

[Joel Rees]

Fungi4All-san,

I'll try explaining what we don't know whether you understand or not.
First, about

   /dev/sda
   /dev/sdb
   ...

When you turn the machine on, these "names" do not exist. Well, at
least, the computer does not know which physical device is /dev/sda
and which is /dev/sdb, etc.

When the BIOS is finding hard disks and other disk-like persistent
storage devices right after you turn the computer on, it remembers them
in the order it finds them. That means that, if one device finishes
powering up before another, it is likely to have a lower device name.

But even that is a probability, not a guarantee, because BIOS is
generally not looking at each device at the exact moment it powers up.

Because of this, /dev/sda may be your boot drive one time, and may be
your backup drive another time. Or, if you have multiple boot drives, it
may be your MSWIndows boot drive one time and your debian boot
drive the next, etc.

You want to think it should be more simple, but it's not. And it's not your
fault, and it's not Debian's fault. (Who's fault? Microsoft, Intel, Apple,
Maxtor, Seagate, Commodore, Atari, Radio Shack, IBM, DEC,
Honeywell, ..., pretty much all the companies involved.)

Why can't the drive itself just say it's /dev/sda? Well, what happens
when you go to the store and need a /dev/sdc, but all the drives in stock
are named /dev/sdb?

Labels of various sorts were tried, but when labels tended to be too
simply done, like "accounting" instead of something like "ACTG20170601".

So UUIDs were invented as a new sort of label that would theoretically
never be duplicated. They are separate from the labels that the are
called labels in /etc/fstab and gparted's listing, etc.

This explanation is too simple, but close enough to what's happening
to explain what we thing has happened to your drives.

UUIDs or other kinds of labels, where are they stored?

In the storage area of the drive itself, along with the MBR, the partition
information, the file system information, and the program and data files.

That means that, when you use dd to duplicate your storage device,
even the UUID is duplicated.

Now, it turns out that it's convenient to label or name partitions/volumes
within the device, and UUIDs are now generally assigned to each
partition/volume. These are different UUIDs, and they are also stored
on the disk itself. So when you dd a parition/volume, you copy the
UUID for that partition/volume, too.

And when you dd the whole device, you copy all the UUIDs on every
partition/volume on the device.

In order to have both the duplicate and the original connected to the
computer at the same time, you have to figure out a way it can tell
them apart.

The easiest way is to first change the UUID for the new device, and
then the UUIDs for each partition/volume, as well. and then edit
/etc/fstab on the new device to point to the changed UUIDs. You can do
this with an install CD or a live OS on a USB, etc.

You can't do it easily by booting either the new or old device, even if
you boot a different OS on either the new or old device.

It can be done,by giving the necessary volumes and the device itself
labels (that are not UUIDs) and changing /etc/fstab on the device that
will be booted to use labels instead of UUIDs.

Anything you changed before you changed either the UUIDs or labels,
edited /etc/fstab to use the new ones, and rebooted, you really don't
know which drive you did it to.

Running fsck before you take care of that could be really dangerous.

If you read through this and understand it, and can tell us what you did
in a way that we can tell you understand this, we can continue to try to
help.

--
Joel Rees

delusions of being a novelist:
http://joel-rees-economics.blogspot.com/2017/01/soc500-00-00-toc.html

Re: Setting up power-off icon

[Lisi Reisz]

On Thursday 01 June 2017 00:58:37 Ben Caradoc-Davies wrote:
> On 01/06/17 11:48, Lisi Reisz wrote:
> > On Thursday 01 June 2017 00:17:29 Lisi Reisz wrote:
> >> [Desktop Entry]
>
> [...]
>
> >> Icon=/usr/share/pixmaps/power-button-off_318-4.jpg
>
> [...]
>
> > I have one that is working via the desktop shortcut - but am now faced
> > with being unable to change the icon.  (Which is just a gear.)
>
> Lisi, have you tried using a PNG, with a ".png" extension?
>
> https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spe
>c-1.0.html
> https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-late
>st.html "The image files must be one of the types: PNG, XPM, or SVG, and the
> extension must be ".png", ".xpm", or ".svg" (lower case). The support for
> SVG files is optional. Implementations that do not support SVGs should just
> ignore any ".svg" files."
>
> Kind regards,

Thanks!!  Had just succeeded.  Now have an enormous, functioning poweroff 
icon!!

Thank you for the reply.  One icon down, three to go  (The others are just 
URLs and should be easy!  And I know now how to change the icon if I want 
to!)

Lisi

Re: Setting up power-off icon

[Ben Caradoc-Davies]

On 01/06/17 11:48, Lisi Reisz wrote:

On Thursday 01 June 2017 00:17:29 Lisi Reisz wrote:

[Desktop Entry]

[...]

Icon=/usr/share/pixmaps/power-button-off_318-4.jpg

[...]

I have one that is working via the desktop shortcut - but am now faced with
being unable to change the icon.  (Which is just a gear.)


Lisi, have you tried using a PNG, with a ".png" extension?

https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-1.0.html
https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html
"The image files must be one of the types: PNG, XPM, or SVG, and the 
extension must be ".png", ".xpm", or ".svg" (lower case). The support 
for SVG files is optional. Implementations that do not support SVGs 
should just ignore any ".svg" files."


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: Setting up power-off icon

[Lisi Reisz]

On Thursday 01 June 2017 00:17:29 Lisi Reisz wrote:
> I want to set up a large power-off icon on the desktop for a user with very
> poor sight.  I have found a suitable icon and am now struggling with
> setting up the icon on the desktop.
>
> Debian Jessie 8.8 with TDE 14.0.5.
>
> This is what I have so far:
>
> [Desktop Entry]
> Name=Shut_down
> Comment=Log out and power off
> Icon=/usr/share/pixmaps/power-button-off_318-4.jpg
> Exec=sudo /sbin/poweroff
> Type=Application
> Encoding=UTF-8
> Terminal=false
> Categories=None;
>
> saved in /home/$USER/Desktop/

I have one that is working via the desktop shortcut - but am now faced with 
being unable to change the icon.  (Which is just a gear.)

Lisi
>
> I get an icon (the wrong one!) on the desktop on which I can click and it
> launches the application launcher and asks for an application or URL.  If I
> delete the word sudo I get the menu opened up and get asked which
> application I want.
>
> I asked on the TDE list and was told to set up an con to execute the sudo
> command, then googled, and got the idea for this from:
> http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/gui/desk
>top-shortcuts but am now completely at sea and am probably asking the wrong
> questions.
>
> I have never been a lover of icons and am not very hot on their creation
> and use.
>
> The user got badly scammed, so I am doing this instead of just reinstalling
> Windows 7 and letting him get on with it.  If I can succeed, this will be
> much easier for him and MUCH less insecure.
>
> Lisi

I

Setting up power-off icon

[Lisi Reisz]

I want to set up a large power-off icon on the desktop for a user with very 
poor sight.  I have found a suitable icon and am now struggling with setting 
up the icon on the desktop.

Debian Jessie 8.8 with TDE 14.0.5.

This is what I have so far:

[Desktop Entry]
Name=Shut_down
Comment=Log out and power off
Icon=/usr/share/pixmaps/power-button-off_318-4.jpg
Exec=sudo /sbin/poweroff
Type=Application
Encoding=UTF-8
Terminal=false
Categories=None;

saved in /home/$USER/Desktop/

I get an icon (the wrong one!) on the desktop on which I can click and it 
launches the application launcher and asks for an application or URL.  If I 
delete the word sudo I get the menu opened up and get asked which application 
I want.

I asked on the TDE list and was told to set up an con to execute the sudo 
command, then googled, and got the idea for this from:
http://www.raspberry-projects.com/pi/pi-operating-systems/raspbian/gui/desktop-shortcuts
but am now completely at sea and am probably asking the wrong questions. 

I have never been a lover of icons and am not very hot on their creation and 
use.

The user got badly scammed, so I am doing this instead of just reinstalling 
Windows 7 and letting him get on with it.  If I can succeed, this will be 
much easier for him and MUCH less insecure.

Lisi

Re: Poor X performance with Intel 8086:22b1 (Braswell)

[Anil Duggirala]

On Wed, 2017-05-31 at 19:50 +, Curt wrote:
> On 2017-05-31, Anil Duggirala  wrote:
> > 
> > Hello,
> > I was just wondering if you could confirm that I am now using the
> > intel
> > driver, I dont know how to check this in my Xorg log. I am still
> > having
> 
> This used to grep accurately for the pertinent info (if things
> haven't
> changed--I'm still on Wheezy (asthmatic cough)):
> 
>  grep -B4 'Module class: X.Org Video Driver' /var/log/Xorg.0.log
> 
> (adjust path to log to wherever your log is living if it is living
> elsewhere though I doubt it).
> 

Thanks guys, the output of grep -B4 'Module class: X.Org Video Driver'
~/.local/share/xorg/Xorg.0.log is 
[58.352] (II) LoadModule: "intel"
[58.353] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[58.380] (II) Module intel: vendor="X.Org Foundation"
[58.380]    compiled for 1.19.0, module version = 2.99.917
[58.380]    Module class: X.Org Video Driver

So that makes it clear, the intel driver is bein used, is there
anything else I can do to improve my graphics. Is it possible that
installing Mate caused trouble of some sort. I tell you the truth, my
solution to many problems has been to simply reinstall the system. I
believe my system is not correctly configured in some way, for example,
composing this email in Evolution in the little composer window, if I
want to delete several words of text and press and hold my backspace
key, it goes back at a certain speed, so I have to wait to see how back
I will be taken with the time I have held pressed the backspace key.
Performance is just not good in general, and I believe this laptop
should certainly be able to handle Gnome, and guessing I would have
issues with any other DE.
I appreciate any help. For now, my plan, when I have time, is to
reinstall Debian Stretch, dont touch anything and configure to load
intel driver, and hope that any issues have been resolved.
thanks,

Re: Poor X performance with Intel 8086:22b1 (Braswell)

[Ben Caradoc-Davies]

On 01/06/17 02:25, Greg Wooledge wrote:

I have pasted my Xorg.log here
https://paste.debian.net/955691thanks a lot,

Please make sure you put whitespace after the URL.  From
https://paste.debian.net/955691 :


Or surround the URL with angle brackets 
likethis to delimit it from surrounding 
text.


Appendix C of RFC 3986  
recommends delimiting URIs in plain text with angle brackets. This is 
especially useful for URLs used in flowing text where the interpretation 
of trailing punctuation might be ambiguous.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Re: Re: Problem with offlineimap

[marcelolaia]

I have a similar problem.

~$ openssl s_client -connect imap.ufvjm.edu.br:993
CONNECTED(0003)
depth=2 C = IL, O = StartCom Ltd., OU = Secure Digital Certificate Signing, CN
= StartCom Certification Authority
verify error:num=19:self signed certificate in certificate chain
---
Certificate chain
 0 s:/C=BR/CN=imap.ufvjm.edu.br
   i:/C=IL/O=StartCom Ltd./OU=StartCom Certification Authority/CN=StartCom
Class 1 DV Server CA
 1 s:/C=IL/O=StartCom Ltd./OU=StartCom Certification Authority/CN=StartCom
Class 1 DV Server CA
   i:/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom
Certification Authority
 2 s:/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom
Certification Authority
   i:/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom
Certification Authority
---
Server certificate
-BEGIN CERTIFICATE-
snip
-END CERTIFICATE-
subject=/C=BR/CN=imap.ufvjm.edu.br
issuer=/C=IL/O=StartCom Ltd./OU=StartCom Certification Authority/CN=StartCom
Class 1 DV Server CA
---
No client certificate CA names sent
Peer signing digest: SHA512
Server Temp Key: ECDH, P-256, 256 bits
---
SSL handshake has read 5723 bytes and written 326 bytes
Verification error: self signed certificate in certificate chain

snip

Start Time: 1496262567
Timeout   : 7200 (sec)
Verify return code: 19 (self signed certificate in certificate chain)
Extended master secret: no

offlineimap returns

ERROR: Unknown SSL protocol connecting to host 'imap.ufvjm.edu.br' for
repository 'X-Remote'. OpenSSL responded:
[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)

Please, have you any clue here?

Thankx!

-- 
Marcelo

Re: buying ssl certificate

[kc atgb]

Le Wed, 31 May 2017 17:11:49 +,
Eduardo M KALINOWSKI  a écrit :

> On Qua, 31 Mai 2017, Don Armstrong wrote:
> > On Tue, 30 May 2017, kc atgb wrote:
> >> One problem I might have with letsencrypt is that it is not recognized
> >> by all protocol clients. We have customers that are not always up to
> >> date on their side (old OSes, softwares, hosts, ... ), and letsencrypt
> >> is recent in the race, so not integrated on these devices.
> >
> > Letsencrypt signs with a signing key which is signed by the DST Root CA
> > which has been valid since 2000, and should be present on almost every
> > device. [For reference, google.com is signed by a key which was
> > generated in 2002...]
> >
> > So if it does have an issue with validity, it's an issue which many
> > SSL certificates are going to share.
> 

This is an information I do not had and that will help a lot for a decision. 
Good point ;)

> According to themselves:  
> https://letsencrypt.org/docs/certificate-compatibility/
> 

Thanks for the link. I had not took the time to take a look at their site. I 
should have gone there before. It answered certain questions I had and I am more
confortable now with how it works.

K.

Re: Poor X performance with Intel 8086:22b1 (Braswell)

[Greg Wooledge]

On Wed, May 31, 2017 at 07:50:09PM +, Curt wrote:
> This used to grep accurately for the pertinent info (if things haven't
> changed--I'm still on Wheezy (asthmatic cough)):
> 
>  grep -B4 'Module class: X.Org Video Driver' /var/log/Xorg.0.log
> 
> (adjust path to log to wherever your log is living if it is living
> elsewhere though I doubt it).

Just for posterity, in stretch, the Xorg.0.log file is in /var/log/ if
you run startx as root, or use a display manager; or ~/.local/share/xorg/
if you run startx as a non-root user.

(Also, you may want grep -FB4 there, since you're using . as a literal
dot rather than a single-character wildcard expression.  Not likely to
matter much in reality, but hey.)

Re: Poor X performance with Intel 8086:22b1 (Braswell)

[Curt]

On 2017-05-31, Anil Duggirala  wrote:
>
> Hello,
> I was just wondering if you could confirm that I am now using the intel
> driver, I dont know how to check this in my Xorg log. I am still having

This used to grep accurately for the pertinent info (if things haven't
changed--I'm still on Wheezy (asthmatic cough)):

 grep -B4 'Module class: X.Org Video Driver' /var/log/Xorg.0.log

(adjust path to log to wherever your log is living if it is living
elsewhere though I doubt it).

Re: Poor X performance with Intel 8086:22b1 (Braswell)

[Pascal Hambourg]

Le 31/05/2017 à 16:25, Greg Wooledge a écrit :

On Wed, May 31, 2017 at 09:15:20AM -0500, Anil Duggirala wrote:

I was just wondering if you could confirm that I am now using the intel
driver, I dont know how to check this in my Xorg log.


You simply read it until you find the driver lines.

https://paste.debian.net/955691 :

 69 [57.769] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
 70 i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
 71 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
 72 Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, 
Q33,
 73 GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
 74 [57.772] (II) intel: Driver for Intel(R) HD Graphics
 75 [57.772] (II) intel: Driver for Intel(R) Iris(TM) Graphics
 76 [57.772] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics


The above lines are not enough. They just mean that the intel driver has 
been loaded, not that it is actually used. You must read further for 
many more "intel" lines.

Re: buying ssl certificate

[Eduardo M KALINOWSKI]

On Qua, 31 Mai 2017, Don Armstrong wrote:

On Tue, 30 May 2017, kc atgb wrote:

One problem I might have with letsencrypt is that it is not recognized
by all protocol clients. We have customers that are not always up to
date on their side (old OSes, softwares, hosts, ... ), and letsencrypt
is recent in the race, so not integrated on these devices.


Letsencrypt signs with a signing key which is signed by the DST Root CA
which has been valid since 2000, and should be present on almost every
device. [For reference, google.com is signed by a key which was
generated in 2002...]

So if it does have an issue with validity, it's an issue which many
SSL certificates are going to share.


According to themselves:  
https://letsencrypt.org/docs/certificate-compatibility/


--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: buying ssl certificate

[Don Armstrong]

On Tue, 30 May 2017, kc atgb wrote:
> One problem I might have with letsencrypt is that it is not recognized 
> by all protocol clients. We have customers that are not always up to 
> date on their side (old OSes, softwares, hosts, ... ), and letsencrypt 
> is recent in the race, so not integrated on these devices.

Letsencrypt signs with a signing key which is signed by the DST Root CA
which has been valid since 2000, and should be present on almost every
device. [For reference, google.com is signed by a key which was
generated in 2002...]

So if it does have an issue with validity, it's an issue which many
SSL certificates are going to share.

-- 
Don Armstrong  https://www.donarmstrong.com

They say when you embark on a journey
of revenge
dig two graves.
They underestimate me.
 -- a softer world #560
http://www.asofterworld.com/index.php?id=560

Re: Poor X performance with Intel 8086:22b1 (Braswell)

[Greg Wooledge]

On Wed, May 31, 2017 at 09:15:20AM -0500, Anil Duggirala wrote:
> I was just wondering if you could confirm that I am now using the intel
> driver, I dont know how to check this in my Xorg log.

You simply read it until you find the driver lines.

> I have pasted my Xorg.log here
> https://paste.debian.net/955691thanks a lot,

Please make sure you put whitespace after the URL.  From
https://paste.debian.net/955691 :

 69 [57.769] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
 70 i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
 71 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
 72 Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, 
Q33,
 73 GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
 74 [57.772] (II) intel: Driver for Intel(R) HD Graphics
 75 [57.772] (II) intel: Driver for Intel(R) Iris(TM) Graphics
 76 [57.772] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics

etc.

It's not that hard to find.  Compare to your previous X log that had
modeset driver lines.

Re: Poor X performance with Intel 8086:22b1 (Braswell)

[Anil Duggirala]

Hello,
I was just wondering if you could confirm that I am now using the intel
driver, I dont know how to check this in my Xorg log. I am still having
an issue I do believe pertains to Gnome. The Applications menu in Gnome
Classic is sluggish at best, as I described before, moving the mouse
around it starts to dramatically increase cpu use, if I am playing a
video and then go to this menu, the video starts freezing. Also, my
scrolling is still not as smooth as it is in Windows (sorry for this
comparison, but it is what I have). Or, for example, the Gnome
animations upon closing or opening a window or in the Desktop Overview,
are not smooth. I believe I still dont have the best graphics
configuration and would like more help. I have pasted my Xorg.log here
https://paste.debian.net/955691thanks a lot,



On Sat, May 27, 2017, at 10:12 AM, Anil Duggirala wrote:
> Hello, I am looking at 2 new threads in my Inbox, which one are we
> going to follow ??> I pasted my new Xorg.log here 
> https://paste.debian.net/945756
> The situation has definitely improved,
> In my previous post  (in the other thread) I used the word completely,
> because I was missing the cp command. I checked to see if there was an
> xorg.conf file there, there wasnt, so I went ahead and copied.> thanks a lot 
> guys, I appreciate it,
> 
> 
> 
> 
> 

RE: How to set ISO date/time with en_US.utf8 as system default?

[gwmfms6]

On 2017-05-30 12:40, Emanuele Bernardi wrote:
My system has en_US.utf8 for default, but I wanted the iso time so I 
just
added the it_IT.utf8 (dpkg-reconfigure locales) and changed in gnome 
Region

& Language the Formats.



And what do you do when you need the Paper format, currency, numeric 
system, etc to be United States locale? Changing the GNOME format 
changes EVERY variable to whatever that country is set to (not 
necessarily what that country uses, what that country's file is set to). 
I live in the United States, and wouldn't you know it, some of us use 
international date time here. Whoa! But there is no way (in GNOME) to 
set the United States locale while using international date time. And 
yes the United States is still on the Imperial measurement system, but 
many professionals (e.g., scientists) use the Metric system in the 
United States. Yet we cannot set these when using GNOME. If I change the 
format (in GNOME) and switch to a locale that does use international 
date time, I then get currency, paper format, numeric, etc that do not 
conform to the USA.

Re: Trying to understand man page for dd

[mbroe]

David  writes:

> If you browse to explainshell.com and paste shell commands that you
> don't understand, it parses the commands and gives excerpts from
> relevant docs, which might help you in future.

Just a quick thank you for pointing out this resource! This will
definitely be going into my UNIX bag of tricks.
-- 
Mitchell Roe
mitchell@member.fsf.org

Re: Full disk encryption on Jessie - usb key and passphrase

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, May 31, 2017 at 02:02:37PM +0200, Прокси wrote:

[...]

> I followed instructions from this[1] link and it worked.
> 
> https://stackoverflow.com/questions/19713918/how-to-load-luks-passphrase-from-usb-falling-back-to-keyboard

Thanks for the link!
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkus40ACgkQBcgs9XrR2kYTTQCeMZlpU/PYVS2mjAzsK0iATQ+6
cUgAnj2HyPuXejUdXSqpj4h8ttBbuM20
=9wya
-END PGP SIGNATURE-

Re: Full disk encryption on Jessie - usb key and passphrase

[Прокси]

On 2017-May-29 21:17, to...@tuxteam.de wrote:
> On Mon, May 29, 2017 at 03:36:44PM +0200, Прокси wrote:
> > Hello,
> > 
> > I have laptop where I set up full disk encryption following this
> > tutorial: 
> > https://xo.tc/setting-up-full-disk-encryption-on-debian-jessie.html
> > 
> > It works great, but since LUKS can have up to 8 key slots, I would like
> > to add another way to decrypt the laptop: key on a external usb. So, if
> > there is a usb with the key plugged in, laptop doesn't ask for the
> > passphrase and just continue booting; if there isn't - it asks for the
> > passphrase. Can this be done?
> 
> Never tried myself, but cryptsetup luksAddKey  should work.
> Make a backup or... better, try first with a sacrificial device
> (either a file you create with dd, like so
> 
>   dd if=/dev/zero of=my-file bs=4096 count=1024
> 
> or similar, or an USB stick). You then "cryptsetup luksFormat" it,
> "cryptsetup luksOpen" it, make a file system on the corresponding
> device (which will typically appear somewhere in /dev/mapper/) and
> play around with it until you feel secure.
> 
> There are also cryptsetup luksHeaderBackup and luksHeaderRestore
> subcommands which look useful in case of a mishap.
> 
> See the cryptsetup man page for details, and ask here if unsure.
> 
 
I followed instructions from this[1] link and it worked.




https://stackoverflow.com/questions/19713918/how-to-load-luks-passphrase-from-usb-falling-back-to-keyboard

Re: dpkg error

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, May 31, 2017 at 01:37:45PM +0200, tony wrote:
> On 31/05/17 10:46, to...@tuxteam.de wrote:
> >
> > There is an error in uvl-raspidisp-extra's post-remove script. You
> > have several options:
> >
> >  - Yell (OK, be gentle and polite: after all they've worked for you
> >for free :) at the packagers. Perhaps they have a mailing list?
> >
> >  - try "apt-get remove --force-yes --purge uv4l-raspidisp-extras"
> >This is somewhat risky, since you don't know what exactly broke
> >in the postrm script and whether it has left sharp and/or flammable
> >debris behind it.
> >
> >  - try to debug the post-remove script. The script itself is located
> >in /var/lib/dpkg/info/uv4l-raspidisp-extras.postrm (I'm assuming
> >a Debian-ish layout). If you find anything of relevance, you should
> >contact the packagers. It seems that the post-remove script is
> >stumbling upon an unexpected condition.
> >
> >Those scripts are supposed to be idempotent, i.e. calling them
> >several times in a row should have the same effect than calling
> >them just once. But since the script is freaking out, tread
> >carefully...
> >
> > Good luck
> > -- tomás
> >
> Thanks for your reply, Tomas. You are correct, it's not a debian
> package; it comes from here: https://www.linux-projects.org/.
> 
> I tried (2), with no useful effect. I've now done (1), and await a
> result.  I don't think I'm up to (3), which is why I'm asking here.

It actually just takes a bit of stubbornness and lots of patience.
A little help from your friends... and of course, good backups :-)

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkur/UACgkQBcgs9XrR2kZ0kgCfXSUjNqiEAMHRoNC+DOlj9lVL
SHIAmwT+RyfbENGTCdzQ8iEHfpAC4buB
=dNbO
-END PGP SIGNATURE-

Re: dpkg error

[tony]

On 31/05/17 10:46, to...@tuxteam.de wrote:
>
> There is an error in uvl-raspidisp-extra's post-remove script. You
> have several options:
>
>  - Yell (OK, be gentle and polite: after all they've worked for you
>for free :) at the packagers. Perhaps they have a mailing list?
>
>  - try "apt-get remove --force-yes --purge uv4l-raspidisp-extras"
>This is somewhat risky, since you don't know what exactly broke
>in the postrm script and whether it has left sharp and/or flammable
>debris behind it.
>
>  - try to debug the post-remove script. The script itself is located
>in /var/lib/dpkg/info/uv4l-raspidisp-extras.postrm (I'm assuming
>a Debian-ish layout). If you find anything of relevance, you should
>contact the packagers. It seems that the post-remove script is
>stumbling upon an unexpected condition.
>
>Those scripts are supposed to be idempotent, i.e. calling them
>several times in a row should have the same effect than calling
>them just once. But since the script is freaking out, tread
>carefully...
>
> Good luck
> -- tomás
>
Thanks for your reply, Tomas. You are correct, it's not a debian
package; it comes from here: https://www.linux-projects.org/.

I tried (2), with no useful effect. I've now done (1), and await a
result.  I don't think I'm up to (3), which is why I'm asking here.

Re: Debian Stretch Firefox-ESR extensions.gnome.org shows "ReferenceError: chrome is not defined"

[Dejan Jocic]

On 29-05-17, ? ?? wrote:
> 
> For the 3rd link, I remove the firefox add-ons - GNOME Shell Integration 
> extension.
> 
> It shows me this following error. If you click "Click here to install browser 
> extension". The GNOME Shell Integration extension will be installed again.
> 
> [https://support.novell.com/Platform/Publishing/images/gnome-browser-extension-notice.png]
> 

Not sure if it will help you, but I did not remove GNOME Shell
Integration extension, just disabled it and for me that did the job.

Re: zabbix-server-mysql

[Gareth de Vaux]

On Mon 2017-05-29 (18:23), Gareth de Vaux wrote:
> Hi all, I'm trying to install zabbix-server-mysql on Stretch but when I
> get to the configuration over the web stage there's no database type
> option for MySQL, only PostgreSQL. I assume this's because zabbix-server-mysql
> pulls in MariaDB rather than MySQL. How do I get zabbix to use 'MySQL'?

Ok I was missing php-mysql module.

Debian Stretch Firefox-ESR extensions.gnome.org shows "ReferenceError: chrome is not defined"

[? ??]

Hi all,


I cannot use Firefox-ESR to install / remove gnome extensions in my Debian 
Stretch.


The error log shows:

ReferenceError: chrome is not defined

I don't know its meaning, so google.


There is only a little useful materials:

https://www.reddit.com/r/gnome/comments/628oyr/referenceerror_chrome_is_not_defined_when_i_try/

[https://www.redditstatic.com/icon.png]

"ReferenceError: chrome is not defined" when I try to use the Gnome extensions 
site on Firefox, Debian. • 
r/gnome
www.reddit.com
I've downloaded the Firefox extension but it still doesn't appear to work. This 
is the site I'm talking about: https://extensions.gnome.org/




https://unix.stackexchange.com/questions/353962/debian-jessie-unable-to-install-gnome-extension-the-native-host-connector-is-no

[https://cdn.sstatic.net/Sites/unix/img/apple-touch-i...@2.png?v=32fb07f7ce26]

Debian Jessie unable to install GNOME extension, the 
...
unix.stackexchange.com
I have a Debian Jessie 64bit 8.7 and Google Chrome Stable 57.0.2987.110. When I 
visited the GNOME Shell extensions site, I saw the following information: 
Although ...


https://www.suse.com/support/kb/doc/?id=7018856


I have tried all those resolutions, but none works.


For 1st and 2nd links, I install chrome-gnome-shell package.


$ dpkg -l  chrome-gnome-shell
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  chrome-gnome-s 8-4  all  GNOME Shell extensions integratio


But it still shows the following error:

[https://support.novell.com/Platform/Publishing/images/gnome-extensions-reference-error.png]


For the 3rd link, I remove the firefox add-ons - GNOME Shell Integration 
extension.

It shows me this following error. If you click "Click here to install browser 
extension". The GNOME Shell Integration extension will be installed again.

[https://support.novell.com/Platform/Publishing/images/gnome-browser-extension-notice.png]

Re: buying ssl certificate

[kc atgb]

Le 2017-05-28 17:10, Andy Smith a écrit :
> Hello,
> 
> On Fri, May 26, 2017 at 10:04:42PM +, kc atgb wrote:
>> I will have to buy/renew some certificates we have at my job.
>> 
>> There are a certain number of certificates providers. The question I 
>> have is which one do I have to consider ?
> 
> Domain-validated (i.e. they just check you can receive email at the
> domain, or that you can put something int eh domain's DNS) TLS
> certificates are all pretty much the same.
> 
> Your worst case scenario is that the certificate authority is found
> to be hopelessly insecure and is distrusted by one or more major
> browsers.
> 
> I suggest it is worth your time to get letsencrypt automation
> working and just use those, for free.
> 
> If you need extended validation for some reason then the costs will
> vary, pick any big name. You'd probably know what to do already if
> this were a requirement though.
> 

We don't need extended validation and if I am not wrong, that can't 
apply to our case because we have a wildcard certificate and there is no 
specific validation for wildcards.

>> Recently came to the market some lowcoast ssl certificate providers. 
>> Or free ssl providers. What do you think about them ?
> 
> I think the best of the free ones is letsencrypt.
> 

One problem I might have with letsencrypt is that it is not recognized 
by all protocol clients. We have customers that are not always up to 
date on their side (old OSes, softwares, hosts, ... ), and letsencrypt 
is recent in the race, so not integrated on these devices.

> Cheers,
> Andy

Re: dpkg error

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, May 31, 2017 at 09:46:46AM +0200, tony wrote:
> Anyone, please?
> 
> On 30/05/17 16:21, tony wrote:
> > I'm trying to upgrade my packages, but am getting:
> >
> > root@picam1:~# apt-get upgrade
> > Reading package lists... Done
> > Building dependency tree   
> > Reading state information... Done
> > Calculating upgrade... Done
> > The following packages will be REMOVED:
> >   uv4l-raspidisp-extras

Difficult to say. The package in question (uvl-raspidisp-extras) doesn't
seem to be part of Debian...

> > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> > 1 not fully installed or removed.
> > After this operation, 422 kB disk space will be freed.
> > Do you want to continue? [Y/n] y
> > (Reading database ... 104725 files and directories currently installed.)
> > Removing uv4l-raspidisp-extras (1.5) ...
> > insserv: warning: script 'uv4l_uvc' missing LSB tags and overrides

The above seems harmless, but reveals some sloppiness on the part
of uvl-raspidisp's packagers.

> > insserv: There is a loop between service watchdog and uv4l_uvc if stopped
> > insserv:  loop involving service uv4l_uvc at depth 2
> > insserv:  loop involving service watchdog at depth 1
> > insserv: Stopping uv4l_uvc depends on watchdog and therefore on system
> > facility `$all' which can not be true!
> > insserv: exiting now without changing boot order!
> > update-rc.d: error: insserv rejected the script header
> > dpkg: error processing package uv4l-raspidisp-extras (--remove):
> >  subprocess installed post-removal script returned error exit status 1
> > Errors were encountered while processing:
> >  uv4l-raspidisp-extras
> > E: Sub-process /usr/bin/dpkg returned an error code (1)

There is an error in uvl-raspidisp-extra's post-remove script. You
have several options:

 - Yell (OK, be gentle and polite: after all they've worked for you
   for free :) at the packagers. Perhaps they have a mailing list?

 - try "apt-get remove --force-yes --purge uv4l-raspidisp-extras"
   This is somewhat risky, since you don't know what exactly broke
   in the postrm script and whether it has left sharp and/or flammable
   debris behind it.

 - try to debug the post-remove script. The script itself is located
   in /var/lib/dpkg/info/uv4l-raspidisp-extras.postrm (I'm assuming
   a Debian-ish layout). If you find anything of relevance, you should
   contact the packagers. It seems that the post-remove script is
   stumbling upon an unexpected condition.

   Those scripts are supposed to be idempotent, i.e. calling them
   several times in a row should have the same effect than calling
   them just once. But since the script is freaking out, tread
   carefully...

Good luck
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkugt4ACgkQBcgs9XrR2kZV+ACfdGorIh+6SqHrIAbmeeseBsrT
E8cAmwV4ELsoH9JhMsn/L6raArjqkzga
=9SaQ
-END PGP SIGNATURE-

Re: dpkg error

[tony]

Anyone, please?

On 30/05/17 16:21, tony wrote:
> I'm trying to upgrade my packages, but am getting:
>
> root@picam1:~# apt-get upgrade
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> Calculating upgrade... Done
> The following packages will be REMOVED:
>   uv4l-raspidisp-extras
> 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
> 1 not fully installed or removed.
> After this operation, 422 kB disk space will be freed.
> Do you want to continue? [Y/n] y
> (Reading database ... 104725 files and directories currently installed.)
> Removing uv4l-raspidisp-extras (1.5) ...
> insserv: warning: script 'uv4l_uvc' missing LSB tags and overrides
> insserv: There is a loop between service watchdog and uv4l_uvc if stopped
> insserv:  loop involving service uv4l_uvc at depth 2
> insserv:  loop involving service watchdog at depth 1
> insserv: Stopping uv4l_uvc depends on watchdog and therefore on system
> facility `$all' which can not be true!
> insserv: exiting now without changing boot order!
> update-rc.d: error: insserv rejected the script header
> dpkg: error processing package uv4l-raspidisp-extras (--remove):
>  subprocess installed post-removal script returned error exit status 1
> Errors were encountered while processing:
>  uv4l-raspidisp-extras
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> How do I get out of this pickle?
>