lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <105757.49287.qm@web31805.mail.mud.yahoo.com> Date: Wed, 10 Oct 2007 12:38:42 -0700 (PDT) From: Luben Tuikov <ltuikov@...oo.com> To: James.Smart@...lex.Com, "Darrick J. Wong" <djwong@...ibm.com> Cc: Andrew Vasquez <andrew.vasquez@...gic.com>, linux-scsi <linux-scsi@...r.kernel.org>, linux-kernel <linux-kernel@...r.kernel.org>, Alexis Bruemmer <alexisb@...ibm.com>, James Bottomley <james.bottomley@...eleye.com> Subject: Re: [PATCH] aic94xx: Use request_firmware() to provide SAS address if the adapter lacks one --- James Smart <James.Smart@...lex.Com> wrote: > Here's one pro for setting WWNs at arbitrary times... > If the box is migrating applications (say containers) that want > different SAN connectivity, where that connectivity (view) is based > on their WWN, it would be really nice to selectively set the WWN and > not touch the SAN config. No. The WWN stays the same and the SAN is re-configured to be aware of the node migration. Access patterns could be more complex than just a single portal allowing access to/from the SAN from/to the node. WWN is supposed to be persistent. This is what it actually is. It is NOT supposed to be "(auto)generated" and/or changed at a whim. This also has security implications, and enterprise networks may refuse to use software (read "kernel") which allows for arbitrary changes to a node's WWN. If access to a node is compromised, a rogue agent may change the node's WWN in order to access SAN zones that it normally will be denied access to. Luben - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists