moin,
beim login auf den srv01 passierte heute
# ssh srv01
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
SHA256:LX0xpviTs3pSYWtibqspcjoqDDxrkzA1kw0F+4ZmXps.
Please contact your system administrator.
was ist hier los?
The authenticity of host 'srv01.ffnw.de (37.120.176.207)' can't be
established.
RSA key fingerprint is SHA256:LX0xpviTs3pSYWtibqspcjoqDDxrkzA1kw0F+4ZmXps.
RSA key fingerprint is MD5:97:7f:f3:b0:7f:57:04:d1:96:15:7f:eb:bc:de:17:6e.
es macht sinn das man weiss das man sich auf den richtigen srv verbindet,
wieso hat sich was am key geändert?
wo stehen die fingerprints zum vergleichen?
--
Freifunk Gruß
pic
Www: https://fr32k.de
Xmpp: picard(a)fr32k.de & picard(a)ffnw.de
Keybase: https://keybase.io/picard
--
Gruß
pic
Xmpp: picard(a)ffnw.de & picard(a)fr32k.de
@ME https://wiki.nordwest.freifunk.net/picard
Moin,
auf einem Server von Stefan läuft nun eine neue VM: files.ffnw.de
Die beherbergt sowohl die Firmware als auch die Cloud. Auf lange Sicht
können wir uns also von srv01 trennen, den ich gestern zum
nächstmöglichen Zeitpunkt (2.2.18) gekündigt habe,
Grüße
Hello,
Your certificate (or certificates) for the names listed below will expire in
0 days (on 01 Aug 17 09:55 +0000). Please make sure to renew
your certificate before then, or visitors to your website will encounter errors.
support.ffnw.de
support2.ffnw.de
For any questions or support, please visit https://community.letsencrypt.org/.
Unfortunately, we can't provide support by email.
For details about when we send these emails, please visit
https://letsencrypt.org/docs/expiration-emails/. In particular, note
that this reminder email is still sent if you've obtained a slightly
different certificate by adding or removing names. If you've replaced
this certificate with a newer one that covers more or fewer names than
the list above, you may be able to ignore this message.
If you want to stop receiving all email from this address, click
http://mandrillapp.com/track/unsub.php?u=30850198&id=fc770692ce714864b34028…
(Warning: this is a one-click action that cannot be undone)
Regards,
The Let's Encrypt Team
Hello,
Your certificate (or certificates) for the names listed below will expire in
0 days (on 31 Jul 17 21:14 +0000). Please make sure to renew
your certificate before then, or visitors to your website will encounter errors.
invalid.ffnw.de
For any questions or support, please visit https://community.letsencrypt.org/.
Unfortunately, we can't provide support by email.
For details about when we send these emails, please visit
https://letsencrypt.org/docs/expiration-emails/. In particular, note
that this reminder email is still sent if you've obtained a slightly
different certificate by adding or removing names. If you've replaced
this certificate with a newer one that covers more or fewer names than
the list above, you may be able to ignore this message.
If you want to stop receiving all email from this address, click
http://mandrillapp.com/track/unsub.php?u=30850198&id=5407afc607d84b7a99a37c…
(Warning: this is a one-click action that cannot be undone)
Regards,
The Let's Encrypt Team
Hello,
Your certificate (or certificates) for the names listed below will expire in
19 days (on 18 Aug 17 14:36 +0000). Please make sure to renew
your certificate before then, or visitors to your website will encounter errors.
mediawiki.ffnw.de
For any questions or support, please visit https://community.letsencrypt.org/.
Unfortunately, we can't provide support by email.
For details about when we send these emails, please visit
https://letsencrypt.org/docs/expiration-emails/. In particular, note
that this reminder email is still sent if you've obtained a slightly
different certificate by adding or removing names. If you've replaced
this certificate with a newer one that covers more or fewer names than
the list above, you may be able to ignore this message.
If you want to stop receiving all email from this address, click
http://mandrillapp.com/track/unsub.php?u=30850198&id=f33027e818214c5a8c0993…
(Warning: this is a one-click action that cannot be undone)
Regards,
The Let's Encrypt Team
Hello,
Your certificate (or certificates) for the names listed below will expire in
9 days (on 06 Aug 17 09:56 +0000). Please make sure to renew
your certificate before then, or visitors to your website will encounter errors.
inventar.ffnw.de
odoo.ffnw.de
For any questions or support, please visit https://community.letsencrypt.org/.
Unfortunately, we can't provide support by email.
For details about when we send these emails, please visit
https://letsencrypt.org/docs/expiration-emails/. In particular, note
that this reminder email is still sent if you've obtained a slightly
different certificate by adding or removing names. If you've replaced
this certificate with a newer one that covers more or fewer names than
the list above, you may be able to ignore this message.
If you want to stop receiving all email from this address, click
http://mandrillapp.com/track/unsub.php?u=30850198&id=fbc36c5618074b06b891b9…
(Warning: this is a one-click action that cannot be undone)
Regards,
The Let's Encrypt Team
Dear Supporter of Digital Freedom,
When trade agreements are negotiated in secret, the public
loses out. There's a new bill in Congress that would require
the U.S. to make drafts of trade agreements available to the
public.
The highly secretive Trans-Pacific Partnership (TPP) would
have locked the United States into its current, broken
copyright rules. It contained provisions that could have
easily been abused by repressive regimes to prosecute human
rights defenders. The TPP is dead, but with the reopening of
NAFTA, and other new trade deals on the horizon, powerful
corporations are lobbying for equally restrictive measures.
Our only hope is to demand transparency in U.S.
participation in trade negotiations. If public interest
groups and ordinary citizens have access to the text of
trade agreements as they are being written, then we can more
effectively urge the government to demand better agreements.
Tell your representative: give the public a place at the
table.
https://act.eff.org/action/demand-transparency-in-trade-deals
Thank you,
Elliot Harmon
Activism Team
Electronic Frontier Foundation
Support our work on transparency in trade agreements:
https://supporters.eff.org/donate/support-our-work-transparency-trade-agree…
Electronic Frontier Foundation, 815 Eddy Street, San Francisco, CA 94109 USA EFF appreciates your support and respects your privacy: https://www.eff.org/policy Unsubscribe from all mailings: https://supporters.eff.org/civicrm/mailing/optout?reset=1&jid=21429&qid=720… Change your email preferences: https://supporters.eff.org/update-your-preferences?cid1=2061725&cs=3d181a07…
Liebe Freifunk-Kollegen in Berlin, Bremen und Franken,
wir versuchen zur Zeit von Freifunk Nordwest einen Server am
Community-IX in Berlin in Betrieb zu nehmen.
Im Server steckt eine HP NC552SFP, die sich bei lspci 2x als Emulex
OneConnect 10Gb ausweist.
Seitens Community-IX sind auf dem Switch LLDP-Pakete von MAC+1 zu sehen,
die Ports haben xx:xx:xx:xx:13:88 und xx:xx:xx:xx:13:8c, die LLDP-Pakete
kommen von xx:xx:xx:xx:13:89. Auf dem System selbst sind die LLDP-Pakete
nicht sichtbar.
Nun haben wir per lldptool versucht, jeglichen LLDP-Foo abzuschalten,
was aber keine Besserung brachte, und hbacmd in einem CentOS-chroot
findet die Karte nicht. Im BIOS der Karte findet sich nichts zu LLDP,
nur zu PXE, was natürlich abgeschaltet ist.
Laut einer Seite[1] zu einer Karte, die auch das be2net Modul verwendet,
lässt sich dieses Verhalten auch nicht deaktivieren:
"The adapter uses the second or the MAC+1 port address for LLDP/DCBX
(Link Layer Discovery Protocol)/(Data Center Bridging eXchange) link
exchange. The DCBX engine is built into the network controller ASIC for
FCoE and is always active although FCoE is not supported. This MAC+1
address remains constant and is not changed with OFM. The forwarding
data base of the switch will show the Ethernet Base port MAC + 1 address
value. A user may expect to only see the port Base MAC address. This is
a potential point of confusion for a user who is unaware of the reason
why the base MAC+1 address is present."
Ist somit die Karte schlichtweg nicht geeignet für einen derartigen
Einsatz, da LLDP gegen die IX-Policy verstösst; oder welche
Möglichkeiten, die LLDP-Pakete abzuschalten, gibt es noch?
Wir haben leider, was SFP-Karten betrifft, bisher sogut wie keine Erfahrung.
Viele Grüße
bjo
[1]ftp://170.225.15.28/ecc/sar/CMA/IOA/03re3/2/Flex_FC1762_4P10GbE_0400401800003_Readme.html#7.3_Using_the_Linux_ethtool_Method_
Hello,
Your certificate (or certificates) for the names listed below will expire in
9 days (on 01 Aug 17 09:55 +0000). Please make sure to renew
your certificate before then, or visitors to your website will encounter errors.
support.ffnw.de
support2.ffnw.de
For any questions or support, please visit https://community.letsencrypt.org/.
Unfortunately, we can't provide support by email.
For details about when we send these emails, please visit
https://letsencrypt.org/docs/expiration-emails/. In particular, note
that this reminder email is still sent if you've obtained a slightly
different certificate by adding or removing names. If you've replaced
this certificate with a newer one that covers more or fewer names than
the list above, you may be able to ignore this message.
If you want to stop receiving all email from this address, click
http://mandrillapp.com/track/unsub.php?u=30850198&id=d954c6485ca64e44ae635f…
(Warning: this is a one-click action that cannot be undone)
Regards,
The Let's Encrypt Team