Re: Fwd: Problemas con repositorios(Solucionado)

[Danilo Gonzalez]

Hola a todos,

El 31 de agosto de 2016, 23:29, Daniel Echeverry 
escribió:

> Hola Danilo
>
> El 31/08/2016 10:33 p. m., "Danilo Gonzalez" 
> escribió:
> >
> > Hola,
> >
> > El 31 de agosto de 2016, 17:43, Juan Lavieri 
> escribió:
> >>
> >> Hola Danilo.
> >>
> >>
> >> El 31-08-2016 a las 05:51 p.m., Danilo Gonzalez escribió:
> >>>
> >>> Cordial Saludo,
> >>>
> >>> Recientemente instalé Debian 8.5 en mi portátil sin ningún problema.
> Una vez finalizada la instalación traté de instalar algunos paquetes
> adicionales usando apt-get pero lamentablemente no funcionó, trate
> cambiando los repositorios en el sources.list, tal como indican en algunas
> páginas web, pero sigue sin funcionar.
> >>>
> >>> Los repositorios que tengo son:
> >>>
> >>> # Repositoris Principales Debian
> >>> deb http://ftp.debian.net/debian/ jessie main contrib non-free
> >>>
> >>> # Repositorios de Seguridad
> >>> deb http://security.debian.org/ jessie/updates
> mdebian-user-spanish@lists.debian.orgain contrib non-free
> >>>
> >>> El error que sale al ejecutar apt-get update es:
> >>>
> >>> Err http://ftp.debian.net jessie InRelease
> >>>
> >>> Err http://ftp.debian.net jessie Release.gpg
> >>>   No se pudo conectar a 168.175.55.16:8080  >:
> >>
> >>
> >> Es probable que ese servidor tenga problemas.  Cambia los repositorios.
> >>
> >> Usa
> >>
> >> #netselect-apt -o archivo-donde-deseas-dejar-la-salida
> >
> > Hola Juan,
> > Gracias por tu sugerencia, pero no funcionó, al parecer el primer paso
> del netselect es descargar una lista de los mirrors de debian usando wget
> pero no se puede obtener dicha lista, ya que se conecta al mismo servidor
> que aparece en los errores previos.
> > La salida es la siguiente:
> > Using distribution stable.
> > Retrieving the list of mirrors from www.debian.org...
> >
> > --2016-08-31 21:25:17--  http://www.debian.org/mirror/mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:27:25--  (intento: 2)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:29:35--  (intento: 3)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:31:45--  (intento: 4)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:33:56--  (intento: 5)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:36:08--  (intento: 6)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:38:22--  (intento: 7)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:40:36--  (intento: 8)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:42:51--  (intento: 9)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:45:07--  (intento:10)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:47:25--  (intento:11)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:49:42--  (intento:12)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:51:59--  (intento:13)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:54:16--  (intento:14)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:56:33--  (intento:15)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 21:58:51--  (intento:16)  http://www.debian.org/mirror/
> mirrors_full
> > Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de
> conexión.
> > Reintentando.
> >
> > --2016-08-31 22:01:08--  (intento:17)  http://www.debian.org/mirror/
> 

Re: Fwd: Problemas con repositorios

[Daniel Echeverry]

Hola Danilo

El 31/08/2016 10:33 p. m., "Danilo Gonzalez" 
escribió:
>
> Hola,
>
> El 31 de agosto de 2016, 17:43, Juan Lavieri 
escribió:
>>
>> Hola Danilo.
>>
>>
>> El 31-08-2016 a las 05:51 p.m., Danilo Gonzalez escribió:
>>>
>>> Cordial Saludo,
>>>
>>> Recientemente instalé Debian 8.5 en mi portátil sin ningún problema.
Una vez finalizada la instalación traté de instalar algunos paquetes
adicionales usando apt-get pero lamentablemente no funcionó, trate
cambiando los repositorios en el sources.list, tal como indican en algunas
páginas web, pero sigue sin funcionar.
>>>
>>> Los repositorios que tengo son:
>>>
>>> # Repositoris Principales Debian
>>> deb http://ftp.debian.net/debian/ jessie main contrib non-free
>>>
>>> # Repositorios de Seguridad
>>> deb http://security.debian.org/ jessie/updates
mdebian-user-spanish@lists.debian.orgain contrib non-free
>>>
>>> El error que sale al ejecutar apt-get update es:
>>>
>>> Err http://ftp.debian.net jessie InRelease
>>>
>>> Err http://ftp.debian.net jessie Release.gpg
>>>   No se pudo conectar a 168.175.55.16:8080 :
>>
>>
>> Es probable que ese servidor tenga problemas.  Cambia los repositorios.
>>
>> Usa
>>
>> #netselect-apt -o archivo-donde-deseas-dejar-la-salida
>
> Hola Juan,
> Gracias por tu sugerencia, pero no funcionó, al parecer el primer paso
del netselect es descargar una lista de los mirrors de debian usando wget
pero no se puede obtener dicha lista, ya que se conecta al mismo servidor
que aparece en los errores previos.
> La salida es la siguiente:
> Using distribution stable.
> Retrieving the list of mirrors from www.debian.org...
>
> --2016-08-31 21:25:17--  http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:27:25--  (intento: 2)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:29:35--  (intento: 3)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:31:45--  (intento: 4)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:33:56--  (intento: 5)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:36:08--  (intento: 6)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:38:22--  (intento: 7)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:40:36--  (intento: 8)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:42:51--  (intento: 9)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:45:07--  (intento:10)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:47:25--  (intento:11)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:49:42--  (intento:12)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:51:59--  (intento:13)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:54:16--  (intento:14)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:56:33--  (intento:15)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 21:58:51--  (intento:16)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 22:01:08--  (intento:17)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 22:03:25--  (intento:18)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
> Reintentando.
>
> --2016-08-31 22:05:42--  (intento:19)
http://www.debian.org/mirror/mirrors_full
> Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de 

Re: Fwd: Problemas con repositorios

[Danilo Gonzalez]

Hola,

El 31 de agosto de 2016, 17:43, Juan Lavieri  escribió:

> Hola Danilo.
>
>
> El 31-08-2016 a las 05:51 p.m., Danilo Gonzalez escribió:
>
>> Cordial Saludo,
>>
>> Recientemente instalé Debian 8.5 en mi portátil sin ningún problema. Una
>> vez finalizada la instalación traté de instalar algunos paquetes
>> adicionales usando apt-get pero lamentablemente no funcionó, trate
>> cambiando los repositorios en el sources.list, tal como indican en algunas
>> páginas web, pero sigue sin funcionar.
>>
>> Los repositorios que tengo son:
>>
>> # Repositoris Principales Debian
>> deb http://ftp.debian.net/debian/ jessie main contrib non-free
>>
>> # Repositorios de Seguridad
>> deb http://security.debian.org/ jessie/updates
>> mdebian-user-spanish@lists.debian.orgain contrib non-free
>>
>> El error que sale al ejecutar apt-get update es:
>>
>> Err http://ftp.debian.net jessie InRelease
>>
>> Err http://ftp.debian.net jessie Release.gpg
>>   No se pudo conectar a 168.175.55.16:8080 :
>>
>
> Es probable que ese servidor tenga problemas.  Cambia los repositorios.
>
> Usa
>
> #netselect-apt -o archivo-donde-deseas-dejar-la-salida
>
Hola Juan,
Gracias por tu sugerencia, pero no funcionó, al parecer el primer paso del
netselect es descargar una lista de los mirrors de debian usando wget pero
no se puede obtener dicha lista, ya que se conecta al mismo servidor que
aparece en los errores previos.
La salida es la siguiente:
Using distribution stable.
Retrieving the list of mirrors from www.debian.org...

--2016-08-31 21:25:17--  http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:27:25--  (intento: 2)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:29:35--  (intento: 3)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:31:45--  (intento: 4)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:33:56--  (intento: 5)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:36:08--  (intento: 6)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:38:22--  (intento: 7)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:40:36--  (intento: 8)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:42:51--  (intento: 9)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:45:07--  (intento:10)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:47:25--  (intento:11)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:49:42--  (intento:12)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:51:59--  (intento:13)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:54:16--  (intento:14)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:56:33--  (intento:15)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 21:58:51--  (intento:16)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 22:01:08--  (intento:17)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 22:03:25--  (intento:18)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 22:05:42--  (intento:19)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Reintentando.

--2016-08-31 22:08:00--  (intento:20)
http://www.debian.org/mirror/mirrors_full
Conectando con 168.175.55.16:8080... falló: Expiró el tiempo de conexión.
Abandonando.

/usr/bin/netselect-apt: wget failed to retrieve

Re: Fwd: Problemas con repositorios

[Juan Lavieri]

Hola Danilo.


El 31-08-2016 a las 05:51 p.m., Danilo Gonzalez escribió:

Cordial Saludo,

Recientemente instalé Debian 8.5 en mi portátil sin ningún problema. 
Una vez finalizada la instalación traté de instalar algunos paquetes 
adicionales usando apt-get pero lamentablemente no funcionó, trate 
cambiando los repositorios en el sources.list, tal como indican en 
algunas páginas web, pero sigue sin funcionar.


Los repositorios que tengo son:

# Repositoris Principales Debian
deb http://ftp.debian.net/debian/ jessie main contrib non-free

# Repositorios de Seguridad
deb http://security.debian.org/ jessie/updates 
mdebian-user-spanish@lists.debian.orgain contrib non-free


El error que sale al ejecutar apt-get update es:

Err http://ftp.debian.net jessie InRelease

Err http://ftp.debian.net jessie Release.gpg
  No se pudo conectar a 168.175.55.16:8080 :


Es probable que ese servidor tenga problemas.  Cambia los repositorios.

Usa

#netselect-apt -o archivo-donde-deseas-dejar-la-salida

Revisas el contenido del mismo y luego _respaldas_ el 
/etc/apt/sources.list y lo sustituyes por este recién generado.


man netselect-apt



Err http://security.debian.org jessie/updates InRelease

Err http://security.debian.org jessie/updates Release.gpg
  No se pudo conectar a 168.175.55.16:8080 :
Leyendo lista de paquetes... Hecho
W: Fallo al obtener 
http://ftp.debian.net/debian/dists/jessie/InRelease 



W: Fallo al obtener 
http://security.debian.org/dists/jessie/updates/InRelease 



W: Fallo al obtener 
http://ftp.debian.net/debian/dists/jessie/Release.gpg 
 No se pudo 
conectar a 168.175.55.16:8080 :


W: Fallo al obtener 
http://security.debian.org/dists/jessie/updates/Release.gpg 
 No se 
pudo conectar a 168.175.55.16:8080 :


W: No se han podido descargar algunos archivos de índice, se han 
omitido, o se han utilizado unos antiguos en su lugar.


Agradezco de antemano cualquier orientación.




Saludos

--
Juan M Lavieri

Errar es de humanos, pero es mas humano culpar a los demás.

Fwd: Problemas con repositorios

[Danilo Gonzalez]

Cordial Saludo,

Recientemente instalé Debian 8.5 en mi portátil sin ningún problema. Una
vez finalizada la instalación traté de instalar algunos paquetes
adicionales usando apt-get pero lamentablemente no funcionó, trate
cambiando los repositorios en el sources.list, tal como indican en algunas
páginas web, pero sigue sin funcionar.

Los repositorios que tengo son:

# Repositoris Principales Debian
deb http://ftp.debian.net/debian/ jessie main contrib non-free

# Repositorios de Seguridad
deb http://security.debian.org/ jessie/updates
mdebian-user-spanish@lists.debian.orgain contrib non-free

El error que sale al ejecutar apt-get update es:

Err http://ftp.debian.net jessie InRelease


Err http://ftp.debian.net jessie Release.gpg

  No se pudo conectar a 168.175.55.16:8080:
Err http://security.debian.org jessie/updates InRelease

Err http://security.debian.org jessie/updates Release.gpg
  No se pudo conectar a 168.175.55.16:8080:
Leyendo lista de paquetes... Hecho
W: Fallo al obtener http://ftp.debian.net/debian/dists/jessie/InRelease

W: Fallo al obtener http://security.debian.org/dis
ts/jessie/updates/InRelease

W: Fallo al obtener http://ftp.debian.net/debian/dists/jessie/Release.gpg
No se pudo conectar a 168.175.55.16:8080:

W: Fallo al obtener http://security.debian.org/dis
ts/jessie/updates/Release.gpg  No se pudo conectar a 168.175.55.16:8080:

W: No se han podido descargar algunos archivos de índice, se han omitido, o
se han utilizado unos antiguos en su lugar.

Agradezco de antemano cualquier orientación.

Re: livestreamer i mplayer

[Ernest Adrogué]

2016-08-31, 10:22 (+0200); Pere Nubiola Radigales escriu:
> Has provat de executar
> 
> livestreamer --stdout -cache 2048' $URL best | mplayer

He provat

livestreamer --stdout $URL best | mplayer -cache 2048 -

però el livestreamer segueix controlant el terminal.  Estic pensant que
potser hauria de fer que el livestreamer escrigui en un fitxer fifo en segon
pla i executar mplayer en primer pla, però és una mica rebuscat.

Re: livestreamer i mplayer

[Ernest Adrogué]

2016-08-31, 00:33 (+0200); Alex Muntada escriu:
> Has provat amb gnome-mplayer o algun altre frontal del mplayer?

No, suposo que seria una opció.  No sé si en queda algun que estigui
mantingut, el gnome-mplayer ha desaparegut del mapa...

Re: Decentralized reliable instant messaging?

[Lisi Reisz]

