Tech Forum Archive

Official announcement / policy on Lehi SSID usage?

13 postsstarted by TChris67 8,965 viewsoriginal topic

TChris67
New Member
#1
I'm sure it was sent as an email at the time, and I have since deleted it. Is there somewhere I can view the original announcement and/or policy on the Lehi SSID? We have some folks arguing that Lehi should be generally available to the ward for smart devices, etc. Stake clerk and Stake President would like to see something official to avoid hard feelings if possible.

Thanks!
russellhltn
Community Administrator
#2
There may be something in the Official Communication Library, but for some reason, the letters from the Presiding Bishopric do not appear to the STS.

From TM: "The Lehi SSID is for local unit leaders only."

From the email sent to STS: "You now have the option to enable the Lehi wireless network (SSID). This will allow you to disable the Liahona SSID during the webcast of sacrament meeting or other important meetings but still provide a wireless network (Lehi) for other local unit leaders who are meeting in the same meetinghouse.
...
The passphrase must be updated for each meetinghouse where the Lehi SSID will be used. The passphrase should be shared only with unit leaders who are approved by the stake president. It must be updated every 90 days or it will automatically be disabled."

Why do people want access to Lehi? It's the same AP and uses the same internet connection. Is dealing with the splash screen really that much of a hardship?

Note that if access to Lehi is handed out generally, then when it's necessary to conserve bandwidth ALL WiFi will have to be shut off.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.

So we can better help you, please edit your Profile to include your general location.
TChris67
New Member
#3
I understand the purpose and ramifications as you have pointed out, but we have a brother frustrated because he isn't being allowed to do what he likes with the network. I think he's starting to back down a little now, but having some official statements will help reach an understanding. Stake president has already told him No, so we're in the "But why?" phase at the moment. Thanks for your response. :)
russellhltn
Community Administrator
#4
It might be the filtering he's running up against. I'm not sure as Lehi would help.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.

So we can better help you, please edit your Profile to include your general location.
nilbus
New Member
#5
The best I could find was the tech wiki page on Lehi and Liahona Wireless Networks. The intended purpose is so "you can disable the Liahona SSID during the webcast of Sacrament or other important meetings but still provide a wireless network (Lehi) for other local unit leaders that are meeting in the same meetinghouse." It states that it is for local "unit leaders that are approved by the Stake President". In the end, usage is up to him.
ambldsorg
Member
#6
nilbus wrote: Wed Apr 30, 2025 5:07 pm The intended purpose is so "you can disable the Liahona SSID during the webcast of Sacrament or other important meetings"
This might work fine in a meetinghouse that has only one ward, but what about those who have 3--4 wards that all have sacrament in the same building at different times of the day? Turning it off during sacrament necessarily means that it would also be off during someone elses sunday school.
russellhltn
Community Administrator
#7
When we've streamed sacrament meeting, we haven't had to turn off the WiFi.

But not all chapels have that much bandwidth. If more bandwidth can't be found, leadership is doing to have to make some decisions. What's more important - streamed meetings for the shut-ins, or giving the general membership full WiFi access? Should wards be scheduled to not have overlap? There's no answer that would make everyone happy.
Have you searched the Help Center? Try doing a Google search and adding "site:churchofjesuschrist.org/help" to the search criteria.

So we can better help you, please edit your Profile to include your general location.
nilbus
New Member
#8
We’ve never turned off WiFi for sacrament meeting streaming to shut-ins, but we have for events with more people like stake conference (streaming out) or stake watch parties (streaming in) where the attendance is much higher and the impact of network error is much greater.
davemoore99
New Member
#9
Anyone have a good recommendation on passwords to use for this every 90 days and good ways to communicate it with the leadership? Anyone found a way to automate this somewhat? Thanks!
ambldsorg
Member
#10
davemoore99 wrote: Sun Jan 18, 2026 10:27 am Anyone have a good recommendation on passwords to use for this every 90 days and good ways to communicate it with the leadership? Anyone found a way to automate this somewhat? Thanks!
Here's a quick Tcl/Tk script that I just wrote that uses Book of Mormon names and a random number to generate a password; you're welcome to use it. It should generate fairly good passwords for 90 day use.

Code: 

package require Tk