On Wednesday 31 August 2016 19:40:18 Curt wrote:
> On 2016-08-31, Lisi Reisz  wrote:
> > On Wednesday 31 August 2016 17:45:07 Curt wrote:
> >> as is your own post in which you did not wrap your lines.
> >
> > Does everyone else agree with this?  They are displaying wrapped for me,
> > and the setting requires them to wrap and is still set to column 78.  (I
> > have just checked.)  If they are not wrapping for the rest of you, then
> > this is a bug which needs pursuing.
>
> https://lists.debian.org/debian-user/2016/08/msg01039.html

But:

https://lists.debian.org/msgid-search/201608311634.41415.lisi.re...@gmail.com
and even:
https://lists.debian.org/msgid-search/201608311916.07090.lisi.re...@gmail.com

There was obviously something wrong with that particular one.  Thunderstorm??  
Pixies??

Lisi

[jessie] how to file bug report against update that broke other packages?

[D. R. Evans]

As of a few days ago the gscan2pdf program is no longer functioning properly
in up-to-date jessie.

The culprit seems to be one of the packages updated as part of the recent
imagemagick security update. But I don't which of the updated files, or even
which package, causes the problem (indeed, I am not 100% certain that it is
the imagemagick update that is the source of the problem, but it sure looks
very, very likely).

So I am unsure how to proceed and let the developers know that the breakage
needs to be fixed (ASAP, I hope), since the breakage appears in a package that
was not updated, and I don't know precisely which package is responsible.

Any advice as to how to notify the debian team of the problem in a way that
will be useful to them would be gratefully received.

  Doc

-- 
Web:  http://www.sff.net/people/N7DR



signature.asc
Description: OpenPGP digital signature

Re: Decentralized reliable instant messaging?

[Amir H. Firouzian]

On Wed, Aug 31, 2016 at 6:21 PM, Brian  wrote:

> On Wed 31 Aug 2016 at 13:14:08 +, Amir H. Firouzian wrote:
>
> > There is a trade off between decentralization & reliability. Traditional
> > E-Mail that people are talking about is NOT TRULY decentral.
> > For instance think about how E-Mail work:
> > 1- Mail Client Query MX record from DNS
>
> IM systems don't do this too? What do they use? Telepathy?
>
> > 2- Connect to SMTP Server and Exchange E-Mail.
>
> Ok. That's unarguable.
>
> > 3- SMTP figure out the sender IP and look domain of E-Mail
>
> My server doesn't do that. I suppose I could instruct it to.
>
> > 3- SMTP server query SRV Record of that domain and check is that IP
> valid.
>
> My server doesn't do that. I suppose I could instruct it to.
>
> > 4- (Nowadays) SMTP query DKIM (Which is TXT record) and validate also.


> My server doesn't necessarily do that; it depends; I suppose I could
> instruct it never to do it.
>
​*​
​My Point isn't how YOUR server work! This is how E-Mail providers does. ​


>
> > So think how BITMESSAGE
> > :
> > 1- The massage ONLY can access in TWO DAYS!
> > 2- All Nodes have ALL E-Mail in Cryptic Form.
>
> The link says
>
>   Bitmessage is a decentralized, encrypted, peer-to-peer, trustless
>   communications protocol that can be used by one person to send
>   encrypted messages to another person, or to multiple subscribers.
>
> How does this sound?
>
>   Email is a decentralized, encrypted, peer-to-peer, trustless
>   communications protocol that can be used by one person to send
>   encrypted messages to another person, or to multiple subscribers.
>
​*​

​But there is completely ​

​different. First it isn't P2P; It's Server to Server. Second it base on
TRUST; You trust on E-Mail providers;
When you send message in traditional E-Mail your E-Mail provider know what
you send. The term that technical people said is "End-To-End Encryption" or
OTR (Off The Record).
Proton Email 
​already solve this problem.​
First Problem which named decentralization is more complex. Your E-Mail is
already going to some Server which is define by your E-Mail Address's
domain; We don't call it "Decentral". In BITMESSAGE your address is kind of
string that look like BITCOIN addresses. e.g:
1dice8EMZmqKvrGE4Qc9bUFf9PX3xaYD
​p
​ALL the message within two days are accessible for ALL People in
BITMESSAGE Net; But it's Cryptic and ONLY the TRUE Receiver which have the
Private Key of That Address can decrypt message. It's like someone send ALL
People something and you are the only person in world know how to open it
(Of Course if N Not Equal NP

&
HERE
)!
It's called "Asymmetric Encryption

".


> > About you last sentence:
> > It's better that your message Not arrive instead of being disclose! and
> > This is the philosophy behind True P2P IM systems.
>
> It's a lousy philosophy. The purpose of communication systems is to
> communicate reliably. I think you must have some special circumstances
> in mind.
>
> ​*
My point isn't "We don't care about reliability" instead There are plenty
of research doing to make it more reliability; But it isn't our FIRST
Priority.
In addition being skeptical is very strong reason to use it.

Re: Decentralized reliable instant messaging?

[David Wright]

On Wed 31 Aug 2016 at 00:34:47 (+0100), Brian wrote:
> On Tue 30 Aug 2016 at 17:22:34 -0500, David Wright wrote:
> 
> > On Tue 30 Aug 2016 at 20:26:45 (+0100), Brian wrote:
> > > On Tue 30 Aug 2016 at 19:31:08 +0100, Lisi Reisz wrote:
> > > 
> > > > Just out of interest, why have you sent a personal copy of a reply to 
> > > > the 
> > > > Debian list about an email of David Wright's to me, which is an 
> > > > irrelevant 
> > > > flouting of the code of conduct rules??? ;-)  It's not like you Brian 
> > > > to make 
> > > > Human Errors. ;-)
> > > 
> > > So I did. Apologies.
> > > 
> > > I make errors all the time; I just fight a good rearguard action. :) But
> > > not this time; surrender is the honorable course of action.
> > > 
> > > 2016-08-30 18:45:35 1ben6M-0008JJ-JK => lisi.re...@gmail.com R=dnslookup 
> > > T=remote_smtp H=gmail-smtp-in.l.google.com [64.233.167.26] 
> > > X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 
> > > DN="C=US,ST=California,L=Mountain View,O=Google Inc,CN=mx.google.com" 
> > > C="250 2.0.0 OK 1472579135 u10si39132321wje.183 - gsmtp"
> > > 2016-08-30 18:45:50 1ben6M-0008JJ-JK => debian-user@lists.debian.org 
> > > R=dnslookup T=remote_smtp H=bendel.debian.org [82.195.75.100] 
> > > X=TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128 DN="C=NA,ST=NA,L=Ankh 
> > > Morpork,O=Debian SMTP,OU=Debian SMTP 
> > > CA,CN=bendel.debian.org,EMAIL=hostmas...@bendel.debian.org" C="250 2.0.0 
> > > Ok: queued as 147DD63"
> > > 2016-08-30 18:45:50 1ben6M-0008JJ-JK Completed
> > > 
> > > I must have hit "r" or "g" in mutt. Damn these two bottles of wine. :)
> > 
> > The error might have been mine. I think I CC'd Lisi in error.
> > The other list I'm on expects people to group-reply.
> > I forgot myself. Sorry if I caused confusion by appearing
> > to send a personal email when it was public (if this is all
> > about <20160830161810.GA8604@alum>).
> 
> The cavalry arrives - but hours late :); I should have stuck to my
> rearguard policy. But thanks for the intervention. It turns out I did
> hit "L" and not "r" or "g".
> 
> Additionally, I have learned a little more about mutt's behaviour.
> 
>   (default: L)
> 
> Reply to the current or tagged message(s) by extracting any addresses 
> which
> match the regular expressions given by the lists or subscribe commands, 
> but
> also honor any Mail-Followup-To header(s) if the $honor_followup_to
> configuration variable is set. In addition, the List-Post header field is
> examined for mailto: URLs specifying a mailing list address. Using this
> when replying to messages posted to mailing lists helps avoid duplicate
> copies being sent to the author of the message you are replying to.
> 
> Your mail had a Mail-Followup-To header to debian-user and Lisi Reisz. I
> think it was this rather than the Cc that got me a telling off.

You got there a lot faster than I did. Presumably you don't/didn't
have any special treatment of followup_to and honor_followup_to in
your .muttrc file.

It would appear to me that it's only polite for someone to add their
*own* address to any Mail-Followup-To header (apart from list addresses
of course) so that they receive replies-to-replies (which a simple
Reply-To header wouldn't achieve).

Otherwise it acts a bit like an email-bomb, doesn't it?

Cheers,
David.

Re: Decentralized reliable instant messaging?

[David Wright]

On Tue 30 Aug 2016 at 18:45:34 (+0100), Brian wrote:
> On Tue 30 Aug 2016 at 11:18:10 -0500, David Wright wrote:
> 
> > On Tue 30 Aug 2016 at 09:59:42 (-0400), Henning Follmann wrote:
> > > 
> > > However, why email is still reliable, because a proper setup provides you
> > > with a well defined error messages (in case it is not delivered).
> > 
> > There are occasions when this is several days later, unfortunately.
> > Some of the retry intervals seem to have been set in the days when
> > people/institutions dialled up the internet on a daily schedule.
> 
> I think you have moved from unreliability (whatever that means) to
> timeliness of delivery. If you put your mail under the control of
> a third party you presumably accept their conditions. Anyway, what,
> without drowning the internet in frequent retries, would be suitable
> as a sequence of retry intervals? Exim on Debian uses
> 
>  # This single retry rule applies to all domains and all errors. It specifies
>  # retries every 15 minutes for 2 hours, then increasing retry intervals,
>  # starting at 1 hour and increasing each time by a factor of 1.5, up to 16
>  # hours, then retries every 6 hours until 4 days have passed since the first
>  # failed delivery.

Much of that is reasonable, but I think (without any evidence) that
most people would prefer to receive a message of abandonment after
16 hours (perhaps only six) rather that sit on their hands for
four days.

For comparison, look at the time people here wait for a posting to
appear before submitting a second try, and a third...

Cheers,
David.

Re: Decentralized reliable instant messaging?

[David Wright]

On Wed 31 Aug 2016 at 16:10:37 (+0200), Nicolas George wrote:
> Le quartidi 14 fructidor, an CCXXIV, David Wright a écrit :
> > The error might have been mine. I think I CC'd Lisi in error.
> > The other list I'm on expects people to group-reply.
> > I forgot myself.

After some experiments, I think I have to withdraw that explanation.
Group-reply would have put
To: Lisi ..., debian-user@lists.debian.org
whereas my posting had
To: debian-user@lists.debian.org
Cc: Lisi ...
which is what list-reply writes¹.

In fact, the problem was that the posting I replied to had
Mail-Followup-To: Lisi ..., debian-user@lists.debian.org
in the header, which mutt dutifully obeyed *and* copied into my reply.
I might have spotted that Lisi was CC'd, but the copying of
Mail-Followup-To into my posting happens behind the scenes,
like handling References.

I suppose I could set a blank Mail-Followup-To in my composition
editor to prevent its auto-generation. (I don't do anything
sophisticated like posting to multiple lists.) But that might defeat
people who use Mail-Followup-To as a way of receiving replies without
being subscribed to the list, so maybe that's not a good idea.

> Systematic group-reply is the correct way of using mailing-lists, because it
> is the only way that does not require the user to waste time for each mail
> deciding the proper key to hit.
> 
> This clause of the code of conduct is unsustainable, and therefore should be
> ignored until the configuration is fixed and the corresponding clause
> updated.
> 
> In the meantime, let the whiners whine; the non-whiners can unilaterally fix
> things for themselves by setting the reply-to header, just like you or me.

Yes, I can't understand why more people don't set it.

In the dim and distant past, I put
:0 Wh: $HOME/msgid.lock
| formail -D 19 $HOME/msgid.cache
into my .procmailrc file which got rid of any duplicates.

¹ only when replying to that particular posting of course.

Cheers,
David.

Test

[Steven Dodge]

Testing ..disregard ...

Re: Jessie (8.0) slow to boot

[Alan McConnell]

On Wed, Aug 31, 2016 at 09:16:00AM -0500, Richard Owlett wrote:
> I have Jessie installed on a desktop and a laptop. They both take about
> 105-110 seconds to boot. Squeeze on the desktop takes ~15 seconds to boot.
  My jessie install also takes a long time to boot.  A lot of it
  is because of attempts to start/stop/do something with
  COMRESET.  Eventually, after a minute, the boot process 'gives
  up'.

  What is COMRESET?  What does it do? can I get rid of these
  attempts?

TIA for anticipated information/help.

Alan McConnell

-- 
Alan McConnell :  http://globaltap.com/~alan/
  Memory says, "I did that."  Pride replies, "I could not have
  done that."  Eventually, Memory yields.(Friederich Nietzsche)

Re: Jessie (8.0) slow to boot

[David Wright]

On Wed 31 Aug 2016 at 11:25:17 (-0500), Richard Owlett wrote:
> On 8/31/2016 10:44 AM, Felix Miata wrote:
> >Richard Owlett composed on 2016-08-31 09:58 (UTC-0500):
> >...
> >>Aug 31 09:13:32 deb8-2ndtry systemd[1]: Job
> >>dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x2daf89\x2d33ba51934630.de
> >>
> >>Aug 31 09:13:32 deb8-2ndtry systemd[1]: Timed out waiting for
> >>device dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x
> >>Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for
> >>/dev/disk/by-uuid/0a344714-ae06-43ed-af89-33ba5193463
> >>Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for
> >>Swap.
> >
> >Which was installed last, Squeeze, or Jessie? You can expect this
> >message trying to boot the earlier installed installation after
> >having done the later install. Unless you take affirmative action
> >to deny it, an existing swap partition used by the earlier
> >installation will be reformatted by the later installation.
> >Reformatting creates a new UUID, thus making the UUID referring
> >to it in the earlier installation's fstab invalid. The earlier
> >needs to have its fstab edited to use the correct swap partition
> >UUID, or volume label, or device name, if swap is actually
> >desired or needed.
> 
> There may be some subtle problems still lurking somewhere which show
> up only for people like me doing many installs of *nearly* identical
> systems.

There way well be. One possible scenario is installing Debian, then
installing again but overwriting the filesystems. To all intents
and purposes, the same responses will get you to the same place,
*but* the swap partition will have been recreated with a new UUID.

To avoid having the swap partition recreated is slightly tedious.
I do it as a matter of course because my swap is referenced by
LABEL rather than UUID. You have to force d-i to install without
one, and then enable it afterwards in VC2 (if you actually need it
for the d-i's use, which I don't) which is disapproved of.

> Commenting out the line in /etc/fstab DID allow it to boot without
> warning messages.
> 
> However,taking into account Darac's comments, does this now mean
> that the machines are now operating without a swap partition?

Quite possibly. Do you need it, particularly on the desktop (which
I assume you don't hibernate). Maybe on the laptop.

> IIRC the current instance of Jessie on the laptop was the
> chronologically the last OS installed so by the comments in this
> thread should not have had the problem. The laptop is my designated
> "Guinea pig" so I'll do a fresh install to see if problem persists.

Are you copying in a pre-existing /etc/fstab by any chance? Fine if
you use LABELs, but it needs checking/editing if you rely on UUIDs.

Cheers,
David.

Re: Decentralized reliable instant messaging?

[Curt]

On 2016-08-31, Lisi Reisz  wrote:
> On Wednesday 31 August 2016 17:45:07 Curt wrote:
>> as is your own post in which you did not wrap your lines.
>
> Does everyone else agree with this?  They are displaying wrapped for me, and 
> the setting requires them to wrap and is still set to column 78.  (I have 
> just checked.)  If they are not wrapping for the rest of you, then this is a 
> bug which needs pursuing.
>

https://lists.debian.org/debian-user/2016/08/msg01039.html


-- 
"I always say to people, ‘No one earns $100 million. You steal $100 million.’
People earn $10 an hour. People earn $40,000 a year. ‘Earn’ means work. Okay?
It doesn’t mean steal, which with these vast amounts of money, of course you
steal them." — Fran Lebowitz

Re: Decentralized reliable instant messaging?

[Brian]

On Wed 31 Aug 2016 at 13:14:08 +, Amir H. Firouzian wrote:

> There is a trade off between decentralization & reliability. Traditional
> E-Mail that people are talking about is NOT TRULY decentral.
> For instance think about how E-Mail work:
> 1- Mail Client Query MX record from DNS

IM systems don't do this too? What do they use? Telepathy?

> 2- Connect to SMTP Server and Exchange E-Mail.

Ok. That's unarguable.

> 3- SMTP figure out the sender IP and look domain of E-Mail

My server doesn't do that. I suppose I could instruct it to.

> 3- SMTP server query SRV Record of that domain and check is that IP valid.

My server doesn't do that. I suppose I could instruct it to.

> 4- (Nowadays) SMTP query DKIM (Which is TXT record) and validate also.

My server doesn't necessarily do that; it depends; I suppose I could
instruct it never to do it.

> So think how BITMESSAGE
> :
> 1- The massage ONLY can access in TWO DAYS!
> 2- All Nodes have ALL E-Mail in Cryptic Form.

The link says

  Bitmessage is a decentralized, encrypted, peer-to-peer, trustless
  communications protocol that can be used by one person to send
  encrypted messages to another person, or to multiple subscribers.

How does this sound?

  Email is a decentralized, encrypted, peer-to-peer, trustless 
  communications protocol that can be used by one person to send 
  encrypted messages to another person, or to multiple subscribers.

> About you last sentence:
> It's better that your message Not arrive instead of being disclose! and
> This is the philosophy behind True P2P IM systems.

It's a lousy philosophy. The purpose of communication systems is to
communicate reliably. I think you must have some special circumstances
in mind.

Re: Decentralized reliable instant messaging?

[Lisi Reisz]

On Wednesday 31 August 2016 17:45:07 Curt wrote:
> as is your own post in which you did not wrap your lines.

Does everyone else agree with this?  They are displaying wrapped for me, and 
the setting requires them to wrap and is still set to column 78.  (I have 
just checked.)  If they are not wrapping for the rest of you, then this is a 
bug which needs pursuing.

Lisi

Re: Decentralized reliable instant messaging?

[Amir H. Firouzian]

It's not my point of view, It's P2P philosophy.
if you consider the project that try to collect Internet Informations; This
philosophy seems to be rational.

On Wed, Aug 31, 2016 at 1:46 PM, Henning Follmann  wrote:

> On Wed, Aug 31, 2016 at 01:14:08PM +, Amir H. Firouzian wrote:
> >
> [...]
>
>
> > About you last sentence:
> > It's better that your message Not arrive instead of being disclose! and
> > This is the philosophy behind True P2P IM systems.
>
> Getting offtopic here. However, please elaborate why this is better?
> Is there some fundamental law behind your rational?
>
> -H
>
> --
> Henning Follmann   | hfollm...@itcfollmann.com
>
>

Re: Decentralized reliable instant messaging?

[Gene Heskett]

On Wednesday 31 August 2016 11:31:18 Lisi Reisz wrote:

> On Wednesday 31 August 2016 15:45:42 Mark Fletcher wrote:
> > Well and
> > good -- actually, very good, because it prevents me making the
> > stupid mistake I frequently make of cc-ing the poster of the mail I
> > am replying to.
>
> But it doesn't prevent Nicolas from deliberately cc-ing most of the
> rest of us when replying to our mails; which is exceedingly annoying
> and is NOT in compliance with the CoC.
>
> It is, of course, and annoyance one can easily avoid by blacklisting
> him.
>
> Lisi

I do not know if its CoC correct, but my copy of kmail, courtesy the 
Trinity people, shows that a "reply-to-list", goes only to the list, 
while a "reply-all" goes to the list, and CC's the poster, in this case 
Lisi.

And a simple reply says only to the list.  That seems odd as it should 
reply to Lisi.  Something in the list headers apparently makes the list 
address a higher priority.  So I use reply-all, then nuke the list 
address by hand, and change the  Cc: line to a To: line if I want to PM 
Lisi.

This works for me, and I am rarely chided about it. I would much druther 
the reply-all kept track of the posters involved in the thread and CC'd 
them if I click on the reply-all button, but that would be a memory 
eating monster of a headache for kmail. FWIW, I turn off kmails thread 
follower long ago, so I see them in their order of arrival here.

Those who missed a reply with valuable info in it because they aren't 
subscribed, expecting to be Cc'd for that whole thread, should 
subscribe, problem solved.

If our Mr. George were to use an email agent that did observe a similar 
protocol, that would stand a good chance of shutting down threads such 
as this one.

Have a great day everyone. My coffee pot had the audacity to run dry, so 
I said a few magic incantations over it, and its now refilling itself.

Then I'll go see whats wrong with a tapered thread cutting program I am 
in the middle of writing a universal version of in g-code (rs-274 std).  
Once that has been done, then I need to find a plastic pan big enough to 
hold this part covered in distilled water, and cut, using edm, three 
slots at 60 degree angles so the part will have 6 fingers that a 
similarly tapered nut I'll have to make, will screw onto, crushing those 
fingers into a no slip grip on the end of a ball screw, even with half a 
ton or more of push or pull is exerted on the screw. Fun & games when I 
win, and it keeps me out of the bars to boot!

I should probably get a life, I have so far, outlived this one. :)

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Security Updates

[Larry Dighera]

Hello Paul,

Thank you for your kind response to my inquiry.

My comments in-line below:


On Wed, 31 Aug 2016 14:48:36 +0100, Darac Marjal 
wrote:

>On Tue, Aug 30, 2016 at 12:58:47PM -0700, Larry Dighera wrote:
>>
>>This page  states:
>>
>>"If you use APT, add the following line to /etc/apt/sources.list to be 
>> able
>>to access the latest security updates:
>>
>>deb http://security.debian.org/ jessie/updates main contrib non-free
>>
>>After that, run apt-get update followed by apt-get upgrade."
>>
>>Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running Debian
>>Jessie results in an error message indicating that the public key is not 
>>found.
>>It also finds two libraries that require updating that are not found when the
>>above mentioned /etc/apt/sources.list entry is removed.
>
>As other people are discussing how to avoid the problems, let me have a 
>go at answering your questions directly.
>
>>
>>  1.  What do I need to do to prevent the error message?
>
>Check that "debian-archive-keyring" is installed. 
>

# apt-get -s install debian-archive-keyring
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'raspbian-archive-keyring' instead of
'debian-archive-keyring'
raspbian-archive-keyring is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Hmmm...  I didn't expect that.  Now I am confused.  I don't recall where I got
the notion that I was running Debian Jessie as opposed to Raspbian Jessie.  I
suppose it was from this link:
 where it is stated:

"Raspbian has now been updated to the new stable version of Debian, which
is called Jessie."

I guess I failed to make the distinction between Raspbian Jessie and Debian
Jessie.  Me culpa.

>
>If that is showing as untrusted as well, then read 
>https://ftp-master.debian.org/keys.html.  
>Note the warning at the top, though: "Please note that the details here 
>are for information only, you should not rely on them and use other ways 
>to verify them."
>

I don't know if it's "showing as un-trusted," but I'm beginning to suspect my
confusion between Raspbian Jessie and Debian Jessie is the source of the issue
I experienced.  

Here is the output from os-release and uname:

 # cat ../usr/lib/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/;
SUPPORT_URL="http://www.raspbian.org/RaspbianForums;
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs;


 # uname -a
Linux raspberrypi3 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l
GNU/Linux

I guess that puts a stake in the heart of this apparent non-issue. 

>
>>
>>  2.  As there are other security related URLs (doubtless, as
>>  distributed/released) that are checked during apt-get update, is the
>>  recommended additional entry advisable/useful for this platform?
>
>If you're running Debian, then that line should provide all the security 
>updates you require. If you've added other repositories, though (PPAs, 
>for example, or if you're using a debian-derived distribution such as 
>Ubuntu, Mint, Devuan etc), then you should consult THOSE projects 
>individually to see if they provide security updates (they may simply 
>provide a rolling "bleeding edge" update model instead).
>

Apparently Raspbian Jessie is "a debian-derived distribution," and not Debian
Jessie as I erroneously believed until your assistance enlightened me.

I'll have to presume the default Raspbian Jessie apt sources repositories
provide the intended security robustness, despite the possible security issues
in libldap-2.4-2 and linux-libc-dev packages that came to light when I ran
apt-get update with the "deb http://security.debian.org/ jessie/updates main
contrib non-free" entry in my /etc/apt/sources.list.

As you suggested, I'll take this discussion to raspbian.org, and see if they
can shed some light on the possible security issues in the libldap-2.4-2 and
linux-libc-dev packages.

I am grateful your thoughtful and sagacious support, and the education I
received as a result.  It's always good to grok truth.  :-)

Best regards,
Larry

Re: Test

[Angel Vicente]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

El Wed, 31 Aug 2016 18:35:53 +0200
Angel Vicente  escribió:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Hola.
> 
> Perdonen las molestias si reciben este correo: tengo la sospecha que
> he sido dado de baja de la lista.
> 
> Salu2

Ah, pues parece que no

> 
> - -- 
> Key fingerprint 01DC 0386 2B28 0A02 A270 E243 008B AABF 1822 9851
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iF4EAREIAAYFAlfHB2kACgkQAIuqvxgimFHjUgD/QVYjbNUvNbHx9rPn0nQnkwny
> o3y9Et0UoxVc9daVKs8BAJSvUsBB2NqatW15l0S1yChiUJgazpLEuhttxcOur+7z
> =QwtK
> -END PGP SIGNATURE-



- -- 
Key fingerprint 01DC 0386 2B28 0A02 A270 E243 008B AABF 1822 9851
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iF4EAREIAAYFAlfHEwQACgkQAIuqvxgimFFb4AD/asYcuPn3wYcLL6k1neFKI1X7
3ti/9UKotfuPlM5J+XgA/2FnB+lI5PNu6lrWEHmnZ2zr2dUXEPCMGOoiBGxoROJJ
=L2Q7
-END PGP SIGNATURE-

Re: Test

[José Mateo Ruiz]

Hola Angel:
Decías el  Miércoles, 31 de Agosto del 2016.
> Hola.
>
> Perdonen las molestias si reciben este correo: tengo la sospecha que he
> sido dado de baja de la lista.
>
> Salu2
>
Si este recibes no estar de baja :-)

 

-- 

   __ __  __   __     ___   __ 
  (  )   (  \/  ) (  ) (_  _)(  _) /  \ 
 __)(  _  )(  /__\   )(   ) _)( () )