set bomnames {
Aaron Abel Abinadi Abinadom Abish Ablom Abraham Adam Agosh Aha Ahah Ahaz Aiath
Akish Alma Alpha Amaleki Amalekite Amalickiah Amalickiahite Amaron Amgid
Aminadab Aminadi Amlici Amlicite Ammah Ammaron Ammon Ammonihah Ammonihahite
Ammonite Ammoron Amnigaddah Amnihu Amnor Amoron Amos Amoz Amulek Amulon
Amulonites Anathoth Angola Ani-Anti Anti-Nephi-Lehi Anti-Nephi-Lehies Antiomno
Antion Antionah Antionum Antiparah Antipas Antipus Antum Archeantus Arpad
Assyria Babylon Bashan Benjamin Bethabara Boaz Bountiful Cain Calno Carchemish
Cezoram Chaldeans Chaldees Chemish Cherubim Cohor Com Comnor Corianton Coriantor
Coriantum Coriantumr Corihor Corom Cumeni Cumenihah Cumom Cumorah Curelom
Deseret Desolation Edom Egypt Egyptian Elam Elijah Emer Emron Enos Ephah Ephraim
Esrom Ethem Ether Eve Ezias Ezrom Gad Gadiandi Gadianton Gadiomnah Gallim
Gazelem Geba Gebim Gibeah Gid Giddianhi Giddonah Gideon Gidgiddonah Gidgiddoni
Gilead Gilgah Gilgal Gimgimno Gomorrah Hagoth Hamath Hearthom Helam Helaman
Helem Helorum Hem Hermounts Heshlon Heth Himni Horeb Immanuel Irreantum Isaac
Isabel Isaiah Ishmael Ishmaelite Israel Israelite Jacob Jacobite Jacobugath
Jacom Jared Jaredite Jarom Jashon Jeberechiah Jehovah Jeneum Jeremiah Jershon
Jerusalem Jesse Jew John Jonas Jordan Joseph Josephite Josh Joshua Jotham Judah
Judea Kib Kim Kimnor Kish Kishkumen Korihor Kumen Kumenonhi Laban Lachoneus
Laish Lamah Laman Lamanite Lamoni Lebanon Lehi Lehi-Nephi Lehonti Lemuel
Lemuelite Levi Liahona Lib Limhah Limher Limhi Limnah Luram Madmenah Mahah
Maher-shalal-hash-baz Malachi Manasseh Manti Mary Mathoni Mathonihah Medes
Melchizedek Melek Michmash Middoni Midian Migron Minon Moab Mocum Moriancumer
Morianton Moriantum Mormon Moron Moroni Moronihah Moses Mosiah Mulek Muloki
Nahom Naphtali Nazareth Neas Nehor Nephi Nephihah Nephite Neum Nimrah Nimrod
Noah Ogath Omega Omer Omner Omni Onidah Onihah Onti Ophir Oreb Orihah Paanchi
Pachus Pacumeni Pagag Pahoran Palestina Pathros Pekah Pharaoh Philistine
Rabbanah Rahab Ramah Ramath Rameumptom Remaliah Rezin Riplah Riplakish
Ripliancum Salem Sam Samaria Samuel Sarah Sariah Saul Seantum Sebus Seezoram
Senine Senum Seraphim Seth Shared Shazer Shearjashub Shelem Shem Shemlon Shemnon
Sherem Sherrizah Sheum Shez Shiblom Shiblon Shiblum Shiloah Shilom Shim
Shimnilom Shinar Shiz Shule Shum Shurr Sidom Sidon Sinai Sinim Siron Syria
Tarshish Teancum Teomner Thummim Timothy Tubaloth Uriah Urim Uzziah Zarahemla
Zebulun Zechariah Zedekiah Zeezrom Zemnarihah Zenephi Zeniff Zenock Zenos
Zerahemnah Zeram Zerin Ziff Zion Zoram Zoramite
}
set lnames [llength $bomnames]
proc genlehipass {w} {
  global bomnames lnames
  $w delete 1.0 end
  for {set x 0} {$x < 3} {incr x} {
    lappend lehipass [lindex $bomnames [expr {int(rand() * $lnames)}]]
  }
  set lehipass [join $lehipass .]
  append lehipass [format %02d [expr {int(rand() * 100)}]]
  $w insert end [join $lehipass .]
}

frame .f
labelframe .f.l -text "Lehi SSID Password Generator"
set t [text .f.l.t -width 68 -height 1]
button .f.l.b -text "Generate" -command [list genlehipass $t]
button .f.l.bc -text "Clear" -command [list $t delete 1.0 end]
pack .f.l.t .f.l.b .f.l.bc -side left
pack .f.l .f
Here's a demonstration (click to view animation):
lehissidpassgen.gif
Save the script into a file named lehissidpass.tcl and then run:

Code: 

tclsh lehissidpass.tcl
Passwords generated look like:

Code: 

Sariah.Kimnor.Abish18
As for communication? Write it down on a piece of paper and place it on their desk? Oh you want to email it? Well, you could just email it---odds are nobody is going to exploit it. Good security is about evaluating proper risk level. Or, you could use something like https://privnote.com/ to communicate it more securely than just in the body of an email---you would want to send out a separate privnote link to each recipient because they self-destruct on the first view.
davemoore99
New Member
#11
Excellent thank you. I'm just trying to create an efficient work flow for 3 different buildings as the STS
ambldsorg
Member
#12
davemoore99 wrote: Sun Jan 18, 2026 5:28 pm Excellent thank you. I'm just trying to create an efficient work flow for 3 different buildings as the STS
One thing that I just realized is that the script that I shared will generate passwords that are too long, at least if I'm to believe the screenshot here:

https://tech.churchofjesuschrist.org/wi ... s_Networks

It's unfortunate that it only allows a maximum of 15 characters. "Maher-shalal-hash-baz" alone is already 22 characters. Perhaps it should be modified to choose only one name from the list (except of course "Maher-shalal-hash-baz") and a random number and perhaps a non-alphanumeric character.

Here are some changes that will do that, always generating a 15 character password:

Code: 

set nnalnum {! \" # $ % & ' ( ) * + , - . / [ \\ ] ^ _ ` ~ : ; < = > ? @ \{ \}}
proc genlehipass {w} {
  global bomnames lnames nnalnum
  $w delete 1.0 end
  while {1} {
    set tmppass [lindex $bomnames [expr {int(rand() * $lnames)}]]
    if {[expr {[string length $tmppass] + 2}] <= 15} {
      set lehipass $tmppass
      break
    }
  }
  if {[string length $lehipass] < 13} {
    append lehipass [lindex $nnalnum [expr {int(rand() * [llength $nnalnum])}]]
  }
  append lehipass [expr {int(rand() * pow(10,15-[string length $lehipass]))}]
  $w insert end $lehipass   
}
Samples:

Code: 

Kumen`895074798
Kumenonhi/65757
Thummim^4019491
At any rate, good luck with implementing your plan.
davemoore99
New Member
#13
Once again thank you for taking the time to give me some ideas and share the script. i've got a starting place now!