(___/ (_)(_/\/\_)(_)(_) (__) (___) \__/ 
  50550 Aragón España
---  
Chimenea que tira poco, el humo a los ojos 

Re: Security Updates

[Charlie Kravetz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 31 Aug 2016 08:16:45 -0700
Larry Dighera  wrote:

>On Wed, 31 Aug 2016 13:28:21 +, "Andrew M.A. Cater"
> wrote:
>
>>On Wed, Aug 31, 2016 at 06:04:34AM -0700, Larry Dighera wrote:  
>>> On Tue, 30 Aug 2016 20:44:27 +, "Andrew M.A. Cater"
>>>  wrote:
>>>   
>>> >On Tue, Aug 30, 2016 at 12:58:47PM -0700, Larry Dighera wrote:  
>>> >> 
>>> >> This page  states:
>>> >> 
>>> >> "If you use APT, add the following line to /etc/apt/sources.list to 
>>> >> be able
>>> >> to access the latest security updates:
>>> >> 
>>> >> deb http://security.debian.org/ jessie/updates main contrib non-free
>>> >> 
>>> >> After that, run apt-get update followed by apt-get upgrade."
>>> >> 
>>> >> Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running 
>>> >> Debian
>>> >> Jessie results in an error message indicating that the public key is not 
>>> >> found.
>>> >> It also finds two libraries that require updating that are not found 
>>> >> when the
>>> >> above mentioned /etc/apt/sources.list entry is removed.
>>> >> 
>>> >>   1.  What do I need to do to prevent the error message?
>>> >> 
>>> >>   2.  As there are other security related URLs (doubtless, as
>>> >>   distributed/released) that are checked during apt-get update, is the
>>> >>   recommended additional entry advisable/useful for this platform?  
>>> >
>>> >Debian or Raspbian?
>>> >
>>> >If Raspbian - that's based very closely on Debian but isn't strictly 
>>> >Debian.
>>> >
>>> >Mixing the two might not be a good idea since there will probably be 
>>> >incompatibilities at some level.
>>> >
>>> >There is a port of pure Debian to the Pi 2 - look on the Debian wiki - but 
>>> >no one has yet done this for the Pi 3 as far as I know.
>>> >
>>> >[The original Pi required different compilation options to cope with 
>>> >floating point "stuff" which rendered Debian incompatible:
>>> >Raspbian is a re-compilation to suit the Raspberry Pi. Pi 2 is ARM v7 with 
>>> >hardware floating point. Pi 3 is 64 bit core (so arm64 would work if
>>> >the Pi folk hadn't put in 32 bit glue logic or thereabouts). There are 
>>> >also issues with the way of loading the operating system, initialising 
>>> >video
>>> >and non-free firmware which can cause problems.]
>>> >
>>> >All the best,
>>> >
>>> >AndyC  
>>> 
>>> 
>>> 
>>> Hello Andy,
>>> 
>>> I thought I made it clear that the OS was Debian Jessie.  It was installed 
>>> from
>>> the NOOBS release: .  As you 
>>> can
>>> see from this article
>>> , Debian Jessie 
>>> was
>>> released for the Raspberry Pi platform almost a year ago, September 2015.  
>>> 
>>> Have you any insight into how to overcome the ;public key not found; error
>>> message adding that security repository to the apt list, as stated on the
>>> Debian.org web site, may be resolved?
>>> 
>>> Thank you for your response.
>>> 
>>> Best regards,
>>> Larry
>>>  
>>
>>Hi Larry, 
>>
>>That's Raspbian - NOOBS installs Raspbian.
>>
>>As Lisi Reisz has stated to you in another email: Raspbian handle their own 
>>security updates.
>>
>>If you want to add the keys to the Debian security updates repository you can 
>>use an apt-key add command and the key available from 
>>http://ftp-master.debian.org/keys.html
>>[The main archive signing key is also used to sign the security updates].
>>
>>Be aware that you might create problems for yourself.
>>
>>You may well want to look at the Debian Administrators handbook - you can try 
>>apt-get install debian-handbook if the package is also available for Raspbian.
>>
>>Hope this helps,
>>
>>Al the very best,
>>
>>AndyC 
>>
>>[Copying to the list as this may be of more use more widely]  
>
>
>Hello Andy,
>
>Have you even looked at the information here:
>?  After reading
>that announcement, how can you continue to insist that I am not running Debian
>Jessie?  
>
>I appreciate your pointer to adding keys to the Debian security updates
>repository with apt-key add.  I will look into that, however if it were
>necessary for me to do that manually, I would have expected the
> page to have mentioned it
>explicitly.  Perhaps I expect too much...
>
>I find the stability of the Debian APT system to be one of the most valuable
>aspects of Debian Linux, compared to other less stable distributions I have
>encountered over the years.  So I am wary of doing anything to break it, even
>if it proffered on a Debian web page, as you cautioned.  
>
>Thank you for sharing your knowledge.
>
>Best regards,
>Larry
>

/etc/apt/sources.list for Debian Jessie for the raspberry pi:
deb http://mirrordirector.raspbian.org/raspbian/ stable main 

Re: Linux MATE problème de changement d'utilisateur.

[contact]

  
  
Bonsoir
oui j'arrive a fermer la session sans problème.
Quand au gestionnaire de connexion ce ne peut pas être lui qui
  est en cause puisque le problème se pose depuis MATE. 

François-Marie BILLARD
  Sculpteur - Céramique 

Le 30/08/2016 à 22:39, MENGUAL
  Jean-Philippe a écrit :


  Bonjour,

Et tu arrives à Fermer la session? éteindre? redémarrer?

Amitiés,


Le 30/08/2016 à 16:02, contact a écrit :

  
Bonsoir

Debian JESSIE et Mate 1.8.1

Quand je clique sur "changer d'utilisteur" rien ne se passe.

Merci

*François-Marie BILLARD*
Sculpteur - Céramique 
Le 30/08/2016 à 15:07, MENGUAL Jean-Philippe a écrit :


  Bonjour,

Sur MATE 1.14? Debian testing?

Que se passe-t-il exactement? Ca ne lance rien? Ca ferme la fenêtre?

Cordialement,



Le 30/08/2016 à 11:23, contact a écrit :

  
sauf que ctrl+alt+F1 ou F2..F7 change de console et ne permet pas de
passer de la session utilisteur1 à la session utilisteur2 sans fermer la
première sous X.

*François-Marie BILLARD*
www.billard-francois-marie.eu
Le 30/08/2016 à 11:05, Frédéric MASSOT a écrit :


  Le 30/08/2016 à 10:58, contact a écrit :

  
Bonjour

depuis peu, dans MATE quand je souhaite depuis une session changer
d'utilisateur et non me déconnecter cela ne fonctionne plus.

Menu Système->Fermer la session->Changer d'utilisateur.

  
  Oui, il faut passer sur l'une des consoles où est GDM : ctrl+alt+F1 ou
F2...F7.

J'ai eu la flemme de faire un rapport de bug.



  



  
  



  

Re: Decentralized reliable instant messaging?

[Curt]

On 2016-08-31, Lisi Reisz  wrote:
>>
>> How about postings in HTML as a case in point of egregious violation?
>
> Purely factually, it was in multipart-alternative.  I hadn't even noticed 
> that my nice plain text display was attched to the possibility of displaying 
> HTML.
>

And purely factually he posted in HTML as well as text, the former being a
violation, as is your own post in which you did not wrap your lines.

-- 
"I always say to people, ‘No one earns $100 million. You steal $100 million.’
People earn $10 an hour. People earn $40,000 a year. ‘Earn’ means work. Okay?
It doesn’t mean steal, which with these vast amounts of money, of course you
steal them." — Fran Lebowitz

Re: Jessie (8.0) slow to boot

[Felix Miata]

Richard Owlett composed on 2016-08-31 11:25 (UTC-0500):


Commenting out the line in /etc/fstab DID allow it to boot
without warning messages.



However,taking into account Darac's comments, does this now mean
that the machines are now operating without a swap partition?


If fstab has no uncommented lines for swap, then there will no swap enabled. 
Among ways to see if swap is currently active are top and free.

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Test

[Angel Vicente]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hola.

Perdonen las molestias si reciben este correo: tengo la sospecha que he
sido dado de baja de la lista.

Salu2

- -- 
Key fingerprint 01DC 0386 2B28 0A02 A270 E243 008B AABF 1822 9851
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iF4EAREIAAYFAlfHB2kACgkQAIuqvxgimFHjUgD/QVYjbNUvNbHx9rPn0nQnkwny
o3y9Et0UoxVc9daVKs8BAJSvUsBB2NqatW15l0S1yChiUJgazpLEuhttxcOur+7z
=QwtK
-END PGP SIGNATURE-

Re: Decentralized reliable instant messaging?

[Lisi Reisz]

On Wednesday 31 August 2016 17:12:43 Lisi Reisz wrote:
> On Wednesday 31 August 2016 17:01:36 Curt wrote:
> > On 2016-08-31, Mark Fletcher  wrote:
> > > By participating in this list you implicitly agree to abide by the code
> > > of conduct; authority is not granted to you to decide which parts of it
> > > you will abide by and which not.
> >
> > How about postings in HTML as a case in point of egregious violation?
>
> Purely factually, it was in multipart-alternative.  I hadn't even noticed
> that my nice plain text display was attched to the possibility of
> displaying HTML.
>
> Lisi

And I did try to check - unsuccessfully, sorry :-(  :-( -  that my email 
client hadn't followed suit.  It is the one serious weakness of KMail-Trinity 
that it sometimes copies HTML, when it has not displayed it in a way that 
meant  that one knew that it was there.

I hope that I have succeeded in getting rid of it this time.

Lisi

Re: Jessie (8.0) slow to boot

[Richard Owlett]

On 8/31/2016 10:44 AM, Felix Miata wrote:

Richard Owlett composed on 2016-08-31 09:58 (UTC-0500):
...

Aug 31 09:13:32 deb8-2ndtry systemd[1]: Job
dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x2daf89\x2d33ba51934630.de

Aug 31 09:13:32 deb8-2ndtry systemd[1]: Timed out waiting for
device dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x
Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for
/dev/disk/by-uuid/0a344714-ae06-43ed-af89-33ba5193463
Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for
Swap.


Which was installed last, Squeeze, or Jessie? You can expect this
message trying to boot the earlier installed installation after
having done the later install. Unless you take affirmative action
to deny it, an existing swap partition used by the earlier
installation will be reformatted by the later installation.
Reformatting creates a new UUID, thus making the UUID referring
to it in the earlier installation's fstab invalid. The earlier
needs to have its fstab edited to use the correct swap partition
UUID, or volume label, or device name, if swap is actually
desired or needed.


There may be some subtle problems still lurking somewhere which 
show up only for people like me doing many installs of *nearly* 
identical systems.


Commenting out the line in /etc/fstab DID allow it to boot 
without warning messages.


However,taking into account Darac's comments, does this now mean 
that the machines are now operating without a swap partition?


IIRC the current instance of Jessie on the laptop was the 
chronologically the last OS installed so by the comments in this 
thread should not have had the problem. The laptop is my 
designated "Guinea pig" so I'll do a fresh install to see if 
problem persists.

Re: Jessie (8.0) slow to boot

[Dominic Knight]

On Wed, 2016-08-31 at 10:24 -0400, Greg Wooledge wrote:
> On Wed, Aug 31, 2016 at 09:16:00AM -0500, Richard Owlett wrote:
> > 
> > What's going on?
> > Are the messages that scroll past preserved anywhere?
> 
> When booting with systemd, the boot messages are stored in RAM
> automatically, and can be viewed by running "journalctl" as root.
> I'd definitely start there.

If it is the swap partition, it has probably been given a new UUID when
you installed a new/additional version of Debian. I use gparted to look
up the current UUID and then paste that over the relevant UUID in
/etc/fstab
Take care when using both gparted and writing to fstab.

Regards.

Re: Decentralized reliable instant messaging?

[Lisi Reisz]

On Wednesday 31 August 2016 17:01:36 Curt wrote:
> On 2016-08-31, Mark Fletcher  wrote:
> > By participating in this list you implicitly agree to abide by the code
> > of conduct; authority is not granted to you to decide which parts of it
> > you will abide by and which not.
>
> How about postings in HTML as a case in point of egregious violation?

Purely factually, it was in multipart-alternative.  I hadn't even noticed that 
my nice plain text display was attched to the possibility of displaying HTML.

Lisi

Re: Jessie (8.0) slow to boot

[Greg Wooledge]

On Wed, Aug 31, 2016 at 11:00:27AM -0500, Richard Owlett wrote:
> On 8/31/2016 10:06 AM, Greg Wooledge wrote:
> >Look for swap partitions defined in /etc/fstab and see if one of them
> >is on a device that no longer exists (or exists only intermittently,
> >such as a removable USB drive).  Chances are you'll find one with
> >UUID=0a344714-something on it.  Try commenting it out.
> 
> Commented out relevant line on both machines.
> They both boot promptly now ;/

OK, good.  Now the final step is to review your fstab vs. your actual
disk partitions and add whatever you may be missing (e.g. a swap
partition whose UUID got changed, as someone else speculated).

Re: Decentralized reliable instant messaging?

[Curt]

On 2016-08-31, Mark Fletcher  wrote:
>
>>
> By participating in this list you implicitly agree to abide by the code of
> conduct; authority is not granted to you to decide which parts of it you
> will abide by and which not.
>

How about postings in HTML as a case in point of egregious violation?

-- 
"I always say to people, ‘No one earns $100 million. You steal $100 million.’
People earn $10 an hour. People earn $40,000 a year. ‘Earn’ means work. Okay?
It doesn’t mean steal, which with these vast amounts of money, of course you
steal them." — Fran Lebowitz

Re: Jessie (8.0) slow to boot

[Richard Owlett]

On 8/31/2016 10:06 AM, Greg Wooledge wrote:

On Wed, Aug 31, 2016 at 09:58:39AM -0500, Richard Owlett wrote:

Aug 31 09:13:32 deb8-2ndtry systemd[1]: Job
dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x2daf89\x2d33ba51934630.de
Aug 31 09:13:32 deb8-2ndtry systemd[1]: Timed out waiting for
device dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x
Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for
/dev/disk/by-uuid/0a344714-ae06-43ed-af89-33ba5193463
Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for Swap.


Look for swap partitions defined in /etc/fstab and see if one of them
is on a device that no longer exists (or exists only intermittently,
such as a removable USB drive).  Chances are you'll find one with
UUID=0a344714-something on it.  Try commenting it out.



Commented out relevant line on both machines.
They both boot promptly now ;/
Thanks

Re: Jessie (8.0) slow to boot

[Felix Miata]

Richard Owlett composed on 2016-08-31 09:58 (UTC-0500):
...

Aug 31 09:13:32 deb8-2ndtry systemd[1]: Job
dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x2daf89\x2d33ba51934630.de
Aug 31 09:13:32 deb8-2ndtry systemd[1]: Timed out waiting for
device dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x
Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for
/dev/disk/by-uuid/0a344714-ae06-43ed-af89-33ba5193463
Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for Swap.


Which was installed last, Squeeze, or Jessie? You can expect this message 
trying to boot the earlier installed installation after having done the later 
install. Unless you take affirmative action to deny it, an existing swap 
partition used by the earlier installation will be reformatted by the later 
installation. Reformatting creates a new UUID, thus making the UUID referring 
to it in the earlier installation's fstab invalid. The earlier needs to have 
its fstab edited to use the correct swap partition UUID, or volume label, or 
device name, if swap is actually desired or needed.

--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Security Updates

[Larry Dighera]

On Wed, 31 Aug 2016 14:19:15 +0100, Lisi Reisz  wrote:

>On Wednesday 31 August 2016 10:39:53 Lisi Reisz wrote:
>> Since you are not replying to anyhting, you may not be subscribed,
>
>I had a reply off list that said that Larry is not replying to our questions 
>because he considers them irrelevant to his original question.
>
>Lisi


Of course, that is not what I said at all.  

Here is a copy of the message I sent to Lisi:

-
To: Lisi Reisz 
Subject: Re: Security Updates
From: Larry Dighera 
Date: Wed, 31 Aug 2016 06:09:27 -0700

On Wed, 31 Aug 2016 10:39:53 +0100, Lisi Reisz  wrote:

>Since you are not replying to anyhting, you may not be subscribed, so here is 
>what I said again:
>
>On Tuesday 30 August 2016 20:58:47 Larry Dighera wrote:
>> This page  states:
>>
>> "If you use APT, add the following line to /etc/apt/sources.list to be
>> able to access the latest security updates:
>>
>> deb http://security.debian.org/ jessie/updates main contrib non-free
>>
>> After that, run apt-get update followed by apt-get upgrade."
>>
>> Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running
>> Debian Jessie results in an error message indicating that the public key is
>> not found. It also finds two libraries that require updating that are not
>> found when the above mentioned /etc/apt/sources.list entry is removed.
>>
>>   1.  What do I need to do to prevent the error message?
>>
>>   2.  As there are other security related URLs (doubtless, as
>>   distributed/released) that are checked during apt-get update, is the
>>   recommended additional entry advisable/useful for this platform?
>
>What is the whole of your sources.list?
>
>Lisi
>
>Like other respondents I suspect that you are using Raspbian not Debian.  Your 
>sources list will tell me/us, or guide us ot teh problem if it is not that.


I'm sorry.  I didn't find your question relevant to my question about the
Debian.org web site providing instructions that produce error messages, and
politely ignored it.  
---


For those who may be following this message thread, here is the output from
'apt-get update' with the offending 'deb-src
http://archive.raspbian.org/raspbian/ jessie main contrib non-free rpi
' entry edited into the /etc/apt/sources.list as instructed on this page:
:

-
Get:1 http://security.debian.org jessie/updates InRelease [63.1 kB]
Hit http://mirrordirector.raspbian.org jessie InRelease
Hit http://archive.raspberrypi.org jessie InRelease
Ign http://security.debian.org jessie/updates InRelease
Hit http://mirrordirector.raspbian.org jessie/main armhf Packages
Ign http://linux.teamviewer.com stable InRelease
Get:2 http://security.debian.org jessie/updates/main armhf Packages [292 kB]
Hit http://archive.raspberrypi.org jessie/main armhf Packages
Ign http://linux.teamviewer.com preview InRelease
Hit http://mirrordirector.raspbian.org jessie/contrib armhf Packages
Hit http://archive.raspberrypi.org jessie/ui armhf Packages
Hit http://mirrordirector.raspbian.org jessie/non-free armhf Packages
Get:3 http://security.debian.org jessie/updates/contrib armhf Packages [1,138
B]
Hit http://linux.teamviewer.com stable Release.gpg
Hit http://mirrordirector.raspbian.org jessie/rpi armhf Packages
Get:4 http://security.debian.org jessie/updates/non-free armhf Packages [14 B]
Get:5 http://security.debian.org jessie/updates/contrib Translation-en [1,211
B]
Hit http://linux.teamviewer.com stable Release
Hit http://linux.teamviewer.com preview Release.gpg
Get:6 http://security.debian.org jessie/updates/main Translation-en [161 kB]
Hit http://linux.teamviewer.com stable/main armhf Packages
Get:7 http://security.debian.org jessie/updates/non-free Translation-en [14 B]
Hit http://linux.teamviewer.com preview Release
Hit http://linux.teamviewer.com preview/main armhf Packages
Ign http://security.debian.org jessie/updates/contrib Translation-en_GB
Ign http://security.debian.org jessie/updates/main Translation-en_GB
Ign http://security.debian.org jessie/updates/non-free Translation-en_GB
Ign http://archive.raspberrypi.org jessie/main Translation-en_GB
Ign http://archive.raspberrypi.org jessie/main Translation-en
Ign http://archive.raspberrypi.org jessie/ui Translation-en_GB
Ign http://archive.raspberrypi.org jessie/ui Translation-en
Ign http://linux.teamviewer.com stable/main Translation-en_GB
Ign http://linux.teamviewer.com stable/main Translation-en
Ign http://linux.teamviewer.com preview/main Translation-en_GB
Ign http://linux.teamviewer.com preview/main Translation-en
Ign http://mirrordirector.raspbian.org jessie/contrib Translation-en_GB
Ign 

Re: Decentralized reliable instant messaging?

[Nicolas George]

Le quintidi 15 fructidor, an CCXXIV, Lisi Reisz a écrit :
> But it doesn't prevent Nicolas from deliberately cc-ing most of the rest of 
> us 
> when replying to our mails; which is exceedingly annoying and is NOT in 
> compliance with the CoC.

I do not "deliberately" cc anyone most of the time, I just obey the messages
headers. You can set up the messages headers to avoid receiving the
extraneous copies from anyone, including me, with a simple configuration
option that I have already explained, to you personally.

Not following advice is of course your absolute right.

> It is, of course, and annoyance one can easily avoid by blacklisting him.

Indeed. Please feel free to blacklist anyone.


signature.asc
Description: Digital signature

Re: Security Updates

[Lisi Reisz]

On Wednesday 31 August 2016 16:16:45 Larry Dighera wrote:
> Have you even looked at the information here:
> ?  After reading
> that announcement, how can you continue to insist that I am not running
> Debian Jessie?

That page (URL) confirms what most of us have suspected all along.  You are 
running Raspbian Jessie, not Debian Jessie.  It says:  
/blog/*raspbian*-jessie-is-here  (my stars)

Lisi

Re: Decentralized reliable instant messaging?

[Lisi Reisz]

On Wednesday 31 August 2016 15:45:42 Mark Fletcher wrote:
> Well and
> good -- actually, very good, because it prevents me making the stupid
> mistake I frequently make of cc-ing the poster of the mail I am replying
> to.

But it doesn't prevent Nicolas from deliberately cc-ing most of the rest of us 
when replying to our mails; which is exceedingly annoying and is NOT in 
compliance with the CoC.

It is, of course, and annoyance one can easily avoid by blacklisting him.

Lisi

Re: Security Updates

[Greg Wooledge]

On Wed, Aug 31, 2016 at 08:16:45AM -0700, Larry Dighera wrote:
> Have you even looked at the information here:
> ?  After reading
> that announcement, how can you continue to insist that I am not running Debian
> Jessie?  

1) It's not on a Debian web site.  It's on someone else's web site.
   Imagine if I posted a link from www.microsoft.com that said
   "Debian is on the decline; switch to Windows 10".  Would you
   consider that an authoritative statement about Debian?

2) It says "The Raspbian operating system is based on Debian Linux,
   and the different versions of Debian are named after characters
   from the Toy Story films. Recent versions of Raspbian have
   been based on Debian Wheezy (the penguin who's lost his squeaker
   in Toy Story 2), but Raspbian has now been updated to the new
   stable version of Debian, which is called Jessie."

Note that it says "based on Debian".  It isn't Debian.  It's a derivative.

Attempting to use security packages from Debian on a derivative system
(which is *not* Debian) may not work properly.  To get the correct
security packages for your system, you need to talk to the Raspbian folks,
not the Debian folks.

Re: Dúvida com DNS Slave

[Henrique Fagundes]

Lucas,

Desde já obrigado por responder.
Existe alguma maneira de desabilitar isso?

Atenciosamente,

Henrique Fagundes
henri...@linuxadmin.com.br
Skype: magnata-br-rj
Linux User: 475399

http://www.aprendendolinux.com/
http://www.facebook.com/PortalAprendendoLinux
http://youtube.com/aprendendolinux/
http://twitter.com/aprendendolinux/
__
Participe do Grupo Aprendendo Linux
https://groups.google.com/forum/#!forum/portal-aprendendo-linux

Ou envie um e-mail para:
portal-aprendendo-linux+subscr...@googlegroups.com

Em 30/08/2016 20:39, Lucas Castro escreveu:

Não é criptografia, a partir da versão 9.9 o bind usa formato raw.

https://kb.isc.org/article/AA-00608/0/Converting-Zone-Files-Between-Text-and-Raw-Formats.html


On 30-08-2016 17:33, Henrique Fagundes wrote:

Amigo,

NS1 - Debian - 9.9.5
NS2 - Ubuntu - 9.9.5
NS3 - CentOS - 9.8.2-0.47

Abraços.

Atenciosamente,

Henrique Fagundes
henri...@linuxadmin.com.br
Skype: magnata-br-rj
Linux User: 475399

http://www.aprendendolinux.com/
http://www.facebook.com/PortalAprendendoLinux
http://youtube.com/aprendendolinux/
http://twitter.com/aprendendolinux/
__
Participe do Grupo Aprendendo Linux
https://groups.google.com/forum/#!forum/portal-aprendendo-linux

Ou envie um e-mail para:
portal-aprendendo-linux+subscr...@googlegroups.com

Em 30/08/2016 17:23, Rodrigo Cunha escreveu:

Cara, qual é a versão do bind dos DNS.
Deduzo que o debian e o ubuntu, quando instalado por apt-get install
implementam um ambiente homologado em seus arquivos de configuração ou
modulos de criptografia.
É possivel que a instalação dos arquivos rpm, homologados pela red hat e
implementados pelo yum install, não sejam homologados com criptografia.
É uma hipotese plausivel...

Em 30 de agosto de 2016 17:06, Henrique Fagundes
>
escreveu:

Prezados Colegas,

Primeiramente saudações pinguianas a todos.
Tenho o seguinte cenário:

NS1 - Debian - Servidor de DNS Master
NS2 - Ubuntu Server - Servidor de DNS Slave 1
NS2 - CentOS 6 - Servidor de DNS Slave 2.

Tudo está funcionando muito bem, porém a minha única dúvida é o
seguinte.

Quando o arquivo db.dominio.com.br  do NS1
é transferido para o o diretório /var/cache/bind/ do NS2, ele chega
"criptografado". Quando dou um "cat" no arquivo, ele mostra a saída
toda "truncada", quase que ilegível.

Funciona de boa, eu faço pesquisas com o comando "dig" e o servidor
me mostra os DNSs corretamente.

Porém, eu gostaria que o arquivo não ficasse criptografado.

No NS3 o arquivo chega aberto, totalmente legível.

Alguém sabe o que eu posso fazer para evitar isso?

Abraços.

Atenciosamente,

Henrique Fagundes
henri...@linuxadmin.com.br 
Skype: magnata-br-rj
Linux User: 475399

http://www.aprendendolinux.com/ 
http://www.facebook.com/PortalAprendendoLinux

http://youtube.com/aprendendolinux/

http://twitter.com/aprendendolinux/


__
Participe do Grupo Aprendendo Linux
https://groups.google.com/forum/#!forum/portal-aprendendo-linux


Ou envie um e-mail para:
portal-aprendendo-linux+subscr...@googlegroups.com





--
Atenciosamente,
Rodrigo da Silva Cunha

Re: Security Updates

[Larry Dighera]

On Wed, 31 Aug 2016 13:28:21 +, "Andrew M.A. Cater"
 wrote:

>On Wed, Aug 31, 2016 at 06:04:34AM -0700, Larry Dighera wrote:
>> On Tue, 30 Aug 2016 20:44:27 +, "Andrew M.A. Cater"
>>  wrote:
>> 
>> >On Tue, Aug 30, 2016 at 12:58:47PM -0700, Larry Dighera wrote:
>> >> 
>> >> This page  states:
>> >> 
>> >> "If you use APT, add the following line to /etc/apt/sources.list to 
>> >> be able
>> >> to access the latest security updates:
>> >> 
>> >> deb http://security.debian.org/ jessie/updates main contrib non-free
>> >> 
>> >> After that, run apt-get update followed by apt-get upgrade."
>> >> 
>> >> Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running 
>> >> Debian
>> >> Jessie results in an error message indicating that the public key is not 
>> >> found.
>> >> It also finds two libraries that require updating that are not found when 
>> >> the
>> >> above mentioned /etc/apt/sources.list entry is removed.
>> >> 
>> >>   1.  What do I need to do to prevent the error message?
>> >> 
>> >>   2.  As there are other security related URLs (doubtless, as
>> >>   distributed/released) that are checked during apt-get update, is the
>> >>   recommended additional entry advisable/useful for this platform?
>> >
>> >Debian or Raspbian?
>> >
>> >If Raspbian - that's based very closely on Debian but isn't strictly Debian.
>> >
>> >Mixing the two might not be a good idea since there will probably be 
>> >incompatibilities at some level.
>> >
>> >There is a port of pure Debian to the Pi 2 - look on the Debian wiki - but 
>> >no one has yet done this for the Pi 3 as far as I know.
>> >
>> >[The original Pi required different compilation options to cope with 
>> >floating point "stuff" which rendered Debian incompatible:
>> >Raspbian is a re-compilation to suit the Raspberry Pi. Pi 2 is ARM v7 with 
>> >hardware floating point. Pi 3 is 64 bit core (so arm64 would work if
>> >the Pi folk hadn't put in 32 bit glue logic or thereabouts). There are also 
>> >issues with the way of loading the operating system, initialising video
>> >and non-free firmware which can cause problems.]
>> >
>> >All the best,
>> >
>> >AndyC
>> 
>> 
>> 
>> Hello Andy,
>> 
>> I thought I made it clear that the OS was Debian Jessie.  It was installed 
>> from
>> the NOOBS release: .  As you 
>> can
>> see from this article
>> , Debian Jessie 
>> was
>> released for the Raspberry Pi platform almost a year ago, September 2015.  
>> 
>> Have you any insight into how to overcome the ;public key not found; error
>> message adding that security repository to the apt list, as stated on the
>> Debian.org web site, may be resolved?
>> 
>> Thank you for your response.
>> 
>> Best regards,
>> Larry
>>
>
>Hi Larry, 
>
>That's Raspbian - NOOBS installs Raspbian.
>
>As Lisi Reisz has stated to you in another email: Raspbian handle their own 
>security updates.
>
>If you want to add the keys to the Debian security updates repository you can 
>use an apt-key add command and the key available from 
>http://ftp-master.debian.org/keys.html
>[The main archive signing key is also used to sign the security updates].
>
>Be aware that you might create problems for yourself.
>
>You may well want to look at the Debian Administrators handbook - you can try 
>apt-get install debian-handbook if the package is also available for Raspbian.
>
>Hope this helps,
>
>Al the very best,
>
>AndyC 
>
>[Copying to the list as this may be of more use more widely]


Hello Andy,

Have you even looked at the information here:
?  After reading
that announcement, how can you continue to insist that I am not running Debian
Jessie?  

I appreciate your pointer to adding keys to the Debian security updates
repository with apt-key add.  I will look into that, however if it were
necessary for me to do that manually, I would have expected the
 page to have mentioned it
explicitly.  Perhaps I expect too much...

I find the stability of the Debian APT system to be one of the most valuable
aspects of Debian Linux, compared to other less stable distributions I have
encountered over the years.  So I am wary of doing anything to break it, even
if it proffered on a Debian web page, as you cautioned.  

Thank you for sharing your knowledge.

Best regards,
Larry

Re: Jessie (8.0) slow to boot

[Greg Wooledge]

On Wed, Aug 31, 2016 at 09:58:39AM -0500, Richard Owlett wrote:
> Aug 31 09:13:32 deb8-2ndtry systemd[1]: Job 
> dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x2daf89\x2d33ba51934630.de
> Aug 31 09:13:32 deb8-2ndtry systemd[1]: Timed out waiting for 
> device dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x
> Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for 
> /dev/disk/by-uuid/0a344714-ae06-43ed-af89-33ba5193463
> Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for Swap.

Look for swap partitions defined in /etc/fstab and see if one of them
is on a device that no longer exists (or exists only intermittently,
such as a removable USB drive).  Chances are you'll find one with
UUID=0a344714-something on it.  Try commenting it out.

Re: Jessie (8.0) slow to boot

[Darac Marjal]

On Wed, Aug 31, 2016 at 09:16:00AM -0500, Richard Owlett wrote:
I have Jessie installed on a desktop and a laptop. They both take 
about 105-110 seconds to boot. Squeeze on the desktop takes ~15 
seconds to boot.


Most of the delay seems to be in something that states approximately
"A start job is running for dev-disk-by\x2duuid?.device (t}"
Where ? is a long alphanumeric string
 t is a timer display
That is followed by two message identified as "Warning" in bright 
yellow.[they pass by to fast to read].


What's going on?


UUID is considered to be the most reliable way to locate a disk, given 
modern kernels' asynchronous device discovery. It is no longer 
considered "safe" to assume that /dev/sda is your main hard drive. On 
small systems, it probably won't change, but if you have several drives, 
they can start at different times, and the order in which they get 
enumerated may change. Therefore, Linux now tends to refer to disks by 
UUID (Universally Unique IDentifier). The boot process now involves 
various methods for finding that UUID and, as you see above, waiting 
some considerable time for the device to appear (the device might be 
dependant on another host, or it might be on a relatively slow bus such 
as USB or SCSI-1 etc)


Now, there are a number of reasons why you might get the messages above, 
but one common 'gotcha' is that systemd is more strict about what 
devices are needed to boot the system. Basically, systemd assumes that, 
if you've listed a device in /etc/fstab and you've not told it 
otherwise, then that device is necessary for the system to boot. The two 
main ways to disabuse it of this notion are to either add the option 
"noauto", in which case the device will not get mounted at boot but you 
can still invoke "mount /path/to/mountpoint" once the system is up, or 
else you can add the option "nofail" which tells systemd that a failure 
to mount the device should not lead to a failure of the service (and 
thus booting can continue).


Another reason, and this may well be something you're hitting, is that 
the UUID doesn't match any devices on the system. UUIDs are, typically, 
created by mkfs (or mkswap). If you reformat a partition, the UUID will 
probably change, and your /etc/fstab might be pointing to the old 
device. If, say, you create filesystems and restore a backup to them, 
then /etc/fstab can be pointing to UUIDs which no longer exist; if 
that's the case, then consider using LABEL=something in /etc/fstab 
instead. UUIDs are reliable, but they are computer generated. Sometimes 
a maintainer-generated identifier is better.



Are the messages that scroll past preserved anywhere?
TIA




--
For more information, please reread.


signature.asc
Description: PGP signature

Re: Jessie (8.0) slow to boot

[Richard Owlett]

On 8/31/2016 9:24 AM, Greg Wooledge wrote:

On Wed, Aug 31, 2016 at 09:16:00AM -0500, Richard Owlett wrote:

What's going on?
Are the messages that scroll past preserved anywhere?


When booting with systemd, the boot messages are stored in RAM
automatically, and can be viewed by running "journalctl" as root.
I'd definitely start there.



The relevant section appears to be

Aug 31 09:12:11 deb8-2ndtry kernel: psmouse serio2: alps: Unknown 
ALPS touchpad: E7=10 00 64, EC=10 00 64
Aug 31 09:12:13 deb8-2ndtry kernel: psmouse serio2: trackpoint: 
IBM TrackPoint firmware: 0x0e, buttons: 3/3
Aug 31 09:12:13 deb8-2ndtry kernel: input: TPPS/2 IBM TrackPoint 
as /devices/platform/i8042/serio1/serio2/input/inp
Aug 31 09:13:32 deb8-2ndtry systemd[1]: Job 
dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x2daf89\x2d33ba51934630.de
Aug 31 09:13:32 deb8-2ndtry systemd[1]: Timed out waiting for 
device dev-disk-by\x2duuid-0a344714\x2dae06\x2d43ed\x
Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for 
/dev/disk/by-uuid/0a344714-ae06-43ed-af89-33ba5193463

Aug 31 09:13:32 deb8-2ndtry systemd[1]: Dependency failed for Swap.
Aug 31 09:13:33 deb8-2ndtry anacron[493]: Anacron 2.3 started on 
2016-08-31

Aug 31 09:13:33 deb8-2ndtry anacron[493]: Normal exit (0 jobs run)

What is this trying to tel me?
Where could I have gone to find answer to above?

Re: Decentralized reliable instant messaging?

[Mark Fletcher]

On Wed, Aug 31, 2016 at 11:11 PM Nicolas George  wrote:

> Le quartidi 14 fructidor, an CCXXIV, David Wright a écrit :
> This clause of the code of conduct is unsustainable, and therefore should
> be
> ignored until the configuration is fixed and the corresponding clause
> updated.
>
>
By participating in this list you implicitly agree to abide by the code of
conduct; authority is not granted to you to decide which parts of it you
will abide by and which not.

You're in compliance by doing something not everyone agrees with but which
looks harmless to me. The result is that when I hit Reply-all to this
thread, my mail client automatically replied only to the list. Well and
good -- actually, very good, because it prevents me making the stupid
mistake I frequently make of cc-ing the poster of the mail I am replying
to. So no arguments with your chosen actions from me. But I don't
particularly wish to hear you advocating for ignoring the code of conduct,
or any part of it, any more, and I very much doubt I am alone.

Mark

Re: Security Updates

[Mark Fletcher]

On Wed, Aug 31, 2016 at 10:18 PM Lisi Reisz  wrote:

> On Wednesday 31 August 2016 10:39:53 Lisi Reisz wrote:
> > Since you are not replying to anyhting, you may not be subscribed,
>
> I had a reply off list that said that Larry is not replying to our
> questions
> because he considers them irrelevant to his original question.
>
> Lisi
>
>
Thus demonstrating the pitfalls of assuming one knows more / is a better
judge of relevance than the people one is seeking help from...!

Mark

Re: Jessie (8.0) slow to boot

[Greg Wooledge]

On Wed, Aug 31, 2016 at 09:16:00AM -0500, Richard Owlett wrote:
> What's going on?
> Are the messages that scroll past preserved anywhere?

When booting with systemd, the boot messages are stored in RAM
automatically, and can be viewed by running "journalctl" as root.
I'd definitely start there.

Jessie (8.0) slow to boot

[Richard Owlett]

I have Jessie installed on a desktop and a laptop. They both take 
about 105-110 seconds to boot. Squeeze on the desktop takes ~15 
seconds to boot.


Most of the delay seems to be in something that states approximately
"A start job is running for dev-disk-by\x2duuid?.device (t}"
Where ? is a long alphanumeric string
  t is a timer display
That is followed by two message identified as "Warning" in bright 
yellow.[they pass by to fast to read].


What's going on?
Are the messages that scroll past preserved anywhere?
TIA

Re: Decentralized reliable instant messaging?

[Nicolas George]

Le quartidi 14 fructidor, an CCXXIV, David Wright a écrit :
> The error might have been mine. I think I CC'd Lisi in error.
> The other list I'm on expects people to group-reply.
> I forgot myself.

Systematic group-reply is the correct way of using mailing-lists, because it
is the only way that does not require the user to waste time for each mail
deciding the proper key to hit.

This clause of the code of conduct is unsustainable, and therefore should be
ignored until the configuration is fixed and the corresponding clause
updated.

In the meantime, let the whiners whine; the non-whiners can unilaterally fix
things for themselves by setting the reply-to header, just like you or me.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: Jessie live booting at 32 bit uefi PC ?

[Mark Fletcher]

On Wed, Aug 31, 2016 at 4:30 PM Hyeonjin Oh  wrote:

> Hi Thomas Schmitt, Thank you for fast feedback.
>
> Have good day.
>
> I can confirm recent experience, live CD couldn't boot UEFI but netinst
could. I used live CD to boot a new machine and build LFS until the grub
installation stage, when I discovered I couldn't install grub in UEFI mode
because none of the UEFI kernel "stuff" was available, so then I had to
boot netinst in UEFI mode, do a minimal Debian install to another USB key,
boot THAT, and use that to install grub on the disk of the machine
concerned, so I could get it to boot UEFI without re-doing the entire
installation of LFS. Live is great in all respects except that one.

I've got to think UEFI capability on the live images can't be far away,
since the netinst can already do it, and the number of machines that need
legacy boot is dwindling all the time (although still large, I'll warrant)
and there's a disturbing trend of new machines coming out with no legacy
compatibility mode.

Mark

Re: postfix mail filtering

[Dan Ritter]

On Wed, Aug 31, 2016 at 01:21:13PM +0100, Tony van der Hoff wrote:
> Hi list,
> 
> I'm running postfix under Wheezy on my VPS, using a more or less
> out-of-the-box configuration. My users access their mail via IMAP.
> 
> I subscribe to a number of mail lists, such as this one. I currently use
> Thunderbird's filtering capability to sort mail into a number of
> subdirectories within my inbox, which works fine, but requires me to set up
> all my workstayions (laptop, home, work) with the same filters. I have now
> acquired an Android smartphone, which has no filtering capability. In any
> case, keeping a number of workstations in sync is a pain.
> 
> So, I'd like to perform the filtering on the server (for my user initially,
> then perhaps for others). My extensive googling reveals that there are many
> tutorials for filtering spam, but that's not really my problem.
> 
> I can't find any tutorials on how to set up filters based on, say subject:,
> from:, or to: fields, but feel certain such must exist.
> Can any kind person direct me to a suitable tutorial, please?

You can use:

- sieve, a language for controlling filtering on IMAP servers.
  Supported by Thunderbird but not very much else.

- procmail, a language for filtering on delivery (postfix will
  call it) -- widely known, but arcane syntax and requires shell 
  access to edit or place the ~/.procmailrc

- maildrop, aka mailfilter, a language for filtering on delivery
  (postfix will call it, too) -- less widely known, but has
  syntax that is much more readable than procmail. Requires
  shell access to place a ~/.mailfilter file.

All of these have Debian packages.

-dsr-

Re: Decentralized reliable instant messaging?

[Stefan Monnier]

> It's better that your message Not arrive instead of being disclose! and
> This is the philosophy behind True P2P IM systems.

Oh, I don't need 100% absolutely guaranteed delivery.

Just some reasonable expectation that messages won't be silently dropped
on the floor in fairly normal circumstances.

E.g. some email messages just don't get delivered, for instance because
they're misflagged as spam, but I still consider email as "reliable".

As a counter example, XMPP silently drops messages in various normal
circumstances, which XEP-0198 tries to address, similarly SIP tends to
drop messages on the floor if the destination is not currently
connected.  Another problem with XMPP is when you use several clients,
in which case not all clients will necessarily see all messages.

As another example, BitMessage's approach of keeping messages for
2 days, together with some way for the sender to know if the message has
been received, seems good enough.


Stefan


> On Tue, Aug 30, 2016 at 1:05 PM, Stefan Monnier 
> wrote:

>> > You can't have all the best together.
>> 
>> What does that mean, exactly?  Are you saying it doesn't have reliable
>> message delivery?  If so, that'd be a deal breaker for me.
>> 
>> 
>> Stefan "shocked that anyone would want to design or use an
>> unreliable messaging system"
>> 
>> 
>> > This mention in previous E-Mails as well. E.g:
>> <20160817192400.GB9964@alum>
>> 
>> > On Thu, Aug 25, 2016 at 6:00 PM, Stefan Monnier <
>> monn...@iro.umontreal.ca>
>> > wrote:
>> 
>> >> > I think you looking for TOX!
>> >> > Visit TOX Project website:
>> >> > https://tox.chat
>> >>
>> >> Thanks.  That does look promising (although I don't see any mention of
>> >> reliable delivery),
>> >>
>> >>
>> >> Stefan
>> >>
>> >>
>> >> > On Sat, Aug 13, 2016 at 7:19 AM, Stefan Monnier <
>> >> monn...@iro.umontreal.ca>
>> >> > wrote:
>> >>
>> >> >> I'm looking for a decentralized instant message system (e.g. XMPP,
>> SIP,
>> >> >> ...) where I can be sure that I receive all messages, even if I'm not
>> >> >> connected when the message is sent [ Obviously, I'll only receive
>> them
>> >> >> when I'm back online.  ]
>> >> >>
>> >> >> IIUC there is some XMPP features that allow such reliable delivery,
>> but
>> >> >> it seems that it's not widely supported by clients.  What Debian
>> >> >> clients, using which protocols, can provide reliable instant
>> messaging?
>> >> >>
>> >> >>
>> >> >> Stefan
>> >> >>
>> >> >>
>> >> >> PS: Bonus points if that feature is also available on an Android
>> >> >> application that's Free Software.
>> >> >>
>> >> >>
>> >>
>> 

Re: Security Updates

[Darac Marjal]

On Tue, Aug 30, 2016 at 12:58:47PM -0700, Larry Dighera wrote:


This page  states:

   "If you use APT, add the following line to /etc/apt/sources.list to be able
   to access the latest security updates:

   deb http://security.debian.org/ jessie/updates main contrib non-free

   After that, run apt-get update followed by apt-get upgrade."

Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running Debian
Jessie results in an error message indicating that the public key is not found.
It also finds two libraries that require updating that are not found when the
above mentioned /etc/apt/sources.list entry is removed.


As other people are discussing how to avoid the problems, let me have a 
go at answering your questions directly.




 1.  What do I need to do to prevent the error message?


Check that "debian-archive-keyring" is installed. If that is showing as 
untrusted as well, then read https://ftp-master.debian.org/keys.html.  
Note the warning at the top, though: "Please note that the details here 
are for information only, you should not rely on them and use other ways 
to verify them."




 2.  As there are other security related URLs (doubtless, as
 distributed/released) that are checked during apt-get update, is the
 recommended additional entry advisable/useful for this platform?


If you're running Debian, then that line should provide all the security 
updates you require. If you've added other repositories, though (PPAs, 
for example, or if you're using a debian-derived distribution such as 
Ubuntu, Mint, Devuan etc), then you should consult THOSE projects 
individually to see if they provide security updates (they may simply 
provide a rolling "bleeding edge" update model instead).






--
For more information, please reread.


signature.asc
Description: PGP signature

Re: Decentralized reliable instant messaging?

[Henning Follmann]

On Wed, Aug 31, 2016 at 01:14:08PM +, Amir H. Firouzian wrote:
> 
[...]


> About you last sentence:
> It's better that your message Not arrive instead of being disclose! and
> This is the philosophy behind True P2P IM systems.

Getting offtopic here. However, please elaborate why this is better?
Is there some fundamental law behind your rational?

-H

-- 
Henning Follmann   | hfollm...@itcfollmann.com

Re: Security Updates

[Andrew M.A. Cater]

On Wed, Aug 31, 2016 at 06:04:34AM -0700, Larry Dighera wrote:
> On Tue, 30 Aug 2016 20:44:27 +, "Andrew M.A. Cater"
>  wrote:
> 
> >On Tue, Aug 30, 2016 at 12:58:47PM -0700, Larry Dighera wrote:
> >> 
> >> This page  states:
> >> 
> >> "If you use APT, add the following line to /etc/apt/sources.list to be 
> >> able
> >> to access the latest security updates:
> >> 
> >> deb http://security.debian.org/ jessie/updates main contrib non-free
> >> 
> >> After that, run apt-get update followed by apt-get upgrade."
> >> 
> >> Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running 
> >> Debian
> >> Jessie results in an error message indicating that the public key is not 
> >> found.
> >> It also finds two libraries that require updating that are not found when 
> >> the
> >> above mentioned /etc/apt/sources.list entry is removed.
> >> 
> >>   1.  What do I need to do to prevent the error message?
> >> 
> >>   2.  As there are other security related URLs (doubtless, as
> >>   distributed/released) that are checked during apt-get update, is the
> >>   recommended additional entry advisable/useful for this platform?
> >
> >Debian or Raspbian?
> >
> >If Raspbian - that's based very closely on Debian but isn't strictly Debian.
> >
> >Mixing the two might not be a good idea since there will probably be 
> >incompatibilities at some level.
> >
> >There is a port of pure Debian to the Pi 2 - look on the Debian wiki - but 
> >no one has yet done this for the Pi 3 as far as I know.
> >
> >[The original Pi required different compilation options to cope with 
> >floating point "stuff" which rendered Debian incompatible:
> >Raspbian is a re-compilation to suit the Raspberry Pi. Pi 2 is ARM v7 with 
> >hardware floating point. Pi 3 is 64 bit core (so arm64 would work if
> >the Pi folk hadn't put in 32 bit glue logic or thereabouts). There are also 
> >issues with the way of loading the operating system, initialising video
> >and non-free firmware which can cause problems.]
> >
> >All the best,
> >
> >AndyC
> 
> 
> 
> Hello Andy,
> 
> I thought I made it clear that the OS was Debian Jessie.  It was installed 
> from
> the NOOBS release: .  As you can
> see from this article
> , Debian Jessie was
> released for the Raspberry Pi platform almost a year ago, September 2015.  
> 
> Have you any insight into how to overcome the ;public key not found; error
> message adding that security repository to the apt list, as stated on the
> Debian.org web site, may be resolved?
> 
> Thank you for your response.
> 
> Best regards,
> Larry
>

Hi Larry, 

That's Raspbian - NOOBS installs Raspbian.

As Lisi Reisz has stated to you in another email: Raspbian handle their own 
security updates.

If you want to add the keys to the Debian security updates repository you can 
use an apt-key add command and the key available from 
http://ftp-master.debian.org/keys.html
[The main archive signing key is also used to sign the security updates].

Be aware that you might create problems for yourself.

You may well want to look at the Debian Administrators handbook - you can try 
apt-get install debian-handbook if the package is also available for Raspbian.

Hope this helps,

Al the very best,

AndyC 

[Copying to the list as this may be of more use more widely]

Re: Security Updates

[Lisi Reisz]

On Wednesday 31 August 2016 10:39:53 Lisi Reisz wrote:
> Since you are not replying to anyhting, you may not be subscribed,

I had a reply off list that said that Larry is not replying to our questions 
because he considers them irrelevant to his original question.

Lisi

> so here 
> is what I said again:
>
> On Tuesday 30 August 2016 20:58:47 Larry Dighera wrote:
> > This page  states:
> >
> > "If you use APT, add the following line to /etc/apt/sources.list to
> > be able to access the latest security updates:
> >
> > deb http://security.debian.org/ jessie/updates main contrib non-free
> >
> > After that, run apt-get update followed by apt-get upgrade."
> >
> > Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running
> > Debian Jessie results in an error message indicating that the public key
> > is not found. It also finds two libraries that require updating that are
> > not found when the above mentioned /etc/apt/sources.list entry is
> > removed.
> >
> >   1.  What do I need to do to prevent the error message?
> >
> >   2.  As there are other security related URLs (doubtless, as
> >   distributed/released) that are checked during apt-get update, is the
> >   recommended additional entry advisable/useful for this platform?
>
> What is the whole of your sources.list?
>
> Lisi
>
> Like other respondents I suspect that you are using Raspbian not Debian. 
> Your sources list will tell me/us, or guide us ot teh problem if it is not
> that.

Re: Decentralized reliable instant messaging?

[Amir H. Firouzian]

There is a trade off between decentralization & reliability. Traditional
E-Mail that people are talking about is NOT TRULY decentral.
For instance think about how E-Mail work:
1- Mail Client Query MX record from DNS
2- Connect to SMTP Server and Exchange E-Mail.
3- SMTP figure out the sender IP and look domain of E-Mail
3- SMTP server query SRV Record of that domain and check is that IP valid.
4- (Nowadays) SMTP query DKIM (Which is TXT record) and validate also.
So think how BITMESSAGE
:
1- The massage ONLY can access in TWO DAYS!
2- All Nodes have ALL E-Mail in Cryptic Form.

About you last sentence:
It's better that your message Not arrive instead of being disclose! and
This is the philosophy behind True P2P IM systems.
Regards

On Tue, Aug 30, 2016 at 1:05 PM, Stefan Monnier 
wrote:

> > You can't have all the best together.
>
> What does that mean, exactly?  Are you saying it doesn't have reliable
> message delivery?  If so, that'd be a deal breaker for me.
>
>
> Stefan "shocked that anyone would want to design or use an
> unreliable messaging system"
>
>
> > This mention in previous E-Mails as well. E.g:
> <20160817192400.GB9964@alum>
>
> > On Thu, Aug 25, 2016 at 6:00 PM, Stefan Monnier <
> monn...@iro.umontreal.ca>
> > wrote:
>
> >> > I think you looking for TOX!
> >> > Visit TOX Project website:
> >> > https://tox.chat
> >>
> >> Thanks.  That does look promising (although I don't see any mention of
> >> reliable delivery),
> >>
> >>
> >> Stefan
> >>
> >>
> >> > On Sat, Aug 13, 2016 at 7:19 AM, Stefan Monnier <
> >> monn...@iro.umontreal.ca>
> >> > wrote:
> >>
> >> >> I'm looking for a decentralized instant message system (e.g. XMPP,
> SIP,
> >> >> ...) where I can be sure that I receive all messages, even if I'm not
> >> >> connected when the message is sent [ Obviously, I'll only receive
> them
> >> >> when I'm back online.  ]
> >> >>
> >> >> IIUC there is some XMPP features that allow such reliable delivery,
> but
> >> >> it seems that it's not widely supported by clients.  What Debian
> >> >> clients, using which protocols, can provide reliable instant
> messaging?
> >> >>
> >> >>
> >> >> Stefan
> >> >>
> >> >>
> >> >> PS: Bonus points if that feature is also available on an Android
> >> >> application that's Free Software.
> >> >>
> >> >>
> >>
>

Re: postfix mail filtering

[Perry E. Metzger]

On Wed, 31 Aug 2016 13:21:13 +0100 Tony van der Hoff
 wrote:
> So, I'd like to perform the filtering on the server (for my user 
> initially, then perhaps for others). My extensive googling reveals
> that there are many tutorials for filtering spam, but that's not
> really my problem.

What you're looking for is an implementation of the Sieve
language/system for mail filtering. You don't say what IMAP
server you are using, but Dovecot has an implementation of this called
"Pigeonhole" that is very likely what you want.

Perry
-- 
Perry E. Metzgerpe...@piermont.com

Re: Decentralized reliable instant messaging?

[Brian]

On Wed 31 Aug 2016 at 10:54:53 +0200, claude juif wrote:

> > Le 31 août 2016 9:48 AM, "Joe"  a écrit :
> >
> > Email is still a useful messaging protocol, it is somewhat broken, but
> > the cure absolutely must not be worse than the disease, or we'll all
> > end up using Facebook.

> Come on guys, the OP ask about instant messaging and mail is everything
> except instant messaging.

With two machines running mail servers (no smarthosts or any of that
nonsense) the messaging is virtually instantaneous. The protocol used
has a good track record and is reliable and robust. It might not suit
what the OP or his respondents want but the bits and pieces to build
such a system are all in Debian.

If one machine is down a secondary MX should take up the slack and
deliver the message when it comes back online.

postfix mail filtering

[Tony van der Hoff]

Hi list,

I'm running postfix under Wheezy on my VPS, using a more or less 
out-of-the-box configuration. My users access their mail via IMAP.


I subscribe to a number of mail lists, such as this one. I currently use 
Thunderbird's filtering capability to sort mail into a number of 
subdirectories within my inbox, which works fine, but requires me to set 
up all my workstayions (laptop, home, work) with the same filters. I 
have now acquired an Android smartphone, which has no filtering 
capability. In any case, keeping a number of workstations in sync is a pain.


So, I'd like to perform the filtering on the server (for my user 
initially, then perhaps for others). My extensive googling reveals that 
there are many tutorials for filtering spam, but that's not really my 
problem.


I can't find any tutorials on how to set up filters based on, say 
subject:, from:, or to: fields, but feel certain such must exist.

Can any kind person direct me to a suitable tutorial, please?

Thanks, Tony
--
Tony van der Hoff| mailto:t...@vanderhoff.org
Buckinghamshire, England |

Re: conseil carte-mère

[Jean-Marc]

Wed, 31 Aug 2016 11:03:39 +0200
Jean-Marc  écrivait :

> salut la liste,
> [...]
> La carte Gigbyte GA-Z170-Gaming K3 est sur ma liste.

Après avoir regardé en détail, je pense plutôt opter pour une carte 
GA-Z170X-Gaming 5.

Sortie DisplayPort et Wake on LAN à dispo.
Et chipset Intel pour le réseau.


Jean-Marc 


pgpaF87OgOqrl.pgp
Description: PGP signature

Re: conseil carte-mère

[Jean-Marc]

Wed, 31 Aug 2016 11:16:36 +0200
Bernard Schoenacker  écrivait :

> bonjour,
> 
> qu'est ce que tu choisi comme carte graphique ?

Aucune. Je compte utiliser le chip intégré au CPU.

> 
> slt
> bernard

Jean-Marc 


pgpLajWikhWTZ.pgp
Description: PGP signature

Re: Decentralized reliable instant messaging?

[Lisi Reisz]

On Wednesday 31 August 2016 07:27:51 deloptes wrote:
> Use authorized
> SMTP servers.

mailhost.zen.co.uk
https://www.zen.co.uk/

As I said, lucky you.

Lisi

Re: Security Updates

[Lisi Reisz]

Since you are not replying to anyhting, you may not be subscribed, so here is 
what I said again:

On Tuesday 30 August 2016 20:58:47 Larry Dighera wrote:
> This page  states:
>
> "If you use APT, add the following line to /etc/apt/sources.list to be
> able to access the latest security updates:
>
> deb http://security.debian.org/ jessie/updates main contrib non-free
>
> After that, run apt-get update followed by apt-get upgrade."
>
> Adding that entry to /etc/apt/sources.list on the Raspberry Pi3 running
> Debian Jessie results in an error message indicating that the public key is
> not found. It also finds two libraries that require updating that are not
> found when the above mentioned /etc/apt/sources.list entry is removed.
>
>   1.  What do I need to do to prevent the error message?
>
>   2.  As there are other security related URLs (doubtless, as
>   distributed/released) that are checked during apt-get update, is the
>   recommended additional entry advisable/useful for this platform?

What is the whole of your sources.list?

Lisi

Like other respondents I suspect that you are using Raspbian not Debian.  Your 
sources list will tell me/us, or guide us ot teh problem if it is not that.

Re: conseil carte-mère

[Bernard Schoenacker]

Le Wed, 31 Aug 2016 11:03:39 +0200,
Jean-Marc  a écrit :

> salut la liste,
> 
> J'ai besoin d'un conseil l'achat d'une carte-mère pour installer un
> système Debian Stretch/Sid sur Intel core I7 Skylake + disque SSD
> NVMe.
> 
> La carte Gigbyte GA-Z170-Gaming K3 est sur ma liste.
> 
> Comme c'est du matos assez récent, je ne trouve rien quand je fais
> une recherche sur le support de ce genre de chose par Linux.
> 
> Le seul truc concerne le chipset LAN qui semble OK avec un noyau >
> 3.10.
> 
> Toute info est la bienvenue.
> 
> Merci.
> 
> Jean-Marc 

bonjour,

qu'est ce que tu choisi comme carte graphique ?

slt
bernard

Re: conseil carte-mère

[Olivier Bitsch]

Hello,

J'avais écrit un article (en anglais) sur le support des Intel NUC (Micro
PC) qui contiennent également un Intel core i7 Skylate et disque SSD NVMe.

J'ai eu quelques soucis à l'installation (grub ne reconnaissait pas le
disque NVMe), mais il existe des solutions de contournement.

Ensuite pour jouer avec la carte graphique interne, il a également faire
une petite bidouille.

Toutes les infos ici :
http://iabsis.com/fr/community/blog/view/debian-intel-nuc-6i5syk

Olivier.

Le 31 août 2016 à 11:03, Jean-Marc  a écrit :

> salut la liste,
>
> J'ai besoin d'un conseil l'achat d'une carte-mère pour installer un
> système Debian Stretch/Sid sur Intel core I7 Skylake + disque SSD NVMe.
>
> La carte Gigbyte GA-Z170-Gaming K3 est sur ma liste.
>
> Comme c'est du matos assez récent, je ne trouve rien quand je fais une
> recherche sur le support de ce genre de chose par Linux.
>
> Le seul truc concerne le chipset LAN qui semble OK avec un noyau > 3.10.
>
> Toute info est la bienvenue.
>
> Merci.
>
> Jean-Marc 
>

conseil carte-mère

[Jean-Marc]

salut la liste,

J'ai besoin d'un conseil l'achat d'une carte-mère pour installer un système 
Debian Stretch/Sid sur Intel core I7 Skylake + disque SSD NVMe.

La carte Gigbyte GA-Z170-Gaming K3 est sur ma liste.

Comme c'est du matos assez récent, je ne trouve rien quand je fais une 
recherche sur le support de ce genre de chose par Linux.

Le seul truc concerne le chipset LAN qui semble OK avec un noyau > 3.10.

Toute info est la bienvenue.

Merci.

Jean-Marc 


pgptZd3GvSOIl.pgp
Description: PGP signature

Re: Decentralized reliable instant messaging?

[claude juif]

Hi,

Come on guys, the OP ask about instant messaging and mail is everything
except instant messaging.

IRC with recording bot could do the job. (But it's clearly old and kind of
hard to setup)

By the way, you could make a simple app based on AMQP protocol to fit your
need.

Regards,

Le 31 août 2016 9:48 AM, "Joe"  a écrit :

On Wed, 31 Aug 2016 08:27:51 +0200
deloptes  wrote:

> Lisi Reisz wrote:
>
> >
> >> About reliability - I have not seen recently undelivered mails
> >> (except bounces between gmain and yahoo .
> >
> > Lucky you!
> >
> > Lisi
>
> Luck is something, that is out of scope in terms of software. Use
> authorized SMTP servers.

Who authorises them, if not the owner of the domain? Should our
governments expect to be paid for email server licences?

> This means you can not install on your linux
> box an smtp server, send an email and expect it to be delivered.

I have done so, for about fifteen years. I like it that way.

> If
> it is your provider, change it or talk to them. It is not common that
> messages are rated as spam, when they come out from legal MX records.

The MX record is not involved in sending. Many companies outsource
their anti-spamming, or for other reasons use completely different
sending and receiving servers.

What you need are complementary domain host A record and IP address
PTR records, pointing to each other, along with an ISP which doesn't
host bulk emailers and is otherwise willing to keep itself off
blacklists.

> As I said DMARC initiative is going on at the moment (and since
> couple of years) and it will affect the mailing in positive way I
> hope.

The main problem with anything like that is that many people have
relatively complex email arrangements, e.g. forwarding from a number of
email addresses to another, and these tend to get broken by security
measures. A couple of years ago my ISP, who had provided email services
based on sub-domains, outsourced them to an Exchange-based system using
the MS SPF system. I don't use the provided sub-domain, so it didn't
involve me, but there was a lot of trouble about it, and eventually the
ISP grudgingly provided another pair of MX records for a SMTP server
which did not implement this system.

Email is still a useful messaging protocol, it is somewhat broken, but
the cure absolutely must not be worse than the disease, or we'll all
end up using Facebook.

--
Joe

Re: livestreamer i mplayer

[Pere Nubiola Radigales]

Has provat de executar

livestreamer --stdout -cache 2048' $URL best | mplayer

Pere Nubiola Radigales
Telf: +34 656316974
e-mail: p...@nubiola.cat
   pnubi...@fsfe.org
   pere.nubi...@gmail.com


El dia 31 d’agost de 2016, 0:33, Alex Muntada  ha escrit:

> Ernest Adrogué:
>
> > livestreamer --player 'mplayer -cache 2048' --verbose-player $URL best
> >
> > el problema és que el livestreamer exectuta mplayer en segon terme.
> Llavors
> > com que l'mplayer no està connectat al terminal no es pot controlar amb
> el
> > teclat (p.ex, per fer pausa o silenciar la reproducció).  La solució
> seria
> > obrir mplayer en un terminal gràfic propi amb una cosa com
>
> Has provat amb gnome-mplayer o algun altre frontal del mplayer?
>
> Salut,
> Alex
>
>

Re: Decentralized reliable instant messaging?

[Joe]

On Wed, 31 Aug 2016 08:27:51 +0200
deloptes  wrote:

> Lisi Reisz wrote:
> 
> >   
> >> About reliability - I have not seen recently undelivered mails
> >> (except bounces between gmain and yahoo .  
> > 
> > Lucky you!
> > 
> > Lisi  
> 
> Luck is something, that is out of scope in terms of software. Use
> authorized SMTP servers.

Who authorises them, if not the owner of the domain? Should our
governments expect to be paid for email server licences?

> This means you can not install on your linux
> box an smtp server, send an email and expect it to be delivered.

I have done so, for about fifteen years. I like it that way.

> If
> it is your provider, change it or talk to them. It is not common that
> messages are rated as spam, when they come out from legal MX records.

The MX record is not involved in sending. Many companies outsource
their anti-spamming, or for other reasons use completely different
sending and receiving servers.

What you need are complementary domain host A record and IP address
PTR records, pointing to each other, along with an ISP which doesn't
host bulk emailers and is otherwise willing to keep itself off
blacklists.

> As I said DMARC initiative is going on at the moment (and since
> couple of years) and it will affect the mailing in positive way I
> hope.

The main problem with anything like that is that many people have
relatively complex email arrangements, e.g. forwarding from a number of
email addresses to another, and these tend to get broken by security
measures. A couple of years ago my ISP, who had provided email services
based on sub-domains, outsourced them to an Exchange-based system using
the MS SPF system. I don't use the provided sub-domain, so it didn't
involve me, but there was a lot of trouble about it, and eventually the
ISP grudgingly provided another pair of MX records for a SMTP server
which did not implement this system.

Email is still a useful messaging protocol, it is somewhat broken, but
the cure absolutely must not be worse than the disease, or we'll all
end up using Facebook.

-- 
Joe

Re: Jessie live booting at 32 bit uefi PC ?

[Hyeonjin Oh]

Hi Thomas Schmitt, Thank you for fast feedback.

Have good day.

2016. 8. 31. 오후 3:58에 "Thomas Schmitt" 님이 작성:

> Hi,
>
> Hyeonjin Oh wrote:
> > Is jessie live possible to boot at 32 bit uefi PC ?
>
> Only via "legacy" BIOS emulation.
>
> Inspection of
>   http://cdimage.debian.org/mirror/cdimage/archive/8.4.0-
> live/i386/iso-hybrid/debian-live-8.4.0-i386-standard.iso
> shows that there are only boot entries which lure PC-BIOS:
>
> - El Torito boot catalog with a single entry for platform "80x86"
>   (which means PC-BIOS). This is used by BIOS when booting from
>   optical media (CD, DVD, BD).
>
> - Isohybrid MBR with a single partition starting at 512-block number 64
>   and not being of type 0xef. (I.e. it is not the EFI System Partition and
>   no valid GUID Partition Table is present.)
>   The MBR program code is used by BIOS when booting from USB stick,
>   memory card, or hard disk.
>
> You could try whether a netinst ISO boots properly on your hardware:
>   http://cdimage.debian.org/debian-cd/8.5.0/i386/iso-cd/
> debian-8.5.0-i386-netinst.iso
> and if so, ask at
>   debian-l...@lists.debian.org
> to give LiveCD the same boot equipment as netinst has.
>
> There seems to be work in progress
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731709
> So my advise is not to complain in any way but rather to offer yourself
> as tester of newest development.
>
>
> Have a nice day :)
>
> Thomas
>
>

Re: Jessie live booting at 32 bit uefi PC ?

[Thomas Schmitt]

Hi,

Hyeonjin Oh wrote:
> Is jessie live possible to boot at 32 bit uefi PC ?

Only via "legacy" BIOS emulation.

Inspection of
  
http://cdimage.debian.org/mirror/cdimage/archive/8.4.0-live/i386/iso-hybrid/debian-live-8.4.0-i386-standard.iso
shows that there are only boot entries which lure PC-BIOS:

- El Torito boot catalog with a single entry for platform "80x86"
  (which means PC-BIOS). This is used by BIOS when booting from
  optical media (CD, DVD, BD).

- Isohybrid MBR with a single partition starting at 512-block number 64
  and not being of type 0xef. (I.e. it is not the EFI System Partition and
  no valid GUID Partition Table is present.)
  The MBR program code is used by BIOS when booting from USB stick,
  memory card, or hard disk.

You could try whether a netinst ISO boots properly on your hardware:
  
http://cdimage.debian.org/debian-cd/8.5.0/i386/iso-cd/debian-8.5.0-i386-netinst.iso
and if so, ask at
  debian-l...@lists.debian.org
to give LiveCD the same boot equipment as netinst has.

There seems to be work in progress
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731709
So my advise is not to complain in any way but rather to offer yourself
as tester of newest development.


Have a nice day :)

Thomas

Jessie live booting at 32 bit uefi PC ?

[Hyeonjin Oh]

Thanks a lot, Debian team.

I have a question below.

Is jessie live possible to boot at 32 bit uefi PC ? (Most tablet with
baytrail CPU is only supporting 32 bit uefi boot)

Re: Decentralized reliable instant messaging?

[deloptes]

Lisi Reisz wrote:

> 
>> About reliability - I have not seen recently undelivered mails (except
>> bounces between gmain and yahoo .
> 
> Lucky you!
> 
> Lisi

Luck is something, that is out of scope in terms of software. Use authorized
SMTP servers. This means you can not install on your linux box an smtp
server, send an email and expect it to be delivered. If it is your
provider, change it or talk to them. It is not common that messages are
rated as spam, when they come out from legal MX records. As I said DMARC
initiative is going on at the moment (and since couple of years) and it
will affect the mailing in positive way I hope.

regards